Collapse all Symbian^3 Product Developer Library

Running Tests using TestDriver

Install STAT to enable the Communication between the PC and the device under test.
If you are using ARMv5, the hardware reference board (for example, H4) must be connected to the PC through USB, serial cable, BT or TCP/IP connection. TestDriver uses STAT application on the device to communicate with the PC and the device. For more details, refer to Symbian Verification Suite » TestDriver » Using TestDriver » Communicating with the device.

The ROM image is built on the PC and transferred to the hardware board using a MMC card.
Configure the TestDriver using the automated scripts located at …\syslibsapitest\syslibssvs\group\
testdriversetup

testdriversetup.bat calls testdriversetup.pl which applies an appropriate set of configuration parameters.
Build test code using the following command:

testdriver build –p <winscw/armv5> –b <urel/udeb> –s syslibs[.ecom[.<test suite name >]]

Note: You can execute TestDriver commands from any location.

For the SysLibs testdriver test suite structure, refer to Building and Execution section.
If you are using ARMv5, build the ROM image using the following command:

buildrom -D_STARTUPMODE2 -D_EABI=ARMV5 -DRVCT -DUSE_STRONG_CRYPTOGRAPHY <h2/h4hrp> techview_statapi
Run the tests.
For ARMv5:

Run the following command:

testdriver run -t <transport service used>

Transport service used can be “serial<COM port number that is connected to the board>”, “bt<COM port number for BT dongle>”, or “usb<mapped port number>.”

For WINSCW:

Run the following command:

testdriver run

Note: All scripts and test data are automatically removed from the system drive of the device under test after the execution.

Parent topic: Building and Running the Tests