What is Software Testing Life Cycle (STLC)?

 What is Software Testing Life Cycle  (STLC)?

A software testing life cycle is a process that outlines the various phases and activities involved in testing software applications to ensure their quality, functionality, and reliability.

Here are the typical phases of STLC:



1. Requirements analysis

In this phase, the QA team studies the SRS (software requirement specification) from a testing perspective. They communicate with various stakeholders to clarify questions about testability. They also evaluate the possibility of automation.

Deliverables:
  • List of all testable requirements
  • Automation study report

2. Test Planning

In this phase, the test manager or the test lead will prepare a detailed plan for testing. Activities include determining the testing strategy, choosing the automation tools, and resource planning.

Deliverables:
  • Test strategy
  • Test Plan
  • Test effort and cost estimation report

3. Test Development

In this phase, testers prepare test cases, test automation scripts, and test data. Peers and the team lead review the test cases once they are ready. 

Deliverables:
  • Test cases
  • Test automation scripts
  • Test data
  • RTM

4. Test Environment Setup

In this step, the QA team sets up the software environment based on the hardware and software specifications. If the software is multi-platform, the team will create multiple such environments.

You can start this phase alongside the Test Development phase.

5. Test Execution

The test team starts executing the test cases based on the test plan. Test cases are marked as passed or failed, and corresponding defect reports are prepared and filed in a bug-tracking tool. 

Once a test run is complete, the product manager will determine if the defects are acceptable or if another round of testing is required, in which case the testers will retest once developers fix the bugs.

Deliverables:
  • Test run execution reports
  • Defect reports

6. Test Closure

Once all the critical issues have been fixed and tested, testing is said to have been completed.

The test team analyzes test artifacts like test cases for improvements in the future or other projects.

A final test closure report that includes all the test metrics of interest is prepared and signed off.

Comments

Popular posts from this blog

What is compatibility tests and how are they performed?

How to create a GitHub repository?