What is STLC in Software Testing? The 6 Phases Explained (2026)

Last updated: July 11, 2026 · 9 min read

The Software Testing Life Cycle (STLC) is the structured process QA teams follow across every release. This guide walks through all six phases with entry and exit criteria, and shows how STLC fits inside the broader SDLC. Complements our Manual Testing Complete Guide.

STLC is a systematic, phase-based approach to testing software. Each phase has defined entry and exit criteria, deliverables, and owners. Following STLC keeps testing predictable, traceable, and audit-ready — which is why regulated industries (fintech, healthtech, aviation) rely on it.

1. Requirement Analysis — QA reads BRD/PRD, identifies testable and non-testable requirements, raises ambiguity queries.
2. Test Planning — Test Lead writes the test plan: scope, approach, resources, schedule, risks.
3. Test Case Design — QAs write test cases and prepare test data. Traceability matrix links each requirement to test cases.
4. Test Environment Setup — DevOps/QA provisions servers, test data, integrations. Smoke test confirms environment is testable.
5. Test Execution — Tests are run (manual + automated). Defects logged, retested, and closed. Daily status reports.
6. Test Closure — Metrics compiled (coverage, defect density, escape rate), retrospective run, artifacts archived.

SDLC is the entire software delivery process — requirements, design, build, test, deploy, maintain. STLC is the testing slice that runs inside SDLC. In agile teams, STLC phases compress and overlap: analysis and case design happen inside a two-week sprint, closure at sprint end.

• Requirement analysis happens in the Three Amigos meeting (PM + Dev + QA).
• Test planning becomes a lightweight test strategy per sprint or per epic.
• Case design uses BDD/Gherkin (Cucumber docs).
• Execution shifts left — unit tests on every commit, regression nightly.
• Closure becomes continuous — dashboards, not documents.

• Requirement Traceability Matrix (RTM)
• Test Plan document
• Test cases and test data
• Test execution report
• Defect report
• Test summary / closure report

• What is a Test Plan?
• Defect Life Cycle
• Manual Testing Complete Guide

The classic 6-phase STLC (Requirement Analysis → Test Planning → Test Case Design → Environment Setup → Test Execution → Closure) reads like a waterfall document. Below is how each phase actually maps to a 2-week Agile sprint at a modern product company.

Entry and exit criteria — the discipline that separates STLC from ad-hoc testing

Every phase has explicit entry and exit criteria. Skip them and testing becomes reactive:

• Entry criteria for execution: preview env green, test data seeded, feature flag on, monitoring in place.
• Exit criteria for execution: 100% acceptance criteria covered, zero P0/P1 open, flake rate <2%, one exploratory session documented.
• Exit criteria for closure: release notes published, escaped-defect log updated, retro action items assigned owners.

STLC vs SDLC — the one-line answer that lands in interviews

SDLC is the full software delivery cycle (requirements → design → code → test → deploy → maintain). STLC is the testing subset, executed in parallel with SDLC in modern Agile teams — not as a downstream phase.

Common interview follow-ups

1. Which STLC phase produces the highest ROI? — Requirement analysis. A defect caught in 3-amigos costs 100x less than one caught in production.
2. Which phase gets skipped most often? — Test closure. Teams ship and move on without a retro on escaped defects.
3. Who owns entry/exit criteria? — The QA lead drafts them, engineering + product ratify them at sprint planning.

Original SoftwareTestPilot research relevant to manual QA:

• Login-page test coverage benchmarks (2026) — which coverage areas ship real production defects.
• Test pyramid benchmarks (2026) — real ratios vs the Cohn model.
• Shift-left benchmarks (2026) — defect cost by lifecycle stage.
• QA salary benchmarks (2026) and QA jobs hiring now.