The document outlines the key phases and activities in software testing:
1. Test planning determines what, how, and when to test based on requirements and plans.
2. Test design uses requirements, plans, documents and cases to design test cases and scenarios.
3. Test execution runs the test cases and logs defects based on requirements, plans and builds.
4. Defect reporting tracks defects found during testing using test cases and reports.
5. Test closure verifies exit criteria through analysis of reports and defects. Responsibilities are assigned and outcomes defined for each activity.
The document outlines the key phases and activities in software testing:
1. Test planning determines what, how, and when to test based on requirements and plans.
2. Test design uses requirements, plans, documents and cases to design test cases and scenarios.
3. Test execution runs the test cases and logs defects based on requirements, plans and builds.
4. Defect reporting tracks defects found during testing using test cases and reports.
5. Test closure verifies exit criteria through analysis of reports and defects. Responsibilities are assigned and outcomes defined for each activity.
The document outlines the key phases and activities in software testing:
1. Test planning determines what, how, and when to test based on requirements and plans.
2. Test design uses requirements, plans, documents and cases to design test cases and scenarios.
3. Test execution runs the test cases and logs defects based on requirements, plans and builds.
4. Defect reporting tracks defects found during testing using test cases and reports.
5. Test closure verifies exit criteria through analysis of reports and defects. Responsibilities are assigned and outcomes defined for each activity.
The document outlines the key phases and activities in software testing:
1. Test planning determines what, how, and when to test based on requirements and plans.
2. Test design uses requirements, plans, documents and cases to design test cases and scenarios.
3. Test execution runs the test cases and logs defects based on requirements, plans and builds.
4. Defect reporting tracks defects found during testing using test cases and reports.
5. Test closure verifies exit criteria through analysis of reports and defects. Responsibilities are assigned and outcomes defined for each activity.
Download as XLSX, PDF, TXT or read online from Scribd
Download as xlsx, pdf, or txt
You are on page 1of 2
SNO PHASE Input
1 Test Planning Project Plan
What to test Functional Requirements How to test when to test
2 Test Designing Project Plan
Functional Requirements Test Plan Design Docs Use cases
3 Test Execution Functional Requirements
Test Plan Test Cases Build from Development Team
4 Defect Reporting & Tracking Test Cases
Test Reports/Test Log
5 Test Closure/Sign-Of Test Reports
Defect Reports Activities Responsibility Out Come Identify the Resources Test Lead/Team Lead (70%) Test Plan Document Team Formation Test Manager (30%) Prepartion of Test Plan Reviews on Test Plan Test Plan Sign-of
Preparation of Test Scenarios Test Lead/Team Lead(30%) Test Cases Document
Preparation of Test Cases Test Engineers( 70%) Treacibility Matrix Reviews on Test Cases Treacibility Matrix Test Cases Sign-of
Executing Test cases Test Lead/Team Lead(10%) Status/Test Reports
Preparation of Test Report/Test Log Test Engineers (90%) Identifying Defects
Preparation of Defect Report Test Lead/Team Lead(10%) Defect Report
Reporting Defects to Developers Test Engineers (90%)
Analyzing Test Reports Test Lead/Test Manger(70%) Test Summary Reports
Analysing Bug Reporting Test Enginners(30%) Evaluating Exit Criteria