Software testing life cycle: Difference between revisions
Undid revision 1127185671 by Shubham Patkar MCA (talk) |
Reverting edit(s) by 212.201.44.249 (talk) to rev. 1127185671 by Shubham Patkar MCA: Vandalism (from contribs) (RW 16.1) |
||
Line 1: | Line 1: | ||
'''Software testing life cycle |
'''Software testing life cycle ( STLC )''' |
||
The procedure or process of software testing is also known as an STLC. |
|||
* [[Software testing]] |
|||
Testing processes are executed in a well-planned and systematic manner. |
|||
* [[Software development life cycle]] |
|||
All activities are to be done to improve the quality of the software product. |
|||
* [[Software release life cycle]] |
|||
'''Criteria for testing -''' |
|||
What to test (what features are tested or what features aren't tested ) |
|||
How to test ( what kind of testing is conducted like- regression, sanity, smock ) |
|||
When to test (timeline or schedule) |
|||
'''Steps for software testing life cycle''' |
|||
{{Disambiguation}} |
|||
Requirement analysis |
|||
Test plan |
|||
Test cases design and development |
|||
Test execution |
|||
Defect reporting and tracking |
|||
Test cycle closure |
|||
'''1. Requirement analysis''' |
|||
Software with SRS document |
|||
'''2. Test Planning''' |
|||
* Input for test plan |
|||
Project plan (done by the product manager, high-level document) |
|||
Functional requirement |
|||
* Activity for test plan |
|||
Identify the resources (software and hardware resources ) |
|||
Team formation (testing team) |
|||
Test estimation (estimate time entire process) |
|||
Preparation of test plan |
|||
Review of test plan |
|||
Test plan sign-off (signoff email and proceed further phase ) |
|||
* who is take Responsibility |
|||
Test lead/ team lead |
|||
Test manager |
|||
* Outcome |
|||
Test plan document (input activity, responsibility,) |
|||
'''Test case design/development (writing the test cases)''' |
|||
* Input for test case design/development |
|||
Project plan (timeline ) |
|||
Functional requirement (features, behavior, main doc) |
|||
Test plan (features test or not ) |
|||
Design docs ( UI ) |
|||
Use cases (part of functional requirement ) |
|||
* Activity for test case design |
|||
Preparation of test scenarios ( like login scenario giving id and password according to a situation like wrong data or correct data ) |
|||
Preparation of test cases (multiple test cases for 1 scenario) |
|||
Review on test cases (check, modify, update test cases) |
|||
Traceability matrix (what requirements are covered or not) |
|||
Test cases sign-off (send email this phase is done) |
|||
* who is take Responsibility |
|||
Test lead/ team lead |
|||
Test engineers |
|||
* Outcome |
|||
Test cases documents |
|||
Traceability matrix document |
|||
'''Test case execution ( Defect / Bug Reporting & tracking )''' |
|||
* Input for test case execution |
|||
Functional requirements (document ) |
|||
Test plan (doc) |
|||
Test cases (doc) |
|||
Build from the development team (multiple build releases when fixing bugs or adding new features ) |
|||
* Activity for test case execution |
|||
Executing test cases |
|||
Preparing of test report/ test log |
|||
Identifying defects |
|||
* who is take Responsibility |
|||
Test lead/ team lead |
|||
Test engineers |
|||
* Outcome |
|||
Status/test reports |
|||
'''Defect Reporting and tracking''' |
|||
* Input for defects reporting and tracking |
|||
Test cases |
|||
Test reporting/test log (defects list report prepared) |
|||
* Activity for defects reporting and tracking |
|||
Preparation of defect report |
|||
Reporting defects to developers |
|||
* who is take Responsibility |
|||
Test lead/team lead |
|||
Test Engineer |
|||
* Outcome |
|||
Defect reports |
|||
'''Test cycle closure''' |
|||
* Input for test cycle closure |
|||
Test cases |
|||
defects reports (review of defects) |
|||
* Activity for test cycle closure |
|||
Analyzing test reports |
|||
Analyzing bug reporting |
|||
Evaluation exit criteria |
|||
* who is take Responsibility |
|||
Test lead/team lead |
|||
Test Engineer |
|||
* Outcome |
|||
Test summary reports |
|||
writer: Shubham Patkar |
Revision as of 19:48, 5 April 2024
Software testing life cycle ( STLC )
The procedure or process of software testing is also known as an STLC. Testing processes are executed in a well-planned and systematic manner. All activities are to be done to improve the quality of the software product. Criteria for testing - What to test (what features are tested or what features aren't tested ) How to test ( what kind of testing is conducted like- regression, sanity, smock ) When to test (timeline or schedule)
Steps for software testing life cycle
Requirement analysis Test plan Test cases design and development Test execution Defect reporting and tracking Test cycle closure
1. Requirement analysis
Software with SRS document
2. Test Planning
- Input for test plan
Project plan (done by the product manager, high-level document) Functional requirement
- Activity for test plan
Identify the resources (software and hardware resources ) Team formation (testing team) Test estimation (estimate time entire process) Preparation of test plan Review of test plan Test plan sign-off (signoff email and proceed further phase )
- who is take Responsibility
Test lead/ team lead Test manager
- Outcome
Test plan document (input activity, responsibility,)
Test case design/development (writing the test cases)
- Input for test case design/development
Project plan (timeline ) Functional requirement (features, behavior, main doc) Test plan (features test or not ) Design docs ( UI ) Use cases (part of functional requirement )
- Activity for test case design
Preparation of test scenarios ( like login scenario giving id and password according to a situation like wrong data or correct data )
Preparation of test cases (multiple test cases for 1 scenario)
Review on test cases (check, modify, update test cases)
Traceability matrix (what requirements are covered or not)
Test cases sign-off (send email this phase is done)
- who is take Responsibility
Test lead/ team lead Test engineers
- Outcome
Test cases documents Traceability matrix document
Test case execution ( Defect / Bug Reporting & tracking )
- Input for test case execution
Functional requirements (document ) Test plan (doc) Test cases (doc)
Build from the development team (multiple build releases when fixing bugs or adding new features )
- Activity for test case execution
Executing test cases Preparing of test report/ test log Identifying defects
- who is take Responsibility
Test lead/ team lead Test engineers
- Outcome
Status/test reports
Defect Reporting and tracking
- Input for defects reporting and tracking
Test cases Test reporting/test log (defects list report prepared)
- Activity for defects reporting and tracking
Preparation of defect report Reporting defects to developers
- who is take Responsibility
Test lead/team lead Test Engineer
- Outcome
Defect reports
Test cycle closure
- Input for test cycle closure
Test cases defects reports (review of defects)
- Activity for test cycle closure
Analyzing test reports Analyzing bug reporting Evaluation exit criteria
- who is take Responsibility
Test lead/team lead Test Engineer
- Outcome
Test summary reports
writer: Shubham Patkar