Migrating to TestDriverV2

This section lists the interface breaks introduced in TestDriver v2 and helps in migrating from TestDriver V1 to TestDriver V2.

1. TestDriverV2 uses a separate .sis file for each task element in the driver hierarchy. This is to allow:

   • isolation of each test

   • small SIS files to transfer, allowing larger .driver files, ease of maintenance and quicker running of a single small test.

   When a main task and a sub task try to share the same .sis file, the .sis file fail to install and throws -10147 KErrSISWouldOverWrite error.

   To overcome this, optimise the task to avoid duplicates of files. Edit the XML input files or use the prototype Test Manager to edit the files appropriatly. Navigate to the sub task that created the offending SIS file, check if any of the files transfered to the board are present in the main task.

2. The ouput breaks from TestDriver v1 ouput as it uses standard Java Logging. The output still conforms with ScanLog.pm standards.

   The following mitigation actions need to be taken:

   1. Modify the logging.properties file to display results in a way you want, using a handler (email, console, file, netsend), formatter (simple, simpler, xml stream) or level (info, warning, severe).

   2. The TestDriver output files are created on completion of each task. These files are used to get the progress information. Other outputs, for example, html files are created using XSLT.

   3. Use the API to monitor the TestDriver.

3. Since Java is being used, the TestDriver needs to be run as a cmd or a java program and not as an executable, this causes a break.

   The following mitigation actions need to be taken:

   • Run TestDriver XXYY.

   • Run TestDriver.cmd XXYY.

   • Run java -Djava.rmi.server.codebase=file:/./plugins/com.symbian.driver.core_1.0.0.jar -jar ./plugins/com.symbian.driver.core_1.0.0.jar XXYY.

4. TestDriver config command introduces a break due to switches conflicting with other TestDriver command switches.

   To mitigate this problem, a uniform TestDriver command line was created changing all duplicate and erroneous config switches to conform to the other commands (e.g. build, run etc). Only TestDriver config has changed.

   The following mitigation actions need to be taken:

   • Configuration is now persisted over installs, hence config command needs to be called only once.

   • TestDriver now allows you to export, import and clear the configuration details, allowing you to bypass the config switches.

5. Installing, configuring and running the server for TestDriver Remoting introdued a break.

   The following mitigation actions need to be taken:

   • Configure the TestDriver Server/Master to the following:

     • --jobs <directory>: Location where the server keeps the input package it receives from the client

     • --port <number>: Port to perform the ROM flashing with trgtest.exe

     • --repos <directory>: Location where the server unzips the test build.

     • --server <hostName>: Name of the server (type ">hostname" on the server command line)

     • --service <name>: A user friendly service name e.g. RemoteTestDriver

     • -e <directory>: Location of the EPOCROOT variable.

     • -x <dir>: Location of XML root.

     • -t <transport>: The mode of connection to the board, for example, serial3, USB.

   • Run the server using the command 'TestDriver master'.

6. TestDriver v2 requires RVCT 2.2 or later version to run the tests. Hence, the system need to have RVCT2.2 installed and path variable set to 2.2 version. TestDriver running on Symbian OS version below 9.xx needs RVCT 2.1.

   The following mitigation actions need to be taken:

   To run TestDriver v2 ensure that the machine has both RVCT 2.1 and 2.2 and should toggle the path variable when switching tests run for v8.1 and v9.xx builds.

For additional information on interface breaks, see TestDriverV2 Migration Guide.

• Command Reference