The stability test for the Resource Kit is an XPOZ script that attempts to reveal any weakness in driver policy or data handling by injecting random data into the driver's environment based on the eDirectory™ syntax type of the attributes each objectClass is working with. The test then checks each driver's Dirxml-StatusLog attribute on both the Subscriber and Publisher channels for any Error messages that have been recorded, and reports these errors in the test summary.
You use the IDV-stability.env XPOZ script to start the stability test. The script is a series of loops based on the DirXML-DriverSet DN you entered as an XPOZ environment variable. The test queries the DirXML-DriverSet object for any DirXML-Driver objects it contains. The DirXML-Driver Distinguished Names (DN's) that are returned from this query are placed in an array structure for the test to use.
You are presented with a list of DirXML-Drivers that you can test. You have the option of stopping all the drivers, with only the tested driver running during each driver loop, or you can keep all drivers running. After the selections have been made, the test queries the selected driver's DirXML-DriverFilter and parses the filter for the classes and attributes that the selected driver is handling. The object classes and their attributes are then placed in array that is walked through by the test. For each eDirectory class, if it is recognized, the test creates an XPOZ Test object, then populates the object with the attributes found in the filter for this objectClass. Each attribute type is retrieved from eDirectory, and the attribute's eDirectory syntax is then tested for each of the following conditions (this varies based on syntax type):
Remove all values.
Blank or null value.
If sized, less than the minimum value.
If sized, over the maximum value.
Minimum value.
Maximum value.
Random string with range.
Random string of extended ASCII characters, where applicable.
Random string of double-byte characters, where applicable.
Illegal characters such as escaped dots in the attribute value (\.).
Multiple values, where applicable.
Attribute value case, where applicable.
After all of the objectClasses attributes are tested with this data, the DirXML-StatusLog attribute is queried for any error messages, the next objectClass is tested for its attributes, and the process is repeated. After all objectClasses and attributes have been tested, the test moves on to the next driver, if applicable. When the test is complete, a summary screen lists the Driver, objectClass, and attribute that recorded any error messages in the status log. The drivers are then returned to the state they were in before the test was started. In other words, if they were running before the test was started, they are restarted after the test completes.
If any new attributes are added to existing drivers, or if new DirXML-Drivers are added to the parent DirXML-DriverSet object, you can re-run the test. These new drivers or new attributes appear as testable components to the script.