| < Day Day Up > |
|
The ITP describes the overall test approach. It identifies the tests to be performed and provides schedules for test activities. In large, multisystem environments, such tests often need to be coordinated and orchestrated in conjunction with downtime or completed during off-hours to avoid interruptions in business operations. The ITP will describe how to test interfaces between the various programs of the system, validate any manual-toautomated interfaces of the system (e.g., screens, reports), test external interfaces with other systems, and verify all functional and nonfunctional specifications of the system. It should also include testing of the following areas:
System interface
Control
Conversion
Security
Backup, recovery, and restart
Screen dialogue
Volume
Performance
Stress
Usability
Documentation
Storage
Maintainability
Compatibility
The STP describes the software test approach, identifies the tests to be performed for each module, and provides detailed schedules for test activities. It ensures correctness and accuracy of the program's internal logic and validates interfaces among the various modules of the program. The STP should be designed to check proper execution of all the procedural statements contained in the program modules. The STP must be written to exercise the internal logic of the program. While not all-inclusive, the following list outlines several test variants that certainly need to be included in a well-designed STP:
Statement coverage tests
Branch/loop coverage tests
Value sampling tests
Boundary value coverage tests
Program interface tests
File-handling tests
Error message tests
Error-prone tests
| < Day Day Up > |
|