4.2. Testing requirements

4.2.1. General testing requirements

The test suite has two parts to it: a set of tests using randomly generated data (actually pseudo-random data), and the same set of tests using non-random data. The non-random tests are expected to produce identical database files on all platforms, and the distribution includes the expected output in the cross_platform_output_XXX.txt text files, where XXX is a supported library, and which is extracted from a database using SQLite3's command line tool and then compared against. The supported third party libraries are: Loki, boost, and Intel TBB. Libraries that are declared or determined to be present will be tested.

Some of the tests use UUIDs, and a third party UUID library may be needed.

4.2.2. Mac OS X testing requirements

Mac OS X 10.4 includes the SQLite3 command line tool and a UUID library, so any or all of these third party libraries may be installed: Loki, boost, and Intel TBB.

4.2.3. Windows testing requirements

Windows includes a UUID library, so only the SQLite3 command line tool and any or all of these third party libraries should be installed: Loki, boost, and Intel TBB.

The SQLite3 command line tool must be copied to the proj_win directory.

4.2.4. POSIX testing requirements

POSIX systems come in different configurations so it may be necessary to install any or all third party libraries such as a UUID library, Loki, boost, and Intel TBB, as well as the SQLite3 command line tool.

For POSIX systems, the e2fsprogs project has a library of utility functions including a UUID library, and is the recommended library if your system does not include UUID functions. The distribution's configure script includes a test for uuid_parse() in libuuid.so and if this test fails, you will need to install a UUID library.