What is Software Testing Life Cycle (STLC)

Software Testing Life Cycle:

Software Testing Life Cycle (STLC) identifies what test activities to carry out and when to accomplish those test activities. Even though testing differs between organizations, there is a testing life cycle.

Don’t Miss: Manual Testing Complete Tutorial


STLC - Software Testing Life Cycle
The different phases of Software Testing Life Cycle are:

Dont miss: Difference between SDLC & STLC

Every phase of STLC (Software Testing Life Cycle) has a definite Entry and Exit Criteria.

Check out the below video to watch “Software Testing Life Cycle Phases (STLC Phases)”

Please be patient. The video will load in some time.


Requirement Analysis:

The entry criteria for this phase is the BRS (Business Requirement Specification) document. During this phase, test team studies and analyzes the requirements from a testing perspective. This phase helps to identify whether the requirements are testable or not. If any requirement is not testable, the test team can communicate with various stakeholders (Client, Business Analyst, Technical Leads, System Architects, etc) during this phase so that the mitigation strategy can be planned.

Entry Criteria: BRS (Business Requirement Specification)
Deliverables: List of all testable requirements, Automation feasibility report (if applicable)


Test Planning:

Test planning is the first step of the testing process. In this phase typically Test Manager/Test Lead involves determining the effort and cost estimates for the entire project. Preparation of the Test Plan will be done based on the requirement analysis. Activities like resource planning, determining roles and responsibilities, tool selection (if automation), training requirement, etc., carried out in this phase. The deliverables of this phase are Test Plan & Effort estimation documents.

Must Read: Test Strategy In Deapth Explanation

Entry Criteria: Requirements Documents
Deliverables: Test Strategy, Test Plan, and Test Effort estimation document.

Must Read: How To Write A Good Test Plan


Test Design:

The test team starts with test case development activity here in this phase. Test team prepares test cases, test scripts (if automation), and test data. Once the test cases are ready then these test cases are reviewed by peer members or team lead. Also, the test team prepares the Requirement Traceability Matrix (RTM). RTM traces the requirements to the test cases that are needed to verify whether the requirements are fulfilled. The deliverables of this phase are Test Cases, Test Scripts, Test Data, Requirements Traceability Matrix

Entry Criteria: Requirements Documents (Updated version of unclear or missing requirement)
Deliverables: Test cases, Test Scripts (if automation), Test data.

Must Read: How To Write Test Cases


Test Environment Setup:

This phase can be started in parallel with the Test design phase. The test environment setup is done based on the hardware and software requirement list. In some cases, the test team may not be involved in this phase. The development team or customer provides the test environment. Meanwhile, the test team should prepare the smoke test cases to check the readiness of the given test environment.

Entry Criteria: Test Plan, Smoke Test cases, Test Data
Deliverables: Test Environment. Smoke Test Results.


Test Execution:

The test team starts executing the test cases based on the planned test cases. If a test case result is Pass/Fail then the same should be updated in the test cases. The defect report should be prepared for failed test cases and should be reported to the Development Team through a bug tracking tool (eg., Quality Center) for fixing the defects. Retesting will be performed once the defect was fixed. Click here to see the Bug Life Cycle.

Entry Criteria: Test Plan document, Test cases, Test data, Test Environment.
Deliverables: Test case execution report, Defect report, RTM

Must Read: How To Write An Effective Defect Report


Test Closure:

The final stage where we prepare Test Closure Report, Test Metrics.
The testing team will be called out for a meeting to evaluate cycle completion criteria based on Test coverage, Quality, Time, Cost, Software, Business objectives. Test team analyses the test artifacts (such as Test cases, Defect reports, etc.,) to identify strategies that have to be implemented in the future, which will help to remove process bottlenecks in the upcoming projects. Test metrics and Test closure report will be prepared based on the above criteria.

Entry Criteria: Test Case Execution report (make sure there are no high severity defects opened), Defect report
Deliverables: Test Closure report, Test metrics

Must Read: Test Metrics

Like this post, please share it with your friends. If you have any questions, please comment below.

Related Posts:

STLC - Software Testing Life Cycle

Get our latest blog posts delivered to your inbox

Subscribe and get popular blog posts about software testing industry.


3 thoughts on “What is Software Testing Life Cycle (STLC)”

  1. In test execution phase, forgot to provide a URL for bug life cycle. I think, I did static testing(review) here 🙂 Good explanation, Thank you.

    • and its a low severity defect

      • Hi Geetanjali. Thanks for pointing out. 🙂 Your inputs are welcome. Keep visiting.

Leave a Comment

Share via
Copy link
Powered by Social Snap