Introduction to TestDriverV2

TestDriver is an automation engine used to build, package and run a series of Symbian OS tests on a PC and on the Symbian OS device or on an emulator from a PC. It automatically runs the tests, retrieves the logging information through a tool called STAT and produces a report indicating the success or failure of the test.

TestDriverV2 (TestDriver version 2) is refered as TestDriver all through this guide.

Following are some of the main advantages of TestDriverV2 over TestDriverV1:

• Uses a simplified input format (schema) unlike the TestDriverV1 which uses 6 DTDs + a File Hierarchy Model.

• Uses a schema to automatically run anything on the PC or the Symbian Device and transfer the information between the two, thus enhancing the versatility and functionality of the TestDriver.

• Performs the PC command line tasks, Symbian command line tasks, transferring between the two systems in addition to running tests (organised as tasks).

• Validates paths and XML syntax before running tests.

• Supports the usage of wildcards and variables when you transfer the filenames.

• Displays results in XML and HTML format for easy XSLT transformation.

• Supports the usage of full URL for the –s tag for the new .driver files. This allows you to use the driver files located anywhere on your system.

• Remembers the last option that was run with a command.

• Provides binary compatible commands except config, where switches conflict with switches of other TestDriver commands.

• Supports advance logging levels (for example, info, warning, fine), different formats (for example, XML, text, stream) and different handlers (for example, email, console, net-send).

• Supports multiple TestDriver instances.

• Supports bldmake and bldclean options.

To use the TestDriver, you need to define an XML file that describes your tests. You also need to install and configure the TestDriver before building or running a test. This guide describes how to configure the TestDriver, build tests into a repository on your machine, run tests on a target device, and view the test logs and test results.

TestDriver is provided as a part of the Symbian OS Development Kit and is installed using the Symbian Engineering Tools installer.

The following sections guide you through topics that are required to use TestDriverV2:

1. TestDriver requirements

2. TestDriver input

3. Using TestDriver

4. TestDriver output

5. Migrating to TestDriver V2

6. Common errors

TestDriver V2 introduced the following interface breaks:

1. TestDriver V2 always uses STAT to reduce the number of defects caused by the code written specifically for the emulator. To enable this you must use WinTAP or a similar loopback mechanism.

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

3. Usage of ScanLog.pm standard for logging the message introduces a break.

4. 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.

5. Usage of config command introduces a break due to switches conflicting with other TestDriver commands.

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

Migrating to TestDriver V2 provides more information on breaks and the mitigation actions to be taken to migrate to TestDriver V2.

• STAT tool

• SIS files