Skip to main content

What is STLC ? What is Software Testing Life Cycle ?






 Software Testing Life Cycle:  

- Software Testing Life Cycle is a process of  different activities which is performed in a systematic manner that are used to perform for the different type of testing activities of the Software/Application.
- STLC defines a series of activities conducted to perform the "Software Testing."

STLC is carried out in five different phases:

1. Test Plan and Control
2. Test Requirement Analysis and Design
3. Test Implementation and Execution
4. Evaluating Exit Criteria and Reporting
5. Test Closure


Phases of STLC:

 STLC Cycle



1. Test Plan and Control:

- In test Planning, the planning of all the testing activities is getting done.
- Test plan helps to identify the Scope of testing (i.e. What to be tested? What not to be tested? What resources are required? Any training is required?)
- We can create the test plan with the help of "SRS, Development Plan, and Project Plan."
- Test Plan is important to avoid random testing or to miss to random testing activities.
- Test Plan is to get done by the Test Manager/Test Lead.
- Test control measures and analyze the result of review and testing.
- Test control prepares the Documentation, Monitoring and Exit criteria.


Input- "SRS Documents", "Development Plan", and "Project Plan"

Output- Test Plan Document and Scope of testing.

2. Test Requirement Analysis and Design- 

- This phase of STLC defines "What's to be tested?"
- In this phase different scenarios are to be defined depends on the condition.
- Senior Testers do the Analysis with the  help of SRS  and Design Templates.


Input- "SRS Document" and "Design Templates"

Output- Test Scenario (What to be tested ?)


3. Test Implementation and Execution:

- In this phase Senior Tester is going through the Test Scenario and create a new document known as "Test Case".
- The created test cases are given to the junior tester to execute the test case.
- Junior tester executes the test cases  and  check there is a defect  in the software or not?
- After testing the software and then create the defect report and also mention in the execution log.

Input- "SRS Document" and "Test Scenario"

Output- Test case Execution and Execution Report

4. Evaluating Exit Criteria and Reporting:

- In this phase STLC defines where to stop the software testing activities.
- After the successful installation of the software, exit criteria has been decided.
e.g. (i) 100% Coverage: It means software should be passed all the testing work properly with no error and software need to work smoothly.
(ii) 80% - 20%  Coverage: It means 80% of the total software should complete the testing activities and remaining 20% of testing activities can allowed with minor defects only.

Input- Test case execution report

Output- Testing activities are get done

5. Test Closure:

- In the Test Closure all the testing activities which are done that we can close the testing activities with the permission of senior management.
- After that, submit the all documents to the management  for the future reference and their documents are known as "Test Deliverable"

Input- Instruction of closing testing activities

Output- Closing of test case and submitting Test report


Popular posts from this blog

What is SDLC ? What is Software Development Life Cycle ?

Software Development Life Cycle ( SDLC )- SDLC is a process used to design, Develop and Test higher quality software. SDLC has the six phases to complete the cycle process. 1. Requirement Gathering and Analysis 2. Design 3. Coding 4. Testing 5. Deployment / Installation 6. Maintenance Phases of SDLC: SDLC Cycle 1. Requirement Gathering and Analysis:     In requirement gathering, it it the formal interaction between the Business Analyst (BA) and Client. Here Business Analyst collects the required data from the customer/Client   as per the client business needs an creates the documents of requirements and this document is known as BRS document (Business Requirement Specifications). And this document is provided to the analyst team. Once the requirement gathering is done System Analyst (SA) analyze the required data and create a product document in a technical language and this document is known as SRS document (Software Require...