The Test Plan identifies multiple test levels, which are going to be performed for the project. Activities which are going to be performed at each level must be planned in advance and has to be formally documented.
Below I am describing a sample Test plan:
1. Purpose
<The purpose of this document is to describe the various test cases, testing methodologies, environments and the Software/Hardware tools that would be used followed during <unit/integration/system> testing in the ABC project.>
2. Approvals and Authorizations
| Designation | Name | Date | |
| Author | |||
| Approved By |
3. Distribution
| Holder’s Designation | Holder’s Name | Issue Date |
| Project Manager | ||
| Test Lead |
4. Amendment Record
| No | Date | Section(s) | Issue No. | Description |
5. Test Plan
5.1 Objective of Test
<The objective of the integration/system test is to test the interfaces between the modules comprising the ABC product and to meet the performance criteria and benchmarks requirements criteria, if any, which may include volume and stress testing>
5.2 Test Method
<Details of the Test Strategy>
5.3 Entry and Exit Criteria
5.3.1 Entry Criteria
• Unit / Integration / System test plan approved.
• Coding phase / Unit testing / Integration testing complete
5.3.2 Exit Criteria
• Unit / Integration / System testing complete.
• Test records produced.
• Defect reports/Defect Tracking/produced and resolved.
5.4 Test Schedule
<As defined in the Project Management Plan.>
5.5 Defect Reporting and Monitoring Progress
• Defect reports/Defect Tracking will be maintained in line with the Testing Procedure.
• The Test Lead will issue a test report to the team members, Project Lead and Project Manager on a fortnightly basis.
5.6 Build Plan and Build Refresh Criteria
A new build of the software will be made whenever
• A Defect is found which prevents further testing
• All test cases have been executed and some Defects have been corrected
5.7 Resource Requirements
5.7.1 Hardware Requirements
| Resource | Description | Qty |
5.7.2 Software Requirements
| Software | Description | Qty |
6. Test Architecture
6.1 Test Architecture/Topology
<Draw the various test architecture/topology required for the testing>
I will try to post a new blog on Test Architecture/Topology very soon. Keep updating and keep visiting... :)
7 Test Environment Set up
< Describe the Testing Environment >
8. Test Cases
<Test cases definition for this testing is documented in the separate Test Case Form.>
2 comments:
The formate of the above blog may not look very eye catching as this is not supporting 'Table'.
I hope you people will not take it very seriously :)...
This is the most desired topic for any newbies.I still have a whole lots of confusion on this very topic which I hope would be erase away in the coming days when I will read this blog a few times more and even more the coming posts as I hope will definitely complement this concept in a deeper level.Thanks!
Post a Comment