next up previous contents
Next: System and acceptance testing Up: Approach Previous: Approach   Contents

Module testing

The module testing will be done on Thursday March 7th.

The most important objective of the module testing is to find as many errors as possible in the modules to be tested. These errors must be corrected before system testing so that the testers can rely on correct functionality of these modules during the system testing.

The tests will be done using a comprehensive set of different test cases. Not all of the low-level modules containg input validity checking but this validity checking is assumed to be done on a higher level. Thus, the test cases can't include every possible input but only such inputs which comply with the SDS.

Tests will be done using designated test drivers and test stubs. For Java classes these drivers will be implemented in Java and for the DLL library the test driver will be implemented using Borland C++ Builder.

The goal of module testing phase is a full statement coverage for the tested modules. However, it must be kept in mind that for some modules this goal is very hard to reach.1 After performing the tests the tester must estimate, whether full statement coverage was achived.

If an error is found during module testing, the error must be described in the rest report.


next up previous contents
Next: System and acceptance testing Up: Approach Previous: Approach   Contents
2002-03-19