Prepare Test Plans: -
After testing team formation and risks analysis the test lead prepares test plan documents.
Format:
1. Test Plan ID: The identification no. or name.
2. Instructions: About the project
3. Test Items: Name of modules or functionalities or services.
4. Feature to be tested: The names of modules which are selected for testing
Eg: a, b, c Modules are all to be tested.
5. Features not to be tested: The names of remaining tested modules.
Eg: V1 --> V2 = V1+Some extra modules (These are to be tested)
6. Approach: The selected list of selecting techniques with respect to test Strategy (selected by Project Manager)
7. Test Environment: Required Hardware & Software to apply the selected test on specified features.
Eg: a, b, c, d
cd ----------> UI ST CI
(Features) MI LT CI
8. Entry criteria:
a. Prepare complete & correctness
b. Establish Test environment
c. Receive stable build from developers.
9. Suspension criteria:
a. Test environment is nor supporting
b. Show stopper defect occurred (without resolving the problem, we cannot start testing)
c. Pending defects are more (Quality gap)
10. Exit Criteria:
a. All modules tested
b. Meet the duration
c. All major bugs resolved
11. Test Deliverable: The names of test documents to be prepared by test Engineers.
Eg:
a. Test Scenarios
b. Test Case Documents
c. Test logs
d. Defect Reports
e. Summary reports etc.
12. Staff & Training needs: The names of selected test engineers and required training sessions for them.
13. Responsibilities: The mapping in between test engineers and their available testing area.
14. Schedule: Dates & Time
15. Risks & Assumptions: List of previously analyzed risks & assumptions
16. Approvals: The signature of test lead and Project Manager.
Format:
1. Test Plan ID: The identification no. or name.
2. Instructions: About the project
3. Test Items: Name of modules or functionalities or services.
4. Feature to be tested: The names of modules which are selected for testing
Eg: a, b, c Modules are all to be tested.
5. Features not to be tested: The names of remaining tested modules.
Eg: V1 --> V2 = V1+Some extra modules (These are to be tested)
6. Approach: The selected list of selecting techniques with respect to test Strategy (selected by Project Manager)
7. Test Environment: Required Hardware & Software to apply the selected test on specified features.
Eg: a, b, c, d
cd ----------> UI ST CI
(Features) MI LT CI
8. Entry criteria:
a. Prepare complete & correctness
b. Establish Test environment
c. Receive stable build from developers.
9. Suspension criteria:
a. Test environment is nor supporting
b. Show stopper defect occurred (without resolving the problem, we cannot start testing)
c. Pending defects are more (Quality gap)
10. Exit Criteria:
a. All modules tested
b. Meet the duration
c. All major bugs resolved
11. Test Deliverable: The names of test documents to be prepared by test Engineers.
Eg:
a. Test Scenarios
b. Test Case Documents
c. Test logs
d. Defect Reports
e. Summary reports etc.
12. Staff & Training needs: The names of selected test engineers and required training sessions for them.
13. Responsibilities: The mapping in between test engineers and their available testing area.
14. Schedule: Dates & Time
15. Risks & Assumptions: List of previously analyzed risks & assumptions
16. Approvals: The signature of test lead and Project Manager.
No comments:
Post a Comment