SIS files
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:
-
TestDriver required files:
The list of files is stored as meta data in the System Configuration
files.
-
Task-level SIS file:
If the current task contains other tasks, then each of these tasks
are installed/uninstalled before the current task is uninstalled.
SIS UID allocation
TestDriver uses more than one .sis
file, and needs several
SIS UIDs. A dedicated range of SIS UIDs is assigned to the TestDriver, which
uses 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 task installed
earlier, then a new UID is used, as the current UID is uninstalled once the
task has been completed.
-
If the task is in the same level as that of the task installed
earlier, the same UID is used, as the previous task is uninstalled before the
current one is started.
-
If the task is going down one level compared to the previous task
then the UID for the encapsulating task is returned to the stack. This
minimises the usage of the new UID. The number of UIDs must be less than or
equal to the number of levels in the hierarchy of tasks.