An Integrated Approach to Software Engineering, Third Edition

Here we briefly discuss the test plans and strategy for the two case studies. The detailed test case specifications for system testing are available from the Web site.
This document describes the plan for testing the course scheduling software. All major testing activities are specified here; additional testing may be scheduled later, if necessary.
In this project we will perform two levels of testing: unit testing and system testing. Because the system is small, it is felt that there is no need for elaborate integration testing. The basic units to be tested are:
Modules to input file-1
Modules to input file-2
Modules for scheduling
In addition, some other units may be chosen for testing. The testing for these different units will be done independently.
All the functional features specified in the requirements document will be tested. No testing will be done for the performance, as the response time requirement is quite weak.
For unit testing, structural testing based on the branch coverage criterion will be used. The goal is to achieve branch coverage of more than 95%. The CCOV coverage analyzer tool will be used to determine the coverage. System testing will be largely functional in nature. The focus is on invalid and valid cases, boundary values, and special cases.
The following documents are required (besides this test plan):
Unit test report for each...