Migrating from TestDriver v1.0
This section lists the interface breaks introduced in TestDriver v2.x and
helps in migrating from TestDriver v1.0 to TestDriver v2.x.
-
TestDriver v2.x uses a separate .sis file for each task
element in the driver hierarchy. This is to allow:
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.
-
The ouput breaks from TestDriver v1.0 ouput as it uses standard Java
Logging. The output still conforms with ScanLog.pm standards.
The following mitigation actions need to be taken:
-
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).
-
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.
-
Use the API to monitor the TestDriver.
-
As Java is being used, the TestDriver must be run as a
cmd or a java program and not as an
executable file, this causes a break.
The following mitigation actions must be taken:
-
TestDriver config command introduces a break because the
switches are 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 (For example, build ,
run , and so on). Only TestDriver config has changed.
The following mitigation actions must be taken:
-
As configuration is now persisted over installs, the
config command must be called only once.
-
TestDriver now enables you to export, import and clear the
configuration details, allowing you to bypass the config switches.
-
Installing, configuring and running the server for TestDriver
Remoting introdued a break.
The following mitigation actions need to be taken:
-
TestDriver v2.x requires RVCT 2.2 or later version to run the tests.
The system must have RVCT2.2 installed and path variable must be set to 2.2
version. TestDriver running on Symbian OS versions earlier than 9.x needs RVCT
2.1.
The following mitigation actions need to be taken:
To run TestDriver v2.x, ensure that your PC has both RVCT 2.1 and
2.2, and you toggle the path variable when switching tests run for v8.1 and
v9.xx builds.
For additional information on interface breaks, see
TestDriver v1.0 Migration Guide.
Copyright ©2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. License: SFL
|