.ico)
Software Testing Life Cycle (STLC)
STLC (Software Testing Life Cycle) which includes different phases of the testing process.The testing process is executed in a well-planned and systematic manner. All activities are done to improve the quality of the software product.
STLC (Software Testing Life Cycle) is a process of specific activities/phases organised during the testing process to ensure software should meet the quality. STLC involves both verification and validation activities.Mostly These flow of process is followed in many industries.
STLC (Software Testing Life Cycle) is journey of testing from where we start testing to end or in other word it is"Overall journey of testing from start to end"
Software Testing Life Cycle (STLC) Following Various Phase
 |
| Software testing life cycle (STLC) |
First we understand the following term meaning
SRS-Software Requirement Specification.
In Software testing life cycle (STLC) following various phase are included
Let's See One By One Phase And Their Role In STLC
1.Test Initiation
In Software testing life cycle (STLC) testing start with the test Initiation stage PM(Project Manager) play an important role in this stage.
During test Initiation phase PM is going to concentrate on following three things
1) Scope of project
2)Requirement of project
3) Risk of project/Risk involved in project
By considering above three things PM is going to finalize the TRM document TRM means Test responsibility matrix.
After finalize the TRM ,PM forwarded this TRM to test lead i.e TL for further process.
2.Test Plan
After receiving the TRM from PM test lead i.e TL start to prepare Test plan here TL take TRM as input to prepare test plan.During test plan phase
TL (Test Lead) is going to concentrate on following three things
1) Job Allocation.
2) Resource Allocation.
3) Estimation.
By considering this all above three things TL prepare Test plan will be reviewed by project manager and client and after that final test plan document is pass to all team member in pdf format.Test plan every sprint has his own test plan.
Test plan document is reviewed in sprint planning meeting if organization/company follow agile methodologies.
3.Requirement Analysis/SRS Analysis/Requirement understanding
After test plan phase user story/SRS Analysis phase come into the picture after receiving test plan document in sprint planning meeting test engineer start to understand the requirement or start to analysis the requirement.
Once test engineer received test plane he came to know about job allocation on which tester know the which user stories are assign or on which user stories tester should work then tester start understanding the requirement.
During user stories analysis if tester not understand any particular requirement the tester should rich out to there test team member if they are not able to understand the requirement then tester should rich out to test lead if test lead.
Also not solve the problem then teater rich out to developer and then product owner.if issue is still not solve then tester rich out to client with the permission of project manager.
4.Test Scenario Identifications
5.Test Case Design
After test test scenario identifications tester should write the test case design.Test case design means How to test? the application test case design consist of navigational statements important point is that client not problem with the test count he wants only software functionality should get tested.
6.Test Case Review
After test case design test case review come into the picture after writing the test case it is very important to review the test case.
Four types of review
1) Self review:-In self review Test engineer himself/herself is review his own test cases.
2) Peer review:- Peer review is done by test team member.
3) Internal review:-Internal review is done by test team member,dev team member,BA(Business analyst)/PO(Project owner) or it will happen within organization.
4) External review:- In external review client will review the test cases also test team,dev team and BA will also be present there.
In test case review see whether all requirement are covered or not whether test scenarios tester have written should covered test case for it?
Also checking the spelling mistakes if any.If there is any steps missing in test case also review priority of test case should take or not.
7.Preparing Traceability Matrix
After test case review prepare traceability matrix is important traceability matrix where we identified missing test cases."Traceability Matrix is mapping between business requirement and written test cases".
During traceability matrix if tester found any missing test case then tester should add it in traceability matrix to find out missing test cases all are review test cases again and again.traceability matrix also know as RTM(Requirement Traceability Matrix) or RMS(Requirement Mapping Sheet).
Two way to prepare Traceability Matrix
1) Excel sheet
2)HP-ALM (Project Management or Defect Management Tool)
Following are the two types of traceability matrix
2)Backward Traceability Matrix
Backward Traceability Matrix is mapping between business requirement and defect.Backward Traceability Matrix is is prepared after test case execution.
Backward Traceability Matrix column contains Sr.no,Requirement ID,Requirement Name,Defect ID.
8.Test Case Execution
1) Retesting
In retesting test engineer going to check whether bug or defect is fix or not.during resting tester check the modified build which send by developer after fixing the bug.In retesting test engineer is going to concentrate on specific particular functionality where actual bug is occured.
2) Regression Testing
In test case execution after retesting its mandatory to do regression testing also whenever new functionality is added then also do regression testing is mandatory.regression testing is define as
"Whenever their is new functionality is added and whenever there is defect fix then in both this cases there is change in code by developer due to that change in code tester need to check its not effect on existing functionality"
In two condition tester should perform regression testing whenever there is new functionality is added and whenever there is defect fix.
Two times tester need to perform regression testing on every consolidated build/every new build and second is master build.
Following are two types of Regression testing
1) Regional type regression testing
Regional regression testing done with modified module along with impacted module.Here which module is modified and which impacted module is only test here.
2) Full regression regression testing
Full regression regression testing done with main features and also remaining part of the application.In full regression testing which is modified and impacted with all features of application should be tested here.
9.Test Summary Report/Software Release Note
Important Questions Related To Interview/Exam
1)What is STLC?
3.Requirement Analysis/SRS Analysis/Requirement understanding.
4.Test Scenario Identifications.
5.Test Case Design.
6.Test Case Review.
7.Preparing Traceability Matrix.
8.Test Case Execution.
9.Retesting,Regression Testing.
10.Test Summary Report/Software Release Note.
3) What is Traceability Matrix in STLC?
4)Test summary report/Software release note?
Peoples Also Ask This
2. What is software? "and "what are the different types of software?"
5. Phase of Software development life cycle(SDLC)
7.Defect Life Cycle: New, assign, open, defered, fixed
.ico){kind=small}