Idaho State University

• Academics
• Prospective Students
• Current Students
• Faculty & Staff
• Alumni & Visitors

• Information
  • Access Security
    • Department Information
    • HP3000 Server Account Information
    • Network Services Account Information
    • Responsible Account Holder Information
    • Application System Responsibility
    • Department/Group Info
  • User Guide
    • Table of Contents
  • Networked Printers
  • Miscellaneous System Info
    • HP1 (HPe3000) Server Scheduled Down Time
    • Powerhouse Web Queue Management Values
    • Portal Web Services Availability Schedule
• Our Staff
  • Support by System
  • Primary Support
  • Backup Support
• Project Management
  • Staff Responsibilities
    • Support by System
    • Primary Support
    • Backup Support
• Information Technology Services
• DEACON Project

Enterprise Applications
Development Guidelines and Procedures

Appendix H: Project Test Plan

Administrative Systems
Project Test Plan

Project Name/Number:
Project Leader:

1. Project Description:
   Briefly describe the project.
2. Define the Types of Tests to be Performed: Phased testing will ensure that all functions within a system meet the system requirements. Test data includes valid data, exception data, invalid data and missing data categories to isolate specific problem areas. Include schedule of dates when all phases will be verified as ready for production by the user.
• Component - each module is tested during the development phase.
• Interface - Each module is tested with each module, program, or system with which it interacts.
• System - Test the whole system including the new modules. For example, a new payroll module or major changes to an existing payroll module would involve testing the entire payroll cycle.
• Parallel - This involves replicating the data and/or environment that is in production and performing the same transactions on both production and development systems while verifying the results are the same or as expected.
• Performance - Test on-line or batch applications with as large a load as possible.
• Control/Security features. - Create test users that should and should not have access and verify that access is working as expected.
• User Acceptance - The application users should participate in and sign off on the testing as final acceptance of the test phase.
3. Detail test criteria and scenarios to be evaluated.
   • Explain priority and criticality of test being performed.
   • Develop testing schedule, including resource assignment, scheduled times, and milestones.
   • Document test criteria using your own format or use example. The example grid could be part of the Project Specifications to avoid duplicating efforts.


4. Outline how test data will be generated.
   • Use your own format to document or use example


5. List of assumptions that define the baseline against which each deliverable was established.
   • For example, number of users, system functioning properly, test completed successfully, etc...


6. Document errors found in testing and resolutions.
   • Use your own format to document or use example
7. Post-session task assignments define the actions that individuals have to do to clarify open questions or resolve open issues.
8. A synopsis (short overview) of the results of the entire session for management review.