STLC (Software Testing Life Cycle)

Software Testing Life Cycle:
Below is the summary of STLC along with Entry and Exit Criteria: Following phases are involved in STLC:

1. Requirement Analysis
2. Test Planning
3. Test case development
4. Test Environment setup
5. Test Execution
6. Test Cycle closure

1. Requirement Analysis:

• Entry Criteria: 
• Requirements Document available (both functional and non functional)
• Application architectural document available

• Activity:
• Analyze business functionality to know the business modules and module specific functionalities.
• Identify types of tests to be performed
• Prepare Requirement Traceability Matrix (RTM).
• Identify test environment details where testing is supposed to be carried out.
• Automation feasibility analysis (if required).
• Exit Criteria: 
• Signed off RTM
• Test automation feasibility report signed off by the client
• Deliverables: RTM, Automation feasibility report (if applicable)

2. Test Planning:

• Entry Criteria: 
• Requirements Documents
• Requirement Traceability matrix.
• Test automation feasibility document.
• Activity:
• Preparation of test plan/strategy document for various types of testing
• Test tool selection
• Test effort estimation
• Resource planning and determining roles and responsibilities.

• Exit Criteria:
• Approved test plan/strategy document.
• Effort estimation document signed off.
• Deleverables:
• Test plan/strategy document., 
• Effort estimation document.

3. Test Case Development:

• Entry Criteria: 
• Requirements Documents
• RTM and test plan
• Automation analysis report
• Activity:
• Create test cases, automation scripts (where applicable)
• Review and baseline test cases and scripts
• Create test data
• Exit Criteria:
• Reviewed and signed test Cases/scripts
• Reviewed and signed test data
• Deleverables: Test cases/scripts, Test data

4. Test Environment SetUp:

• Entry Criteria: System design document and Environment set-up plan
• Activity:
• Prepare hardware and software requirement list
• Setup test Environment and test data
• Perform smoke test on the build
• Accept/reject the build depending on smoke test result
• Exit Criteria: 
• Environment setup is working as per the plan and checklist
• Test data setup is complete
• Smoke test is successful
• Deleverables: Environment ready with test data set up, Smoke Test Results.

5. Test Execution:

• Entry Criteria: 
• Baselined RTM, Test Plan, Test case/scripts are available
• Test environment is ready
• Test data set up is done
• Unit/Integration test report for the build to be tested is available
• Activity: 
• Execute tests as per plan
• Document test results, and log defects for failed cases
• Update test plans/test cases, if necessary
• Map defects to test cases in RTM
• Retest the defect fixes
• Regression testing of application
• Track the defects to closure
• Exit Criteria:
• All tests planned are executed
• Defects logged and tracked to closure
• Deleverables:
• Completed RTM with execution status
• Test cases updated with results
• Defect reports

6. Test Cycle Closure:

• Entry Criteria: 
• Testing has been completed
• Test results are available
• Defect logs are available
• Activity:
• Evaluate cycle completion criteria based on - Time, Test coverage, Cost, Software Quality, Critical Business Objectives
• Prepare test metrics based on the above parameters.
• Prepare Test closure report
• Exit Criteria: Test Closure report signed off by client
• Deleverables: Test Closure report, Test metrics