Вы находитесь на странице: 1из 3

Software Testing Life Cycle consists of six (generic) phases:

Test Planning,
Test Analysis,
Test Design,
Construction and verification,
Testing Cycles,
Final Testing and Ipleentation and
Post Ipleentation!
Software testing has its o"n life cycle that intersects "ith every stage of the #D$C! The %asic
re&uireents in software testing life cycle is to control'deal "ith soft"are testing ( )anual,
Autoated and Perforance!
Test Planning
This is the phase "here Pro*ect )anager has to decide "hat things need to %e tested, do I have
the appropriate %udget etc! +aturally proper planning at this stage "ould greatly reduce the ris,
of lo" &uality soft"are! This planning "ill %e an ongoing process "ith no end point!
Software Testing Life Cycle
Phase Activities Outcome
Planning Create high level test plan Test plan, -efined #pecification

Create detailed test plan, Functional
.alidation )atrix, test cases
-evised Test Plan, Functional
validation atrix, test cases

test cases are revised/ select "hich test
cases to autoate
revised test cases, test data
sets, sets, ris, assessent

scripting of test cases to autoate,
test procedures'#cripts,
Drivers, test results,
Testing cycles coplete testing cycles Test results, 0ug -eports
Final testing
execute reaining stress and perforance
tests, coplete docuentation
Test results and different
etrics on test efforts
Post ipleentation 1valuate testing processes
Plan for iproveent of testing
Activities at this stage "ould include preparation of high level test plan2(according to I111 test
plan teplate The #oft"are Test Plan (#TP) is designed to prescri%e the scope, approach,
resources, and schedule of all testing activities! The plan ust identify the ites to %e tested, the
features to %e tested, the types of testing to %e perfored, the personnel responsi%le for testing,
the resources and schedule re&uired to coplete testing, and the ris,s associated "ith the plan!)!
Alost all of the activities done during this stage are included in this soft"are test plan and
revolve around a test plan!
Test Analysis
3nce test plan is ade and decided upon, next step is to delve little ore into the pro*ect and
decide "hat types of testing should %e carried out at different stages of #D$C, do "e need or plan
to autoate, if yes then "hen the appropriate tie to autoate is, "hat type of specific
docuentation I need for testing!
Proper and regular eetings should %e held %et"een testing teas, pro*ect anagers,
developent teas, 0usiness Analysts to chec, the progress of things "hich "ill give a fair idea
of the oveent of the pro*ect and ensure the copleteness of the test plan created in the
planning phase, "hich "ill further help in enhancing the right testing strategy created earlier! 4e
"ill start creating test case forats and test cases itself! In this stage "e need to develop
Functional validation atrix %ased on 0usiness -e&uireents to ensure that all syste
re&uireents are covered %y one or ore test cases, identify "hich test cases to autoate, %egin
revie" of docuentation, i!e! Functional Design, 0usiness -e&uireents, Product #pecifications,
Product 1xternals etc! 4e also have to define areas for #tress and Perforance testing!
Test Design
Test plans and cases "hich "ere developed in the analysis phase are revised! Functional
validation atrix is also revised and finali5ed! In this stage ris, assessent criteria is developed!
If you have thought of autoation then you have to select "hich test cases to autoate and
%egin "riting scripts for the! Test data is prepared! #tandards for unit testing and pass ' fail
criteria are defined here! #chedule for testing is revised (if necessary) 6 finali5ed and test
environent is prepared!
Construction and verification
In this phase "e have to coplete all the test plans, test cases, coplete the scripting of the
autoated test cases, #tress and Perforance testing plans needs to %e copleted! 4e have to
support the developent tea in their unit testing phase! And o%viously %ug reporting "ould %e
done as "hen the %ugs are found! Integration tests are perfored and errors (if any) are
Testing Cycles
In this phase "e have to coplete testing cycles until test cases are executed "ithout errors or a
predefined condition is reached! -un test cases 227 -eport 0ugs 227 revise test cases (if needed)
227 add ne" test cases (if needed) 227 %ug fixing 227 retesting (test cycle 8, test cycle 9:!)!
Final Testing and Implementation
In this "e have to execute reaining stress and perforance test cases, docuentation for
testing is copleted ' updated, provide and coplete different atrices for testing! Acceptance,
load and recovery testing "ill also %e conducted and the application needs to %e verified under
production conditions!
Post Implementation
In this phase, the testing process is evaluated and lessons learnt fro that testing process are
docuented! $ine of attac, to prevent siilar pro%les in future pro*ects is identified! Create
plans to iprove the processes! The recording of ne" errors and enhanceents is an ongoing
process! Cleaning up of test environent is done and test achines are restored to %ase lines in
this stage!