ABSTRACT

The unit test plan is based on the program or design specification and is required for a formal test environment. The following is a sample unit test plan table of contents.

1. Introduction Section

a. Test Strategy and Approach b. Test Scope c. Test Assumptions

2. Walkthrough (Static testing)

a. Defects Discovered and Corrected b. Improvement Ideas c. Structured Programming Compliance d. Language Standards e. Development Documentation Standards

3. Test Cases (Dynamic testing)

a. Input Test Data b. Initial Conditions c. Expected Results e. Test Log Status

4. Environment Requirements

a. Test Strategy and Approach b. Platform c. Libraries d. Tools e. Test Procedures f. Status Reporting

E2: SYSTEM/ACCEPTANCE TEST PLAN

The system or acceptance test plan is based on the requirement specifications and is required for a formal test environment. System testing evaluates the functionality and performance of the whole application and consists of a variety of tests including: performance, usability, stress, documentation, security, volume, recovery, etc. Acceptance testing is a userrun test which demonstrates the application’s ability to meet the original

business objectives and system requirements and usually consists of a subset of system tests.