STLC (Software Testing Life Cycle)

STLC stands for Software Testing Life Cycle. It is a set of activities or phases that are followed during the testing process of a software application. The main purpose of STLC is to ensure that the software being developed undergoes thorough and effective testing before it is released to the users.

The typical phases of STLC include:

  • Requirement Analysis:
    • Understand and analyze the software requirements.
  • Test Planning:
    • Develop a detailed test plan, including test objectives, scope, resources, schedule, and testing activities.
  • Test Case Development:
    • Create detailed test cases based on the requirements and test plan.
  • Test Environment Setup:
    • Set up the test environment with the required hardware, software, and network configurations.
  • Test Execution:
    • Execute the test cases, report defects, and collect test results.
  • Test Closure/Sign-Off:
    • Analyze test reports, defect reports, and evaluate exit criteria to decide whether testing is complete.

STLC PHASES:

Requirement Analysis:

Entry Criteria:

    • Approved project plan.

Input Documents:

    • Software requirements specification.

Activities:

    • Understand and analyze the requirements.

Who is Involved:

    • Testers, Business Analysts, and Developers.

Output Documents:

    • Requirement Traceability Matrix (RTM), identified testable features.

Exit Criteria:

    • Approved Requirement Traceability Matrix.

Test Planning:

Entry Criteria:

    • Approved Requirement Traceability Matrix.

Input Documents:

    • Requirements document, RTM.

Activities:

    • Develop a detailed test plan, identify resources, and form the testing team.

Who is Involved:

    • Test Managers, Testers.

Output Documents:

    • Test Plan document.

Exit Criteria:

    • Approved Test Plan document.

Test Case Development:

Entry Criteria:

    • Approved Test Plan.

Input Documents:

    • Requirements document, Test Plan.

Activities:

    • Create detailed test cases based on the test plan and requirements.

Who is Involved:

    • Testers.

Output Documents:

    • Test Cases.

Exit Criteria:

    • Approved Test Cases.

Test Environment Setup:

Entry Criteria:

    • Completed Test Cases.

Input Documents:

    • Test Cases, Test Plan.

Activities:

    • Set up the test environment with required configurations.

Who is Involved:

    • Testers, System Administrators.

Output Documents:

    • Ready-to-test environment.

Exit Criteria:

    • Completed Test Environment Setup.

Test Execution:

Entry Criteria:

    • Completed Test Environment Setup.

Input Documents:

    • Test Cases, Test Plan.

Activities:

    • Execute test cases, report defects, and collect test results.

Who is Involved:

    • Testers.

Output Documents:

    • Test Execution Reports, Defect Reports.

Exit Criteria:

    • Test execution completed, and test results reviewed.

Test Closure/Sign-Off:

Entry Criteria:

    • Completed Test Execution.

Input Documents:

    • Test Execution Reports, Defect Reports.

Activities:

    • Summarize testing activities, prepare closure reports, and gather lessons learned.

Who is Involved:

    • Testers, Test Managers.

Output Documents:

    • Test Closure Report, Lessons Learned document.

Exit Criteria:

    • Test closure reports approved, and all identified issues addressed.

Followers