Software Test Life Cycle
Software Test Process may vary from one company to another, but purpose is common. Requirement Analysis, Software Test Planning, Software Test Case development, Software Test environment Setup, Software Test Execution and Software test Cycle Closure are the important Phases in Software Test Life Cycle.
Software Test Lead, Software Testers, Business Analyst, Technical support people and SME (Subject Matter Expert) are involved in this Software Test Process.
Software Test Lead: Creates RTM, Risk Analysis, Implements Test Strategy , Creates Software Test Plan, Plans Configuration Management, defines Test Environment Setup, Guidance to Team Members, Monitors Test Process and Test Control.
Software Testers: Understand Test Requirements, Derive Test Scenarios, Document Test Cases, Update RTM, Collect Test Data, Verify Test Environment Setup, Execute Test Cases, Report & Track Defects, Confirmation Testing and Report Test Results.
Business Analyst: Clarifications on Requirements
Tech Support People: Software Test Environment Setup and Solve Test Environment Issues.
SME (Subject Matter Expert): Provides Knowledge on Software Application Domain (Banking/Insurance/ERP/Ecommerece/Telecom/Retail Market/Healthcare…)
Chapter Index
1) Requirement Analysis
2) Test Planning
3) Test Design & Development
4) Test Environment Setup
5) Test Execution
6) Test Cycle Closure
This Software Testing Life Cycle or Software Test Process is for conducting Software Testing at System Testing Level and It is Manual Testing Process.
We have Entry and Exit Criteria for all phase in the Software Testing Life Cycle…
Entry Criteria: Entry Criteria gives the prerequisite items that must be completed.
Exit Criteria: Exit Criteria defines the items that must be completed.
1) Requirement Analysis
In Requirement Analysis phase, test team studies the requirements and identify the testable requirements.
Entry Criteria: Requirements Document available (both functional and non functional), Application architectural document or Product should be available…
Exit Criteria: RTM should be signed off and The customer should sign off on the test automation feasibility
Activities in this phase:
a) Identify types of tests to be performed.
b) Risk Analysis
c) Prepare Requirement Traceability Matrix (RTM).
d) Identify Test environment details
e) Automation feasibility analysis (if required).
Deliverables:
a) Requirement Traceability Matrix (RTM)
b) Automation feasibility report(Optional)
2) Test Planning
In this phase the Test Manager or Test Lead prepares the Test Plan and Test strategy documents.
Entry Criteria: Requirements Document, Requirement Traceability Matrix (RTM) and Automation Feasibility Report
Exit Criteria: Approved Test Plan document, Test Strategy document and Effort estimation document
Activities in this phase:
a) Selection of Testing Approach
b) Test Estimation
c) Team Formation
d) Preparation of Test Plan, Test strategy documents
e) Configuration Management Planning
f) Resource planning
g) Test Tool Selection (if required)
h) Training Requirement
Deliverables:
a) Test Plan, Test Strategy document.
b) Test estimation document. Etc..
3) Test Design & Development
In Test design phase, testers prepare test scenarios, test cases/test scripts and test data based on the Requirement Document/s and Test Plan.
Entry Criteria: Requirements Document/s, RTM and Test Plan, Automation analysis report
Exit Criteria: Reviews Test cases, Test Scripts (if automation) and Test data.
Activities in this phase:
a) Derive Test Scenarios
b) Test Case Documentation
c) Review Test Cases
d) Update RTM – Map Test Cases to Requirements in RTM
e) Creation of Test Scripts if required
f) Collect Test Data Etc…
Deliverables:
a) Test cases
b) Test scripts (for automation if required)
c) Test Data
4) Test Environment Setup
- It is a combination of hardware and software environment on which the tests will be executed.
- Test Environment supports test execution with software, hardware and network configured. Test environment configuration must mimic the production environment.
- Readiness of the test environment can be validated by smoke testing performed by the Testing team.
Entry Criteria: System design document/s, Architectural document of the application and Environment set-up checklist. Provision of Test Plan, readiness of Smoke Test cases and preparation of test data.
Exit criteria: Test environment should be ready and smoke testing should be performed successfully.
Activities:
a) Setup Test Environment and Test Data
b) Verify Test Environment by Conducting Smoke Tests
Deliverables:
a) Test Environment ready with test data set up
b) Smoke Test Results.
5) Test Execution
In Test Execution phase the test cases are executed in the testing environment, while execution of the test cases the Testing team may find bugs which will be reported, bugs are fixed by the developer and they are retested by the Testing Team.
Entry Criteria: Test Plan document, Test cases, Test data, Test Environment
Exit Criteria: Test case execution report. Defect report, RTM
Activities:
a) Execution of Test Cases
b) Document test results, and log defects for failed cases
c) Update RTM – Map defects to test cases in RTM
d) Retest the Defect fixes
e) Track the Defects to Closure
Deliverables:
a) Test execution Report
b) Updated test cases with results
c) Completed RTM with execution status
d) Opened and Closed Bug Report/s
6) Test Cycle Closure
Testing team will meet, discuss and analyze testing artifacts and evaluate Test cycle completion criteria. Identify strategies that have to be implemented in future and taking lessons from the current test cycle.
Entry Criteria: Test case Execution report and Opened and closed Defect Reports
Exit Criteria: Test Closure Report signed off by client, Test Metrics
Activities:
a) Evaluate Test Cycle completion criteria
b) Prepare test metrics
c) Documentation of the learning from the project
d) Prepare Test closure report
Deliverables:
a) Test Closure report
b) Test metrics
Follow me on social media:
