6.4. Test Director

Test Director is a test and fault tracking system.

Test Director is based on MS Windows and hence the interfaces into the system are available on MS Windows only. Users have to run the Scmbug daemon on a Windows machine.

In order to use Test Director as your fault tracking system you will need to ensure that you install:

For Test Director, some example configuration settings for the daemon configuration file /etc/scmbug/daemon.conf are shown in Figure 6-5.

Figure 6-5. Example daemon configuration settings for Test Director.

# The URL connection string to Test Director.
database_location => 'http://emea-testdir:8080/qcbin',
	
# The database vendor is the same as the Domain within Test Director,
# This must match the value that you would use on manual login.
database_vendor => 'Domain',

# The database name is the same as the Project within Test Director.
database_name => 'Project',

# The user name is the Test Director user login.
database_username => 'username',

# The password for the Test Director login.
database_password => 'password',
	    

Test Director and its fields can be further customized in the file /etc/scmbug/TestDirector.conf. This file must be updated to match your system.

The Test Director backend does not currently support the VDD Generator.

As of version 9.0.0, Test Director does not yet support a mapping of the SCM username to a Test Director username. An SCM to bug-tracking username mapping is accomodated by the integration daemon using the userlist variable, as described in Section 4.4.8.

Note

Due to a bug in Windows ActiveState Perl, the backend would crash if a Win32::OLE object was called from a forked process (the forked daemon connection handler). For this reason the Test Director backend calls are all executed from a seperate script and the results are read back in. This does not limit the functionality, but it does mean that sub-processes are created.

Scmbug has been verified to work against the following releases of Test Director: