What is software testing life cycle (STLC)?
Basically, STLC is the sequential process or activities which is performed by the QA team during the testing phase of the Software Development Life Cycle Process. STLC is the integrated part of Software Development Life Cycle. The aim of the STLC is to maintain the software quality asuurance and to deliver bug free products.
STLC involves verification and validation both.
Why STLC should be performed?
While Product is being developed, QA team analyzes and defines the scope of the testing, Review the Software Requirement Specification document and finds the ambiguity if any which results into the clear idea about the requirement for both team; Development team and QA team, this helps to find the bugs in early stage of software development.
QA team Prepares the Test Plan, Test Strategy, Entry and Exit Criteria, Test Case Development.
Once the software is developed, it is handed over to QA for Testing. Test Case Execution will help to reduce the testing time and improve the software quality which leads to finding the bugs in the early phase.
Different phases of software testing life cycle
Requirement Analysis
This is the very first step of STLC. In this step, the QA team is involved in understanding the requirement to get the idea for In Scope Testing . If any ambiguity finds anything which is not understandable then the team meets with the stakeholders to get the detailed knowledge about the requirement.
Below activities are performed in Requirement Analysis
- Identify types of tests to be performed.
- Gather details about testing priorities, testing focus,
- Prepare RTM(Requirement Traceability Matrix)
- Gather information about the environment details where testing is supposed to be performed.
Test Planning
This is the most important and most efficient phase of STLC. In this Phase, all the testing plans and testing strategies are defined. QA Manager defines the testing estimation time and cost for the Testing work. Moreover, The resources, testing environment, test limitation and test schedule are determined.
Below activities are performed in test planning
- Test Plan Creation
- Test Strategy document
- Test Tool selection
- Test effort estimation
- Resource Planning and determine roles and responsibilities
Test Case Creation
In this Phase, Test case creation takes place. Testing team creates the test cases with details. Also, Prepare the test data for the testing. Once the test case creation is completed, it is reviewed and then reworked based on review comments if any. In this stage, TestData is identified, created and identified. Test Data makes the testing easy and saves the time during testing if data is already identified initially for testing.
Below activities are performed in test case creation
- Test Case creation
- Test Case review
- Identification of Test Data
Test Environment Setup
Test Environment Setup decides the hardware and software conditions under which the software is tested. This phase can be done parallel with the test case development phase. Testing team is not involved in this phase. Development team Provides the testing environment after performing smoke testing of the environment.
Below activities are performed in test environment setup
- Understand the environment setup
- Understand the required architecture
- Prepare Software and hardware requirements list for the environment
- Setup Test Environment and Test Data
- Perform Smoke Test on the given environment
Test Case Execution
Test Case Execution carried out by the testing team once the test case development and test case environment setup is completed based on the prepared test case in earlier stages. It is real-time validation of products and finding bugs. If any bugs are reported then it is reverted back to the development team for correction and retesting will be performed once it is fixed.
Below activities are performed in Test case execution
- Execute Test Case
- Bugs finding and Bugs Reporting
- Retesting
- Link Defects to test case in RTM
- Follow Bug life cycle.
Testing Closure
This is the last stage of STLC in which the process of testing is analyzed. This Phase involves activities like test case completion reporting, test completion matrix and test results. Testing team analyze testing artifacts to identify testing strategies that need to be implemented in the future and , taking lessons from the current test cycle. Basically, the purpose is to remove process bottlenecks for future test cycles.
Below activities are performed in testing closure
- Identify cycle completion criteria based on test coverage, time, Cost and Quality
- Prepare test metrics
- Prepare Test closure report
- Qualitative and quantitative reporting of quality of the product
- Find out the defect distribution by type and severity based on the test result report
Conclusion
Software Testing is not just an isolated activity, i.e. testing. It consists of sequential activities carried out methodologically to help certify quality of the software and to deliver bug free products to clients which is only possible by following STLC process.
She is Senior Quality Analyst at Elitech Systems. She has expertise in automated and manual Software testing, proficient in analysing a large scale project with useful insights for developers and project team.
Comments are closed.