Here is the description of the unit tests for the re-engineered BDII.

The unit tests can be run directly from the CVS tree. The script will exit 1 if there is a failure and exit 0 if the tests are successful.

The testing script firstly generates the configuration and writes this to the etc directory. 

The BDII is restarted and a check is made to ensure that the database is empty.

The dummy ldif scripts are then used to populated the database and a check is made to ensure that the database has been updated.

The configuration is altered to change the population scripts used.

The three population scripts test:
A hanging information provider
A information provider that does not exist
A information provider with bad data.

These three scripts should not affect the population of the database.

As the TTL for the data in the database has been set to 20 secs and the hanging information provider times out is 20, the delete method should remove all entries from the database and a check is made that it is empty.


