How to run tests remotely

You can use the TestDriver to run the test packages remotely over a TCP/IP network. To do this, you must install TestDriver on the local host, and configure using the 'testdriver config' command. The client and the server reside inside the TestDriver and are installed with the TestDriver.

As WinTap can interfere with remote connections, you must set the following to ensure that the primary TCP connection is listed first:

  • Go to Start > Settings > Network and Dial-up connection

  • Select Advanced > Advanced Setting...

Setup

The following illustration shows the complete setup required to run tests remotely. The client and server shown seperately in the illustration are an integral part of the TestDriver. The Server program (TestMaster) accepts the TestDriver jobs and executes the test jobs on a first in first out basis.

Workflow for running tests remotely


Workflow for running tests remotely

TestDriver Remoting


TestDriver Remoting

Note: The TestClient and TestMaster are now integrated into the TestDriver. You must install TestDriver on the local and remote host and configure both sides using the testdriver config command. Use the supported devices.

Some of the terms used in the test setup are as follows:

  • TestMaster - The TestMaster is a software program that must be running on the Server, to run remote tests. The TestMaster receives test jobs sent by the TestClient, and then passes them on to the TestDriver, which executes the tests on the device.

  • TestDriver - The TestDriver runs both the client and the server in order to create test packages which form part of the test jobs to the TestMaster, and then executes the tests on the device. For more information on using TestDriver and creating test packages, see Using TestDriver and Building test packages.

    When several test jobs are to be processed, they are placed in a queue by the TestMaster, and progress information is sent either directly (synchronous mode) or can be retrieved when needed (asynchronous mode).

  • Test job - The test job is created on the client and contains the test package (created by TestDriver) and the ROM image file to be used while running tests on the device.

  • Test package - The test package contains tests to be executed by the TestDriver on the device.

  • Test results - The test results are stored on the server as testresult.zip file, and can be retrieved by the client.

Workflow process

When using TestDriver to run tests remotely over a network (WAN or LAN) in asynchronous mode, the workflow processes on the server and client sides are as follows:

Server side process

  • Install TestMaster with the TestDriver on the PC. For details, see Installing the TestDriver.

  • Connect a device to the server to run the tests on it.

  • Check for the status, 'TestMaster running', on the console.

Client side process

The following is the general process to follow to run tests remotely in asynchronous mode.

  • Install the TestDriver on the PC that acts as the client as outlined in Installing the TestDriver.

  • Create the test package containing tests to be executed on the device, using TestDriver. For more information on creating test packages, see Building test packages.

  • Create the test job, by placing the test package and the ROM image to be used for tests in a directory, for example testjob1.

  • Submit the test job using the runremote command with the relevant options (see How to run test packages remotely).

    The test job is then sent to the TestMaster for execution. If several test jobs are to be executed on the server, they are held in a queue.

    When the test job is ready to run, it is sent to the TestDriver, which executes the tests (defined in the test package) on the device, using the ROM image supplied with the test job.

    If you are running a test job in synchronous mode, progress information on the status of the test job is displayed automatically.

    If you are running a test job in asynchronous mode, you can check the status of the test job any time, using the command testdriver jobstatus, as described in How to run the test packages remotely.

  • Define the directory location for collecting the test results on the client side.

  • Retrieve the test results from the server to the client using the testdriver results command. The results are stored in a testresult.zip file, within the defined location.

  • View the results by opening the HTML report included in the testresult.zip file.

For more information on running the test jobs, see How to run the test packages remotely.