Elaborating Software Test Processes and Strategies

A.Priyanka,B.Pravallika,B.Satvika

COMPUTER SCIENCE AND ENGINEERING

Koneru Lakshmaiah Education Foundation,

Greenfields, Vaddeswaram , Guntur.

[email protected], [email protected],

[email protected]

Abstract--- The under softwares responsible 50 percent of the cost

strategies, from our research group development . The test process and parts
conducted a qualitative study on software that software testing has been defined in
producing organization’s test processes several models and certificates like
TMMi or ISTQB . according to these,
The study manily focuses on the aspects there exists a new software testing
that compose testing strategy; human standard, ISO/IEC 29119 , it defines the
resources, test tools, test case selection, standard model for software testing
testing methods and the role of the process in organizations.
management in the test process to name
few of the major components. By the test The test process of model has four process
cases, there is also a improvements of
the software products and focusing the 1.policies
available test resources, problems which 2.strategies
could be addressed by means of
3. management and practice,
systematic process improvement and test
4.allwhich exist in test organizations
strategy for the organization.
In this research, the main aim is to build
1.Introduction: modelforreal-life organizations to apply
In development software, the process of the standard-based test process model to
testing is the costly phase , it can develop and observe the fitness of their
testing activities. This research is based on Test Cases Test Results Module To be
practical experience in software industry. Tested STUB STUB13

2. Different testing techniques 2.1.2.INTEGRATION TESTING :

2.1.Strategies Approach: After completing unit testing the

integration testing comes in second level
In this approach the testcases strategically of testing . This process deals with the of
uncover more number of errors in short different modules. each of the module is
time of span .We should decide the tested completely , one cannot enter this
suitable test strategies with suitable test testing phase. This the best approach to
plan and produce a text document.Testing find out integration testing is the
should begin with the starting level(unit incremental integration; where modules
level ) and then should move towards the are added one after another. Integration
integration of the entire computer based testing will perform when new module is
system.We have different techniques are added . This process of testing is gbest to
required at different point of testing span find out which module is showing the
Test process should perform by error.
independent test group. There are two methods of integration –
A typical Software Test Strategy the Top-Down integration and Bottom-Up
testing is that testing is a big task, the integration.
testing cycle can be divided into four 2.1.3.VALIDATION TESTING:
different phase where different test
strategy is employed in varaity phase The validation test ensures that the
following some requirements are satisfied
We also have different test techniques are successfully
used in different phase.
All Functional Requirements
The different phases of testing cycles.
All Behavioral characteristics
2.1.1.UNIT TESTING:
All Performance Requirements
Unit Testing is done with a an .
Component level design is used as a guide. All Documentation Correctness
It must to fix the the unit testing first. The If requirements are very useful in
module interface needs to be examined and validation testing likeerror
tested. The boundary conditions need to be compactability,reportability and
examined ( some sort of black box testing ,scalability a deficiency list need to be
).. The error conditions, the error handlings prepared from the normal reference.
and the error messages – all these criteria
need to be tested. 2.1.4.SYSTEM TESTING:

Unit Testing If it is necessary driver and After completion of validation

suitable stubs need to be developed and testing the final testing is system testing .
integrated with the modules DRIVER It is also implement the software with
hardware, people and information. The
purpose of the system testing is to fully 2. Beta Testing
implemented[2] by the computer based
3. Gamma Testing
system. The system test iseffective if it can
also done by the customer’s needs. 4. Smoke Testing
Otherwise the customer’s environment is
5. Regression Testing
re-created in-house.
6. Automated Testing
There are few types of system testing as
described :- 7. Fuzz Testing

- Recovery Testing [ How system 8. Static Testing

recovers from Faults? ] 2.4.SELECTED APPROACH AND
RESEARCH QUESTION:
- Security Testing [ while doing testing
process it secure the system ] The theory of this approach is to conduct
a grounded theory study on 12 different
- Stress Testing [ How much time the
software producing organizations. This
system can take the process? ]
selection of 12 different companies
- Performance Testing [ its performs represents different polar points of the
normal condition and also stresses industry, from service-oriented consultants
condition ] to multinational companies developing
software for their own products.
2.2.VERIFICATION AND
VALIDATION : 3.TEST STRATEGY:

Verification & Validation ( V&V ) The testing process[3] can be divided to

One has to Validate the product software several layers in software process
to ensure that all the functional are met by organisation
the software. One should to verify that
. layers test policy
product functionality has been correctly
implemented in the software. . test strategy

Verification : we need to check in testing . test management

we are going with product correct
.and testing work
Validation : we need to check in test 3.1:Software Testing Techniques:
process that we are going with right
product are not  Execute the program before the
customer.[2]
Validation comes only once in the  To reduce the number of errors
testingprocess but verification comes detected by customers.
throught the test process  In order to find the highest possible
number of errors software testing
2.3.OTHERS TYPES OF TESTING techniques must be used
SCENARIO:
3.1.1.Research method:
1. Alpha Testing
 This study is based on the grounded • Theory is generated [1]as a
theory research approach.[1] on this consequence of, systematic data
methods, the participating OU:s were collection and analysis
interviewed with questions related to the
research topic, while the situation was 4.2:Grounded theory works:
recorded and transliterated. The answers 1. We can understand the context, which
were then coded with three phased coding have been provided events, derived from it
scheme, the themes and concepts were
highlighted and later sorted for 2 we have more numbers of methods of
associations. data collection

As per the grounded theory approach, the 3 for that a key data can be implemented
method is considered well-suited for this and subjected to a process of testing
type of study for example a book called
4. grounded analysis, takes place
“Basics of Qualitative Research”
discovered by Strauss and Corbin defines
the method and introduces how it can be
applied. 4.3:Grounded analysis: stages

Three phases that grounded theory study • To bring different information of

consists of : data

• first Open coding analyzes and • investigating anomalies or

highlights all the concepts, relations and confirming relationships between
classes found within the collected data. source entities

• Axial encoding is establish • Code the data

dependencies and relations between
• Compare and contrast the data
classes and concepts.
• Identify patterns, categories, sub-
• Selective encoding uses the established
categories
relations to separate and highlight the
major concepts while defining the affect of • Saturation – no insights are reached
secondary concepts in relation to the major even when new data are added
ones.
5.rich interpretation, which leads to

6.Grounded theory –better result

4.GROUNDED THEORY
5:CODING:

4.1:Features of grounded theory: • Read the data several times to: get
a general sense, note down ideas,
• Theoretical explanations are not
think about organising the data,
predefined
check if more data are needed.
• Theory emerges from the data
• Then coding can start.
 • any who wishes to become • Fewer flaky tests
proficient at doing qualitative
analysis must learn to code well • Having nontechnical people start
and easily researcher doing automation

• coding has three types: open, axial, • Easier CI/CD integration

and selective • More reusable tests
5.1:The coding process: 8.CONCLUSION:
• Highlight key points in each As for the research approach in
dataset (e.g. an interview)
software test strategy, the impact of
• Give each key point a code to different aspects - tools, methods,
describe the data personnel, test case design and
quality criteria - should be further
• The codes will give patterns across
the data investigated as major areas of
interest
• Then group the patterns into
categories To achieve this goal,
this study pursues strategy of
• Give each category a title
observing and defining the impact
• New codes and subcategories will of each area of interest defined in
emerge. literature,while supplementing it
with concepts derived from real-
6.MYTHS SURROUNDING
life organizations. The current
SOFTWARE TESTING CAREER:.
strategy is to refine these
• Testing Compensations will be observations into general strategies
less as releated business. with variables for affecting factors

• There is no career growth in 9.References:

Software Testing.
1. A. Strauss and J. Corbin, Basics
• the individuals who don’t know of Qualitative Research: Grounded
code take Software Testing as a Theory Procedures and
profession Techniques. Newbury Park, CA:
SAGE Publications, 1990.
7: Future of Software testing:
2. E. Kit, “Software Testing in the
• Artificial Intelligence: some of the Real World: Improving the
benefits we could expect to start Process”, Addison-Wesley,
seeing in testing thanks to AI: Reading, MA, USA, 1995
• Easier authoring of tests 3. D.-J. De Grood, “Generic Test
Strategy”, Testgoal, Springer
• Lower maintenance work on test
Berlin Heidelberg, pp. 119-123,
scripts
2008. ISBN 978-3-540-78828-7