Interface breaks

TestDriver v2.x introduced the following interface breaks:

  1. It 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. 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.

  5. Usage of config command introduces a because of conflicting switches with other TestDriver commands.

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

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