Guides › Software Testing & QA
Software Testing Life Cycle (STLC): Complete Guide
Learn the Software Testing Life Cycle (STLC), its phases, entry and exit criteria, deliverables, real-world examples, and QA best practices.
Software Testing Life Cycle (STLC): Complete Guide
The Software Testing Life Cycle (STLC) is a structured process used by software testing teams to plan, prepare, execute, and complete testing activities.
It helps QA engineers understand what needs to be tested, how testing should be performed, when defects should be reported, and how testing results should be evaluated.
In this guide, you will learn the phases of STLC, important activities, entry and exit criteria, deliverables, practical examples, interview questions, and best practices.
Table of Contents
- What Is STLC?
- Why Is STLC Important?
- STLC vs SDLC
- Phases of STLC
- Entry and Exit Criteria
- STLC Deliverables
- Real-World STLC Example
- STLC in Agile Development
- Common STLC Challenges
- STLC Best Practices
- Practical Exercises with Solutions
- STLC Interview Questions
- Frequently Asked Questions
- Conclusion
1. What Is STLC?
STLC stands for Software Testing Life Cycle.
It is a sequence of testing activities performed to verify software quality and determine whether an application meets its requirements.
STLC focuses specifically on testing activities, whereas the broader software development process includes requirements, design, development, testing, deployment, and maintenance.
Example
Suppose a team is developing an online shopping website.
The QA team needs to test:
- User registration and login.
- Product search.
- Shopping cart functionality.
- Payment processing.
- Order confirmation.
- Website compatibility.
- Error handling.
Instead of testing randomly, the team follows a structured process to understand requirements, prepare test cases, execute tests, report defects, and summarize the results.
That structured testing process is STLC.
Main Objectives of STLC
- Identify defects as early as possible.
- Ensure requirements are testable.
- Prepare an effective testing strategy.
- Improve test coverage.
- Track defects systematically.
- Provide reliable information about software quality.
- Reduce the risk of releasing faulty software.
2. Why Is STLC Important?
STLC gives testing teams a repeatable and organized way to perform QA activities.
Benefits of STLC
1. Better planning
The team defines the testing scope, resources, schedule, and responsibilities before execution.
2. Improved test coverage
Requirements are mapped to test scenarios and test cases to reduce the chance of missing important functionality.
3. Early defect detection
Reviewing requirements and designs can reveal ambiguities before development is complete.
4. Clear responsibilities
Team members understand who prepares test cases, configures environments, executes tests, and manages defects.
5. Better reporting
Test execution results and defect reports help stakeholders understand progress and remaining risks.
6. More efficient testing
Planning and prioritization help teams focus on the most important areas first.
7. Improved release decisions
Testing summaries provide evidence that can support release decisions, although testing alone cannot guarantee defect-free software.
3. STLC vs SDLC
STLC and SDLC are related, but they have different scopes.
SDLC stands for Software Development Life Cycle. It covers the broader process of building and maintaining software.
STLC focuses on the testing activities performed within that process.
| Feature | STLC | SDLC |
|---|---|---|
| Full form | Software Testing Life Cycle | Software Development Life Cycle |
| Main focus | Testing and quality verification | Developing and maintaining software |
| Activities | Test planning, test design, execution, defect tracking | Requirements, design, development, testing, deployment, maintenance |
| Main participants | QA engineers, testers, test leads | Product owners, analysts, designers, developers, testers, operations teams |
| Deliverables | Test cases, test reports, defect reports | Requirements, designs, code, releases, documentation |
| Goal | Evaluate software quality and risks | Deliver and maintain a software product |
How They Work Together
Testing activities often begin while requirements and design are still being developed.
For example, a QA engineer can review login requirements before developers finish implementing the login page.
This allows the team to identify missing requirements and prepare tests earlier.
4. Phases of STLC
STLC is commonly described using six major phases:
- Requirement Analysis
- Test Planning
- Test Case Development
- Test Environment Setup
- Test Execution
- Test Cycle Closure
Organizations may combine, rename, or repeat these phases depending on their development methodology.
Phase 1: Requirement Analysis
In this phase, the QA team studies the requirements to understand what must be tested.
Activities
- Review business and technical requirements.
- Identify testable features.
- Clarify unclear requirements.
- Identify risks and dependencies.
- Determine the types of testing required.
- Identify test data and environment needs.
- Begin mapping requirements to test scenarios.
Example
Requirement:
"A registered user must be able to log in using a valid email address and password."
The QA engineer identifies these scenarios:
- Login with valid credentials.
- Login with an incorrect password.
- Submit the form with empty fields.
- Enter an invalid email format.
- Verify logout and session behavior.
The tester may also ask what should happen after repeated failed login attempts.
Deliverables
- Requirement review notes.
- Initial test scenarios.
- Requirement Traceability Matrix (RTM), where applicable.
- List of testing risks and questions.
Phase 2: Test Planning
During test planning, the team decides how testing will be performed.
The test lead or QA lead often coordinates this phase with the project team.
Activities
- Define testing scope.
- Select testing types and approaches.
- Estimate time and effort.
- Identify required skills and resources.
- Choose testing tools.
- Define responsibilities.
- Identify risks and mitigation strategies.
- Establish entry and exit criteria.
- Plan the testing schedule.
Example
For an online shopping website, the team may plan:
- Functional testing for registration, login, cart, and checkout.
- Compatibility testing on supported browsers.
- API testing for product and order services.
- Regression testing after important changes.
- Accessibility checks for critical user journeys.
Test Plan Contents
A test plan may include:
- Project overview.
- Testing objectives.
- Scope and exclusions.
- Test strategy.
- Resources and responsibilities.
- Test environment.
- Schedule and estimates.
- Tools and test data.
- Entry and exit criteria.
- Risks and mitigation plans.
- Reporting procedures.
Deliverables
- Test plan.
- Test estimates.
- Testing schedule.
- Resource plan.
- Risk assessment.
Phase 3: Test Case Development
In this phase, the QA team prepares test cases and the data needed to execute them.
Activities
- Write test scenarios.
- Create detailed test cases.
- Prepare test data.
- Review test cases.
- Map cases to requirements.
- Identify cases suitable for automation.
- Prepare test scripts or checklists when appropriate.
Example
Test Case ID: LOGIN-001
Title: Login with valid credentials
Precondition: An active registered account exists.
Test Data: Valid email and password.
Steps:
- Open the login page.
- Enter the registered email.
- Enter the correct password.
- Click Login.
Expected Result: The user reaches the dashboard.
Deliverables
- Test scenarios.
- Test cases.
- Test data.
- Reviewed test documentation.
- Updated requirement traceability information.
Phase 4: Test Environment Setup
The test environment is the combination of application build, infrastructure, devices, browsers, services, and data used for testing.
Activities
- Configure the test environment.
- Deploy the application build.
- Set up test accounts and permissions.
- Prepare databases and test data.
- Configure external service dependencies.
- Verify environment availability.
- Perform basic smoke checks when a suitable build is available.
Example
For a web application, the QA team may need:
- A staging application.
- Supported browsers.
- Test user accounts.
- A test database.
- A payment sandbox.
- API endpoints and test credentials.
- Access to application logs.
The team should verify that the environment is ready before starting full test execution.
Deliverables
- Configured test environment.
- Environment readiness checklist.
- Test account and data setup.
- Environment issue report, if necessary.
Phase 5: Test Execution
In this phase, testers execute planned test cases and compare actual results with expected results.
Activities
- Execute test cases.
- Record actual results.
- Mark cases as Pass, Fail, Blocked, or Not Run.
- Report defects.
- Attach useful evidence.
- Retest fixed defects.
- Perform regression testing where needed.
- Update test execution status.
Example
Suppose a tester executes three login test cases.
| Test Case | Expected Result | Actual Result | Status |
|---|---|---|---|
| Valid credentials | Dashboard opens | Dashboard opens | Pass |
| Incorrect password | Login rejected | Login rejected | Pass |
| Empty required fields | Validation appears | No validation appears | Fail |
The third test case fails because the observed behavior does not match the expected behavior.
The tester records a defect with clear reproduction steps.
Deliverables
- Test execution results.
- Defect reports.
- Updated test case statuses.
- Retest results.
- Regression test results.
- Testing progress reports.
Phase 6: Test Cycle Closure
Test cycle closure takes place when the planned testing cycle is complete or a defined stopping point is reached.
Activities
- Review executed test cases.
- Summarize passed and failed tests.
- Review open defects.
- Evaluate remaining risks.
- Compare actual results with exit criteria.
- Prepare a test summary report.
- Document lessons learned.
- Identify improvements for future test cycles.
Example
The QA team completes testing for the login feature.
The summary report records:
- Total test cases.
- Passed test cases.
- Failed test cases.
- Blocked and unexecuted cases.
- Open defects by severity.
- Unresolved risks.
- Recommended next steps.
The team then shares the results with relevant stakeholders.
Deliverables
- Test summary report.
- Test closure notes.
- Defect summary.
- Outstanding risk list.
- Lessons learned.
5. Entry and Exit Criteria
Entry and exit criteria define the conditions required to begin or complete a testing phase.
They help teams make decisions based on agreed expectations rather than assumptions.
What Are Entry Criteria?
Entry criteria are the conditions that should be met before a phase begins.
Examples include:
- Requirements are available for review.
- The test plan has been approved.
- Test cases are ready for execution.
- The test environment is accessible.
- Required test data is prepared.
- The application build is deployed.
Not every criterion applies to every phase.
What Are Exit Criteria?
Exit criteria define when a phase or test cycle can be considered complete.
Examples include:
- Planned high-priority tests have been executed.
- Required test coverage has been achieved.
- Critical defects have been resolved or formally accepted as risks.
- Test results have been documented.
- Remaining defects have been reviewed.
- Stakeholders have received the test summary.
Exit criteria depend on project risk, contractual requirements, and release policies.
Example: Login Feature
Entry Criteria:
- Login requirements are approved.
- A test build is available.
- Test accounts are prepared.
- Login test cases are reviewed.
Exit Criteria:
- Required login test cases have been executed.
- Critical login defects have been addressed.
- Failed cases have been investigated.
- Remaining risks have been documented.
- The test summary is available.
A team should not assume that all software is ready for release merely because a particular test phase has ended.
6. STLC Deliverables
A deliverable is a document, record, or other output produced during a testing phase.
| STLC Phase | Common Deliverables |
|---|---|
| Requirement Analysis | Requirement review notes, initial scenarios, RTM |
| Test Planning | Test plan, estimates, schedule, risk assessment |
| Test Case Development | Test cases, test data, test scripts |
| Environment Setup | Environment checklist, readiness status |
| Test Execution | Execution results, defect reports, retest records |
| Test Cycle Closure | Test summary report, outstanding risks, lessons learned |
Deliverables vary between organizations. Agile teams may maintain lighter documentation and track work directly in project tools.
What Is a Requirement Traceability Matrix?
A Requirement Traceability Matrix (RTM) links requirements to test scenarios or test cases.
Its purpose is to help verify that requirements have appropriate test coverage.
Example:
| Requirement ID | Requirement | Test Case ID | Status |
|---|---|---|---|
| REQ-001 | User can log in | LOGIN-001 | Pass |
| REQ-002 | Invalid password is rejected | LOGIN-002 | Pass |
| REQ-003 | Required fields are validated | LOGIN-003 | Fail |
This matrix helps identify requirements that have not been tested or that have failing test cases.
7. Real-World STLC Example: Online Shopping Website
Imagine a team is developing an online shopping website with registration, login, product search, cart, and checkout features.
Phase 1: Requirement Analysis
The QA team reviews the user journeys and identifies test scenarios for each feature.
Example: Users must be able to add available products to their carts.
Phase 2: Test Planning
The team decides which features need functional, compatibility, API, security, and regression testing.
The team also estimates the work and identifies required environments and tools.
Phase 3: Test Case Development
Testers write cases for:
- Registration.
- Login.
- Product search.
- Product details.
- Adding and removing cart items.
- Quantity updates.
- Coupon validation.
- Checkout and order confirmation.
Phase 4: Test Environment Setup
The team prepares a staging website, test accounts, product data, and a payment sandbox.
Phase 5: Test Execution
Testers execute the cases and report defects.
For example, the cart total may not update when a product quantity changes.
The issue is documented and assigned to the development team.
Phase 6: Test Cycle Closure
After the fix, the QA team retests the affected behavior and checks related cart functionality.
The final report summarizes the results, unresolved issues, and remaining risks.
8. STLC in Agile Development
In Agile development, testing is not necessarily a separate activity that begins only after development is complete.
Instead, testing can happen continuously during each sprint.
How STLC Fits into Agile
Backlog Refinement
QA engineers review user stories, acceptance criteria, and potential risks.
Sprint Planning
The team discusses test effort, dependencies, and acceptance requirements.
Development and Testing
Developers and testers collaborate as features are implemented. Testing may occur throughout the sprint.
Continuous Integration
Automated checks may run when code changes are committed or merged.
Sprint Review
The team demonstrates completed work and gathers feedback.
Retrospective
The team identifies ways to improve testing and development practices.
Example
A team develops a registration feature in a sprint.
The QA engineer reviews the requirements, prepares test cases, tests available builds, reports defects, retests fixes, and helps verify acceptance criteria.
The team repeats these activities as the feature evolves.
Agile teams may adapt the traditional STLC phases rather than follow them as rigid sequential stages.
9. Common STLC Challenges
Unclear Requirements
Problem: Requirements do not explain expected behavior.
Solution: Ask questions early and document agreed acceptance criteria.
Limited Testing Time
Problem: The release deadline leaves little time for full testing.
Solution: Prioritize critical user journeys and high-risk functionality, and communicate untested areas.
Unstable Test Environment
Problem: Environment failures prevent reliable execution.
Solution: Establish readiness checks, clear ownership, and a process for reporting environment issues.
Poor Test Data
Problem: Test cases cannot be executed because the required data is missing or invalid.
Solution: Prepare controlled test data and document setup and reset procedures.
Frequent Requirement Changes
Problem: Existing test cases become outdated.
Solution: Review impacted requirements and update relevant tests when changes occur.
Too Many Open Defects
Problem: The team struggles to decide what must be fixed before release.
Solution: Assess severity, priority, user impact, available workarounds, and release risk with the appropriate stakeholders.
Incomplete Test Coverage
Problem: Important scenarios are missed.
Solution: Map requirements to test cases and review positive, negative, boundary, and error-handling conditions.
10. STLC Best Practices
Follow these practices to make testing more effective.
- Involve QA during requirement analysis.
- Define scope and responsibilities clearly.
- Prioritize tests based on risk.
- Write clear and maintainable test cases.
- Link test cases to requirements where appropriate.
- Prepare test data before execution.
- Verify environment readiness.
- Record test results accurately.
- Report defects with reproducible steps.
- Retest fixes and check for regressions.
- Track unresolved defects and risks.
- Share concise test summaries with stakeholders.
- Review the process after each testing cycle.
- Automate suitable repetitive tests when beneficial.
- Never mark unexecuted tests as passed.
11. Practical Exercises with Solutions
Try the exercises before reviewing the suggested answers.
Exercise 1: Identify the STLC Phase
A QA engineer is reviewing requirements and asking questions about how a password-reset feature should behave.
Which STLC phase is this?
Solution: Requirement Analysis.
The engineer is clarifying requirements and identifying testable conditions.
Exercise 2: Test Planning
A team is deciding the testing scope, schedule, tools, resources, and risks for a new website.
Which phase is this?
Solution: Test Planning.
The team is defining how testing will be organized and performed.
Exercise 3: Test Case Development
A tester creates test cases for valid login, incorrect passwords, empty fields, and invalid email formats.
Which phase is this?
Solution: Test Case Development.
The tester is preparing the cases and test data needed for execution.
Exercise 4: Failed Test Case
A test case expects an error message for an invalid password, but the application accepts the password.
What should the tester do?
Solution:
- Confirm the test data and expected behavior.
- Repeat the steps if appropriate.
- Record the actual result.
- Report a defect with reproduction steps.
- Attach relevant evidence.
- Track the defect until it is resolved or otherwise dispositioned.
Exercise 5: Test Closure
The team has completed the planned tests and needs to summarize results, open defects, and unresolved risks.
Which phase is this?
Solution: Test Cycle Closure.
The team reviews the testing outcome and prepares a summary.
Exercise 6: Requirement Traceability
A requirement has no linked test cases.
What is the risk, and what should the team do?
Solution:
The requirement may not have adequate test coverage. The team should review the requirement, create appropriate test scenarios and cases, and update the traceability information.
12. STLC Interview Questions
Q1. What is STLC?
STLC stands for Software Testing Life Cycle. It is a structured set of activities used to plan, prepare, execute, and close testing.
Q2. How many phases are in STLC?
A common model has six phases: Requirement Analysis, Test Planning, Test Case Development, Test Environment Setup, Test Execution, and Test Cycle Closure.
Organizations may use different phase names or structures.
Q3. What is the difference between STLC and SDLC?
SDLC covers the broader software development and maintenance process. STLC focuses on testing activities within that process.
Q4. What happens during Requirement Analysis?
The QA team reviews requirements, identifies testable conditions, clarifies ambiguity, and begins identifying test scenarios and risks.
Q5. What is a test plan?
A test plan documents the testing scope, approach, resources, schedule, risks, responsibilities, and completion criteria.
Q6. What are entry criteria?
Entry criteria are the conditions that should be met before a testing phase begins.
Q7. What are exit criteria?
Exit criteria define the conditions for completing a phase or testing cycle.
Q8. What is a test deliverable?
A test deliverable is an output of testing work, such as a test plan, test case, defect report, or test summary.
Q9. What is an RTM?
A Requirement Traceability Matrix links requirements to test cases or other testing evidence to help track coverage.
Q10. Can STLC be used in Agile?
Yes. Agile teams can adapt STLC activities to continuous development, frequent testing, sprint-based planning, and ongoing feedback.
Q11. What is test closure?
Test closure involves reviewing execution results, defects, remaining risks, and lessons learned, then communicating the testing outcome.
Q12. Is STLC always sequential?
No. Activities can overlap or repeat, particularly in Agile and iterative development environments.
13. Frequently Asked Questions
Is STLC suitable for beginners?
Yes. STLC provides a useful framework for understanding how QA work is planned and organized.
Does STLC start after coding is complete?
No. Testing-related activities can begin during requirements and design reviews, before coding is finished.
Who is responsible for STLC?
QA engineers, testers, test leads, and other project members may contribute. Responsibilities depend on the organization.
Are all STLC documents mandatory?
No. Documentation depends on project size, risk, regulations, contractual requirements, and team practices.
What is the most important STLC phase?
Every phase contributes to quality. Requirement analysis and test planning are particularly valuable because they help teams identify risks and organize effective testing early.
Does STLC guarantee bug-free software?
No. STLC provides a structured way to identify defects and evaluate quality, but it cannot guarantee that all defects will be found.
What should a test summary report contain?
It commonly includes testing scope, execution results, defect status, untested areas, unresolved risks, and recommendations.
14. Conclusion
The Software Testing Life Cycle provides a structured approach to software testing, from understanding requirements to summarizing the final results.
By learning its phases, entry and exit criteria, deliverables, and practical workflows, you can better understand how QA teams organize testing activities.
Practice each phase using a demo application. Create a test plan, prepare test cases, execute them, report defects, and write a test summary.
These skills will help you build a strong foundation for manual testing, automation testing, and a future career in software quality assurance.
Related Guides
- Software Testing: Complete Beginner to Advanced Guide
- Manual Testing: Complete Guide with Examples
- How to Write Test Cases: Examples and Templates
- Bug Reporting and Defect Life Cycle
- Functional vs Non-Functional Testing
- Automation Testing: Complete Beginner Guide
More guides
- How to Use Codify: A 7-Day Start Plan — New here? Pick a roadmap, make a study plan, start the DSA sheet, revise with notes, practise for placements and test yourself — one step a day, then a daily routine.
- Infosys Preparation Guide: Online Test, Pseudocode and Interview — Roles (SE, DSE, SP), what each section of the Infosys online test checks, how to crack pseudocode and reasoning, a 4-week plan and the interview.
- Wipro Elite NLTH Preparation: Aptitude, Essay and Coding — The Wipro fresher test round by round — quant, logical and verbal, the written essay, two coding problems — plus a 3-week plan and interview tips.
- Accenture Preparation Guide: Cognitive, Technical, Coding and Communication — Every Accenture round explained — cognitive, MS Office/networking/cloud technical MCQs, pseudocode, coding and the spoken-English test — with a 4-week plan.