Mapper C++ code is statically checked by using the C++ compiler with all useful warning options turned on.
Mapper HTML files are checked for dangling links, by extracting all the link anchors and references and then searching for anchors referred to but not defined.
All testing of Mapper is fully automatic. The Makefile has build targets for running the tests.
C++ test drivers are used for unit and integration testing of Mapper.
Shell commands drive the system tests of Mapper, and use files for the input data.
While running the tests of Mapper,
all C assert checks are activated.
The tests will therefore check the internal and intermediate state information during the test execution, rather than merely checking the outputs of the execution. Testing is therefore more likely to detect defects, and debugging them is likely to be faster.
The automatic test suite must process as input each XML element in the DTD at least once.
The automatic test suite must execute at least 95% of all executable lines of Mapper.
The automatic test suite
must execute at least
70%
of the executable lines of each compilation unit (.cpp file)
of Mapper.
This documentation is still being written,
and is therefore incomplete.
$Revision: 6.12 $
$Date: 2002/07/13 20:18:41 $