The STLC: the testing life cycle

In the last lesson we zoomed out and saw the whole journey of building software, the SDLC. Now we zoom in on one box of that picture, the testing box, and discover it has a whole life cycle of its own. It's called the Software Testing Life Cycle, or STLC, and it turns "go test the thing" into an organised, professional sequence of steps.

Why bother with a structured cycle instead of just clicking around? Because organised testing is repeatable, explainable, and far less likely to miss something important. When a manager asks "are we ready to test?" or "are we done testing?", the STLC gives you a real answer instead of a shrug.

The six phases of the STLC

1. 1

   Requirement analysis

   Study what's being built and figure out what's worth testing. You read the requirements, ask questions about anything fuzzy, and decide what's actually testable. A vague requirement is a gift here, because catching it now is far cheaper than catching it later.

2. 2

   Test planning

   Decide the strategy: what you'll test, what you won't, how much time and how many people it takes, what tools you'll use, and what counts as "done". The output is a test plan. This is the brain of the whole cycle.

3. 3

   Test case development

   Write the specific tests: the exact steps, the data to use, and the result you expect each time. A good test case is so clear that someone else could run it and get the same answer.

4. 4

   Test environment setup

   Prepare the place where tests will actually run: the right servers, browsers, devices, accounts, and sample data. A test is only as trustworthy as the environment it runs in.

5. 5

   Test execution

   The hands-on part. Run the test cases, compare what happened to what you expected, and log every difference as a defect. Pass, fail, or blocked: each result gets recorded.

6. 6

   Test cycle closure

   Wrap up. Summarise what was tested, what passed and failed, what's still open, and what you'd do better next time. This is where a team actually learns, instead of repeating the same mistakes.

Entry and exit criteria: the gates between phases

Here's the idea that makes the STLC feel professional rather than chaotic. Each phase has entry criteria (what must be true before you're allowed to start it) and exit criteria (what must be true before you're allowed to call it finished). Think of them as the bouncers at the door of each phase: you don't get in until you're ready, and you don't leave until you're done.

Don't confuse the SDLC and the STLC, because the names are so similar. The SDLC is the life cycle of building the whole product. The STLC is the life cycle of the testing effort inside it. The STLC lives inside the testing phase of the SDLC, the way a chapter lives inside a book.