- Year not given
Test life cycle in quality control
Short answer
The test life cycle (STLC) is the sequence: requirement analysis, test planning, test design, environment setup, test execution, defect reporting, and test closure. It organizes systematic defect finding, with deliverables such as RTM, test plan, test cases, test logs, defect reports, and a summary report.
What do you mean by test life cycle in the quality control process?
The test life cycle (Software Testing Life Cycle, STLC) is a sequence of specific activities performed during the testing process to ensure quality goals are met. In quality control it organises testing so that defects are found systematically. It runs in parallel with the SDLC.
Requirement analysis -> Test planning -> Test design
-> Environment setup -> Test execution
-> Defect reporting -> Test closure
Phases
- Requirement analysis (test analysis)
- Study requirements to identify testable items; clarify unclear ones.
- Output: list of test conditions, requirement traceability matrix (RTM).
- Test planning
- Define scope, objectives, strategy, resources, schedule, tools, risks, entry/exit criteria.
- Output: test plan, effort estimate.
- Test case design / development
- Write test cases with input, steps, expected result; prepare test data.
- Review test cases.
- Test environment setup
- Prepare hardware, software, network and test data; smoke test the environment.
- Test execution
- Run tests, compare actual with expected results, log pass/fail.
- Defect reporting and tracking
- Log defects with severity and priority, assign to developers, retest after fix, regression testing.
- Defect states: new, assigned, fixed, retested, closed or reopened.
- Test closure
- Evaluate exit criteria, prepare test summary report, metrics (defect density, coverage), lessons learned, archive testware.
| Phase | Deliverable |
|---|---|
| Analysis | RTM |
| Planning | Test plan |
| Design | Test cases |
| Setup | Ready environment |
| Execution | Test logs |
| Reporting | Defect reports |
| Closure | Summary report |
Importance
Gives a structured, repeatable and measurable approach; supports early defect detection; clear entry and exit criteria prevent premature release.
Example: For an online exam portal, testers map requirements to 120 test cases, run them on a staging server, log 35 defects, retest fixes and issue a test summary before release.
✓ Answer checked by Claude Opus 5.5 (high effort)
Related questions
- Quality control process · ICT Project Management, chapter 10
- Project development life cycle phases · ICT Project Management, chapter 1
- Testing IT systems in quality control · ICT Project Management, chapter 10
- Product versus project life cycle · ICT Project Management, chapter 4
- System development life cycle · ICT Project Management, chapter 4
- Project life cycles in detail · ICT Project Management, chapter 4
- Quality control at site; slump test · Concrete Technology and Masonry Structure, chapter 3
- Control cycle; quality control factors · Project Engineering, chapter 4 · asked 2×
- Quality control of concrete at site · Concrete Technology and Masonry Structure, chapter 5 · asked 11×
- Life cycle phases and goal setting example · Project Engineering, chapter 1