Running test suites in Using TestDriver

Tests can be run both on the Emulator and on a device, from a PC. The boards tested so far are Assabet and Lubbock. When tests are run, the tests and their dependencies are copied to the C: drive of the device (or emulator).

Tests are then executed on the device and the logs are collected and transferred back to the PC.

The command line for running a test suite is:

> testdriver run -p <platform> -b <build> -s <suite> [-t transport] [-a architecture] [-l rdebug|console] [-c collection path]

The following arguments and options are used.

`-p`	This is mandatory, used to specify the platform. Options are `arm4`, `armv4`, `armv5`, `wins`, `winscw`.
`-b`	This is mandatory, used to specify the build type. Options are `udeb` and `urel`.
`-s`	This is mandatory, used to specify the suite which is to be built. An example of using the `-s` option is: `-s testsuite1.testsuite4`.
`-t`	This is optional, 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 a device.
`-a`	This is optional, 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 -a misa`
`-l`	This is optional and used for collecting test results via the communication port (`rdebug`) or from a .log file (`console`).
`-c`	This is optional, and is used for specifying your own location for storing test logs and test results, other than the default results repository used by the Test Driver.
`-h`	This is optional, and displays help information.

Running test suites

Command line syntax

See also