Test Driver allows you to run test packages. This is useful if you need to run tests independently of building them.
A test package is a zip file containing tests, their dependencies and the XML files which describe them, see Building test packages.
The command line for running a test package is:
> testdriver run [--tp package] [-t transport] [-a architecture]
The parameters are the same as for running a suite, except the -s
option is replaced with a --tp
(test package) argument. This value will be a path to a test package (.tpkg
).
--tp
|
This is mandatory, and is used to specify the test package which is to be run, including the full directory path and the
file name.
An example of using the --tp option is: --tp \\<drive_name>\packages\CtsPackage.tpkg .
|
-t
|
This is optional, and is used to specify the mode of transport for communicating with the device.
Options are serial1 , serial2 or tcp . The default option is set to serial1 .
At present, only serial and TCP/IP transport modes have been tested - how to set these up is described in Communicating with the device.
|
-a
|
This is optional, and is used for defining the application specific software product (ASSP) architecture if required.
An example command line to build the suite is:
> testdriver run -p arm4 -b urel -s testsuite1.testsuite3
|
-h
|
This is optional, and is used for displaying help information.
|
|
An example of how to run a test package is shown below:
> testdriver run -p arm4 -b urel --tp \\<drive_name>\packages\CtsPackage.tpkg -t serial2