Running the Test

The create, manage and run configurations has to be set before running the test. This will not be changed often. The execution of a test project is performed by running the TestDriver. The .driver file specifies the test suite and tasks to be executed in both phases that is both Build and Run. Once the .driver file is created a request for a build and/or a run of the tests from the same perspective can be made.

Complete the following steps to run the .driver file:

  1. Click Run > Run to launch the Run dialog box. The Run command can also be given by right-clicking the .driver file in the Navigator window and then selecting Run As > Run.

    The create, manage and run configuration dialog box has four tabs: Main, Arguments, Device, and Common.

  2. From the main tab, select TestDriver configuration type and create a new create, manage and run configuration by clicking the top left icon or right-click the .driver file and select New.

    Run dialog box


    Run dialog box

  3. Type the Name for the new create, manage and run configuration.

  4. Set the Driver Location and Suite fields. In the Test Target group box, Driver Location is the location of the .driver file on the PC, and Suite is the name of the driver file. The Command that can be given are Build, Run, and Build and Run. The platform target, and the variant can also be specified.

  5. Click the Arguments tab to specify the Paths variables, Build Options, Test Execution Framework Options.

    Arguments dialog box


    Arguments dialog box

    In the Path Variables group box the following must be set:

    • Epoc Root: This is the drive where the Epoc32 tree has been installed.

    • Source Root: This is the source path that replaces the variable ${sourceroot} in the .driver file.

    • Repository Root: This is the path where TestDriver creates (at build phase) the repository of the sis files preserving the test suites hierarchy.

    • Result Root: This is the path where TestDriver creates (at run phase) the test results preserving the test suite hierarchy.

    Rebuild repository without rebuilding the code rebuilds the repository without rebuilding the code which corresponds to TestDriver command rbuild. Run clean on build must also be selected. The TEF option must be selected if the test is run on the H4 board. For further information, refer to TestDriver command reference documentation.

  6. The Hardware options and the Emulator options must be set.

    Device dialog box


    Device dialog box

    In the Hardware options the following can be set:

    • Install to sys/bin for STATLite: This option is selected only if using STATLite instead of stat to communicate with the device.

    • Transport: Select the means of transport between the PC and the hardware. board.

    • IP address: This is used only when NT/RAS option is selected. If COM1 is used :

      transport=serial and port=1

      If NT/RAS is selected in Transport then

      transport=NT/RAS, IP=xx.xx.xx.xx and port=xxxx

      where, port is a four digit number.

    • Port Number: This is the port number for the Serial, USB, Bluetooth and NT/RAS. For Serial and Bluetooth it is the COM PORT, for USB it is the USB port, and for NT/RAS it is the NT/RAS port which is usually 3000.

    • RDebug port: This is the com port used for RDEBUG testing such as COM2.

  7. Click Run to run the TestDriver.

These create, manage and run configurations will be preserved for the current workspace.