Software Testing Life Cycle

 STLC stands for Software Testing Life Cycle. STLC is a sequence of different activities performed by the testing team to ensure the quality of the software or the product.

Requirement Study/System Study: 

When the requirement is ready and shared by the stakeholders (Product Owner/Client), the testing team starts the high-level analysis.

Write Test Plan: 

The testing team plans the strategy and approach to testing the project.

Write Test Cases:

In this phase test cases are created using the given requirement & the test case phases are classified into 6 steps.

First step will be identifying the possible test scenario. Based on the created test scenario, test cases are created. After creating test cases, created test cases are forwarded to the test lead to review the created test cases. Test cases will be reviewed by the test lead and if there is any correction test lead will forward the test case to the tester to correct the test cases using the review comments. After the correction using the review comments, the test case should be again forwarded to the test lead and after again reviewing the test cases it will be approved. The reviewed test cases should be stored in the repository

For eg: Jira or test link.

Traceability Matrix:

Traceability Matrix or Requirement Traceability Matrix should be created based on the created test cases. The tester should match each requirement with each test case. The tester should ensure that each requirement has at least one test case.

Test Execution:

 This phase created/reviewed test case must be executed on the app. 

Defect Tracking:

After the test case execution, if there is any defect it should be raised in the given bug tracking tool.

Test Execution Report:

This is a communication sent out to establish transparency to the QA team’s activities of the day during the Test cycle – including both Defect information and Test case run information. 

Retrospective Meeting:

Retrospective meetings occur at the end of each sprint to help teams pause and think about improving future performance. It's a safe space for reviewing the project's successes, identifying opportunities for process improvement, and solving issues that may have come up.