You can use a Test Plan Document to document the strategy that will be used to verify and ensure that a software product or system meets its design specifications and other requirements. It will help you define Release Criteria, identify Test Deliverables, prepare Budget Costs and describe the test environment to be used for the testing.
Use the Test Plan to:
1.1 Objectives
1.2 System Description
1.3 Scope
1.4 Code Freeze Date
1.5 Exception Handling
1.6 Risks
1.7 Issues
1.8 Dependencies
1.9 Relationship to Other Plans
2 Test Plan Strategy
2.1 Acceptance Testing
2.2 Automated Test
2.3 Beta Testing
2.4 Conversion Testing
2.5 Documentation Test
2.6 Hardware Testing
2.7 Interface Testing
2.8 Integration Testing
2.9 Localization
2.10 Network Testing
2.11 Parallel Testing
2.12 Security Testing
2.13 Stress and Volume Test
2.14 System Test
2.15 Performance Testing
2.16 Recovery Testing
2.17 Regression Testing
2.18 Unit Testing
2.19 User Acceptance Test
3 Test Environments
3.1 Hardware
3.1.1 Servers
3.1.2 Server Configuration
3.1.3 Desktop Configuration
3.2 Software
3.3 Security
3.4 Tools
3.5 Documentation
4 Control Procedures
4.1 Reviews
4.2 Bug Review meetings
4.3 Change Control
4.4 Defect Reporting
5 Test Execution
5.1 Features to be tested
5.2 Test Case Matrix
6 Release Criteria
6.1 Readiness Criteria
6.2 Acceptance Criteria
6.2.1 Alpha release criteria
6.2.2 Beta release criteria
6.2.3 Final release criteria
6.3 Pass/Fail Criteria
6.4 Suspension Criteria
6.5 Resumption Criteria
6.5.1 Release to User Acceptance Test Criteria
6.5.2 Release to Production Criteria
6.6 Severity Codes
7 Management Approach
7.1 Test Deliverables
7.2 Roles and Responsibilities
7.3 Resource Loading Chart
7.4 Budget Information
7.5 Training Requirements
Appendix A
Glossary of Terms
Traceability Matrix
If you want some perspective on how you or your company needs to enhance their Sales/Client Management Capabilities, please email me (Shubhanjan Saha) at shubhanjan.saha@gmail.com
Use the Test Plan to:
- Define your Test Plan Strategy.
- Identify different types of testing to be performed.
- Provide schedules for test activities.
Table of Contents
1 Introduction1.1 Objectives
1.2 System Description
1.3 Scope
1.4 Code Freeze Date
1.5 Exception Handling
1.6 Risks
1.7 Issues
1.8 Dependencies
1.9 Relationship to Other Plans
2 Test Plan Strategy
2.1 Acceptance Testing
2.2 Automated Test
2.3 Beta Testing
2.4 Conversion Testing
2.5 Documentation Test
2.6 Hardware Testing
2.7 Interface Testing
2.8 Integration Testing
2.9 Localization
2.10 Network Testing
2.11 Parallel Testing
2.12 Security Testing
2.13 Stress and Volume Test
2.14 System Test
2.15 Performance Testing
2.16 Recovery Testing
2.17 Regression Testing
2.18 Unit Testing
2.19 User Acceptance Test
3 Test Environments
3.1 Hardware
3.1.1 Servers
3.1.2 Server Configuration
3.1.3 Desktop Configuration
3.2 Software
3.3 Security
3.4 Tools
3.5 Documentation
4 Control Procedures
4.1 Reviews
4.2 Bug Review meetings
4.3 Change Control
4.4 Defect Reporting
5 Test Execution
5.1 Features to be tested
5.2 Test Case Matrix
6 Release Criteria
6.1 Readiness Criteria
6.2 Acceptance Criteria
6.2.1 Alpha release criteria
6.2.2 Beta release criteria
6.2.3 Final release criteria
6.3 Pass/Fail Criteria
6.4 Suspension Criteria
6.5 Resumption Criteria
6.5.1 Release to User Acceptance Test Criteria
6.5.2 Release to Production Criteria
6.6 Severity Codes
7 Management Approach
7.1 Test Deliverables
7.2 Roles and Responsibilities
7.3 Resource Loading Chart
7.4 Budget Information
7.5 Training Requirements
Appendix A
Glossary of Terms
Traceability Matrix
If you want some perspective on how you or your company needs to enhance their Sales/Client Management Capabilities, please email me (Shubhanjan Saha) at shubhanjan.saha@gmail.com
No comments:
Post a Comment