The Six Phases Of Software Testing Life Cycle (STLC)
The six phases of the STLC are,
- Requirement Analysis
- Test Planning
- Test Case Development
- Environment Setup
- Test Execution and
- Test Cycle Closure
Given below are the processes which will be undertaken in each phase, classified on the basis of Entry Criteria, Activities Involved, Exit Criteria and Deliverables.
The latest software testing training in Cochin is also teaching advanced methods to students that can help them to oversee the process of automation testing. If you are keen on developing a career as a software tester, it is important that you learn everything about the industry and its testing operations from a leading education center which gives the best software testing training in Kerala that can offer highly competent software performance testing lessons.
The first step in STLC is the Requirement Analysis, where the testing team looks at the Requirement document with both functional and non functional details. This is checked inorder to identify the testable requirements.
- Requirements specifications and Document of application architectural
- Analyzing the system requirement specifications from a testing point of view, preparing the Requirement Traceability Matrix (RTM), identifying the testing techniques and testing types, prioritizing the features that require focussed testing, analyzing automation feasibility and identifying the details about testing environment where actual testing will be done.
- RTM should be signed off and the customer should sign off on the test automation feasibility
- Procurement of the Requirement Traceability Matrix (RTM) and Automation Feasibility report if applicable.
All the testing strategies are defined in this phase. The cost and effort of the entire project will be determined by the Test Manager.
- Requirements documents and Automation Feasibility Report
- Estimating the testing effort, selecting the testing approach , preparing the test plan and test strategy documents, resource planning and assigning of roles and responsibilities, and selection of testing tool.
- Approved test plan and test strategy document and effort estimation document
- To procure the Test Plan or Test strategy document and Testing Effort estimation document
Test Case Development
Here the testing team writes down the detailed test cases. If required they also prepare the test data. Obviously, RTM is also prepared.
- Availability of the Requirements Documents and the automation feasibility report.
- Creating test cases, creating test scripts if required, verifying test cases and automation scripts and creating test data in the testing environment.
- Reviewed test cases, reviewed test automation scripts and test data creation ready for testing.
- You have the test cases, test data and Test Automation Scripts, if required.
Test Environment Set Up
The setup or installation process of software and hardware that is required to test the application.
- Availability of Test Plan, availability of Smoke Test cases and availability of test data.
- Based on the Requirement and Architecture document the list of required software and hardware is prepared, to set up the test environment, to create test data and after the Test Environment is set up we have to execute the Smoke test cases in order to check the readiness of the test environment.
- Environment setup is ready for testing, installed required software and hardware, build installation is complete and successful, completion of test data creation and completion of Smoke testing.
- The Test Environment is ready with test data and we have the results of the Smoke test cases.
The test cases based on the prepared test planning and prepared test cases are executed in this phase.
- To procure the Test Plan or Test strategy document, test cases and test data
- To execute test case, to report test results, logging defects for the failed test cases, to verify and retest the defect and closure of defects
- Execution of all test cases and defects are logged and tracked for closure
- Test case execution report and defect report
Test Cycle Closure
The Test Cycle Closure process is where you meet with the testing team members. You discuss and evaluate cycle completion criteria based on Test coverage, Quality, Cost, Time, Critical Business Objectives, and Software.
You brush up on what all went good and which area needs improvement. You also acquire lessons from current STLC as input to upcoming test cycles. This will also help in reducing bottlenecks in the future STLC processes.
- Completion of Test Case Execution, report of the Test Case Execution and Defect Report
- Evaluate test completion based on Test Coverage and Software Quality, documentation of learning from the project, to analyze the test results in order to find out the distribution of severe defects and preparation of the Test Closure report.
We procure the signed off Test Closure report by the client.
- Test Closure report and Test metrics
These six phases are essential to complete the STLC process. These processes are carried out to ensure that the product quality fulfills the demanded expectations of the customer.