The TestDriver configuration files are indirectly used as input for both the build and run commands. The build command builds the test code, copies the produced binaries and the data dependencies to the repository and copies the SIS files containing all these files. The run command directs the STAT tool to transfer the SIS files stored from the repository to the device.

The SIS files that are required to run a test are packaged into four types:

1. TestDriver required files:

   • to be sent and installed only once for each build command

   • to be uninstalled and deleted only when all the selected tests have been attempted to be executed.

   The list of files is stored as meta data in the System Configuration files.

2. Task-level SIS file:

   • to be sent and installed before each task

   • to be uninstalled and deleted when the selected task has been attempted to be executed.

   If the current task contains other tasks, then each of these tasks will be installed/uninstalled before the current task is uninstalled.

TestDriver uses more than one .sis file, and needs several SIS UIDs. A dedicated range of SIS UIDs is assigned to the TestDriver, which will pick the first available UID from the range of UIDs. UIDs are allocated in a round robin fashion using the following rules:

• If the task is going up one level compared to the previous installed task, then a new UID will be used, since the current UID will only be uninstalled once the task has been completed.

• If the task is in the same level as that of the previously installed task, the same UID will be used, as the previous task will be first uninstalled before the current one is run.

• If the task is going down one level compared to the previous task then the UID for the encapsulating task will be returned to the stack. This minimises the usage of the new UID. The number of UIDs should never be more than one above the number of levels in the hierarchy of tasks.