Software Testing Life Cycle: Diagram, Definition, Template

 What  Is Software Test Life Cycle?

  • Software Test Life Cycle consist of different activities performed by testing team to ensure quality of the software or the application.
  • Software Test Life Cycle starts as soon as we get the Requirement Documents from the end user.
  • When the development of the application is over , testers are ready with the test cases and start with test case execution. This helps us to find bugs in the starting phase.
  • Let us understand Software Test life cycle with the help of diagram.
  • System Study: When requirement document is ready and shared by the end user then the testing team start high level study of the application under test.

  • Write Test Plan: It consist of future testing activities to be done like number of resources required , Types of testing to be done, Test estimation etc.
  • Write Test Cases: In this phase all the end to end test cases of each and every module of the application is written.
  • Prepare Traceability Matrix: After we write the test cases, we do reverse mapping of test cases against the requirement document to ensure for each and every requirement there is atleast one test case written which can be executed, by doing this it give us minimum coverage.
  • Defect Tracking : Once all the test cases are executed and there are defects found in the application then those defects are reported to the developers , Defects are reported using different defect tracking tools like: Bugzilla, Mantis, Jira etc.
  • Prepare Summary Report or Software Test Coverage Matrix: STCM Report consist of overall report of the testing like number of test cases executed, number of test cases pending, number of test cases passed, number of test cases executed. Based on STCM report end user finds it easy to verify quality product is developed or not.
  • Sample summary report:

Module

Description

% Test case executed

% Test case passed

Test cases pending

Priority

Login

Verify customer login

100%

100%

0

High

signup

Verify customer signup

100%

100%

0

High

Delete customer

Verify customer delete

100%

100%

0

High

Edit profile

Verify edit profile

100%

100%

0

High

upload profile

Verify profile picture upload

100%

100%

0

High

Add friend

Verify user is able to add friends

100%

100%

0

High


  • Retrospect Meeting: In this meeting, we identify what went right and what went wrong, so that next time in the project we can avoid wrong things but then we will keep on doing the right things. By doing this we be sure that next time the process will be much more better.



Comments

Popular posts from this blog

Test Case Design Technique in Software Testing With Examples

What is smoke testing?How to perform smoke testing?Difference between smoke and sanity?

Test Cases and Test scenarios: Definition, Examples, Template