Test plan

TEST PLAN OUTLINE
(IEEE 829 Format)
1. Test Plan Identifier
2. References
3. Introduction
4. Test Items
5. Software Risk Issues
6. Features to be Tested
7. Features not to be Tested
8. Approach
9. Item Pass/Fail Criteria
10. Suspension Criteria and Resumption Requirements
11. Test Deliverables
12. Remaining Test Tasks
13. Environmental Needs
14. Staffing and Training Needs
15.Responsibilities
16. Schedule
17. Planning Risks and Contingencies
18. Approvals
19. Glossary

Sample Master Test Plan

TEST PLAN IDENTIFIERRS-MTP01.3

REFERENCES

None Identified.

INTRODUCTION

This is the Master Test Plan for the Reassigned Sales Re-write project. This plan will address only those items and elements that are related to the Reassigned Sales process, both directlyand indirectly affected elements will be addressed. The primary focus of this plan is to ensure that the new Reassigned Sales application provides the same level of information and detail as the current system while allowing for improvements and increases in data acquisition and level of details available (granularity).
The project will have three levels of testing, Unit, System/Integration andAcceptance. The details for each level are addressed in the approach section and will be further defined in the level specific plans.
The estimated time line for this project is very aggressive (six (6) months), as such, any delays in the development process or in the installation and verification of the third party software could have significant effects on the test plan. The acceptance testing isexpected to take one (1) month from the date of application delivery from system test and is to be done in parallel with the current application process.

TEST ITEMS

The following is a list, by version and release, of the items to be tested:
A. EXTOL EDI package, Version 3.0
If a new release is available prior to roll-out it will not be used until after installation. It will be a separateupgrade/update project.
B. DNS PC EDI transaction package, Version 2.2
If a new release is available prior to roll-out it will not be used until after installation. It will be a separate upgrade/update project.
C. Custom PC EDI transaction package (two distributors only).
D. New reassigned sales software, initial version to be Version 1.0
A detailed listing of programs, databases, screens andreports will be provided in the system and detailed design documents.
E. Order Entry EDI interface software, Current version at time of pilot. Currently, version 4.1.
F. Reassigned Sales System requirements document, SST_RQMT.WPD version 4.1
G. Reassigned Sales System Design Document, SST_SYSD.WPD version 3.02
H. Reassigned Sales Detail Design Document, SST_DTLD.WPD version 3.04

SOFTWARERISK ISSUES

There are several parts of the project that are not within the control of the Reassigned Sales application but have direct impacts on the process and must be checked as well.
A. The local AS/400 based vendor supplied EDI software package. This package will be providing all the reformatting support from the ANSI X12 EDI formats to the internal AS/400 data base file formats.
B.The PC based software package installed at each distributor's location (both custom written and vendor supplied) will be providing the formatting of the distributors data into the correct EDI X12 formats.
C. Backup and Recovery of the EDI transmission files, local databases and restart of the translation process, must be carefully checked.
D. The ability to restart the application in themiddle of the process is a critical factor to application reliability. This is especially true in the case of the transmission files as once the data is pulled from the mail box it is no longer available there and must be protected locally.
E. Database security and access must be defined and verified, especially for files shared between the Order Entry application and the Reassigned Sales...