8 Testing the library

We are following a bottom-up testing strategy. The verification of the library is performed in the following steps:

Figure 8.1: Test types

1. Unit testing is performed in order to verify the low-level modules of the library.
2. Subsystem testing is performed in order to verify the combination of several subsystems. i.e. to test each library layer.
3. System testing is performed in order to verify the whole system. i.e. the GNU PDF Library.

We use check ¹ to implement our testing infrastructure. Please read the check manual in order to become familiar with its concepts such as test suite, test case, etc.

At some point we wrote a simple replacement for libcheck in Windows systems: nocheck (torture/unit/nocheck). The usage of the replacement is now deprecated, since the latest version of libcheck should support windows.

• The test specification document
• Unit testing
• Test Data Files
• The tortutils Library