STLC- Software Testing Life Cycle In Software Testing - Phase Of STLC

STLC-Software Testing Life Cycle

STLC Stands for Software testing life cycle, it is a Procedure to test the application,stlc is a subset of SDLC.In the STLC process, different activities are carried out to improve the quality of the product. Software testing is a critical part of preparing software for use, and an STLC helps make this process more sophisticated, consistent, and effective

Phases of STLC

The Various Phases of STLC are 


Software Testing Life Cycle in Software Testing - STLC

  • System Study
  • Prepare Test Plan
  • Write Test Cases
  • Traceability Matrix
  • Test Execution
  • Test Execution Report
  • Retrospect Meeting



System Study -

In this phases the system requirement is given to the testing team what to be tested.they go through requirement and understand and if they have any doubt they contact to the team lead , manager ....to get clearify their doubt.

Prepare Test Plan

Test plan is a document which derives all future activities of the project. All future testing activities is planned and put into a document and this document is known as Test Plan. It contains – number of engineers needed for the project, who should test which feature, how the defects must be communicated to the development team, when we should start and finish writing test cases, executing test cases, what are the types of testing we use to test for the application etc.

Write test case 

we write test cases for each feature. These test cases are reviewed, and after all mistakes are corrected and once the test cases are approved – then they are stored in the test case repository.

Traceability Matrix

 it is a document that ensures that every requirement has a test case.
Test cases are written by looking at the requirements and test cases are executed by looking at the test cases. If any requirement is missed i.e, test cases are not written for a particular requirement, then that particular feature is not tested which may have some bugs. Just to ensure that all the requirements are converted, traceability matrix is written. 

Test Execution:

Defect Tracking 

any bug found by the testing team is sent to the development team. This bug has to be checked by the testing team if it has been fixed by the developers.

Test Execution Report:-

 Send it to the customer – contains a list of bugs(major, minor and critical), a summary of the test pass, fail, etc, and when this is sent, according to the customer – the project is over.
TER is prepared after every test cycle and sent to the development team, testing team, management, and customer(depending on if it is a fixed bid project or a time & material bid project).
The last TER of the last test cycle is always sent to the customer. And this means that the project is over according to the customer.

Retrospect meeting

(also called Post Mortem Meeting / Project Closure Meeting)
The Test Manager calls everyone in the testing team for a meeting and asks them for a list of mistakes and achievements in the project.

Hope !! The above article for STLC (software testing life cycle helpful for you..

Team
QA acharya




Tags: STLC , STLC phases , software testing life cycle.
Related Post:



Team- QA acharya

Previous Post Next Post