Introduction to running tests remotely

It is possible to use TestDriver to run test packages remotely over a TCP / IP network (Wide Area or Local Area Network), via a TestClient and TestMaster interface.

The following diagram shows the overall setup when running test remotely:

• TestClient - The TestClient is a software program that needs to reside on the Client in order to be able to send tests (packaged as test jobs) to the Server and execute them via the TestMaster. If several test jobs need to be processed they are placed in a queue by the TestMaster, and progress information is sent either directly to the TestClient (synchronous mode) or can be retrieved when needed (asynchronous mode).

• TestMaster - The TestMaster is a software program that needs to run on the Server in order for the remote test execution to work. The TestMaster receives test jobs sent by the TestClient, and then passes them on to the TestDriver, which executes the tests on the Lubbock development board.

• Lubbock development board - This is the development board on which tests are executed using TestDriver. The board needs to be connected to the Server via a null modem cable and a power supply.

• TestDriver - TestDriver needs to be run on both the Client and Server in order to create test packages which form part of the test jobs sent by the TestClient to the TestMaster, and then to execute the tests on the Lubbock development board. For more information on using TestDriver and creating test packages, see Using TestDriver and Building test packages.

• Test job - The test job is created on the Client side and sent to TestMaster by the TestClient. The test job contains the test package (created by TestDriver) and the ROM image file to be used when executing the tests on the development board.

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

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

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 and TestDriver on the PC to be used as the Server.

• Connect a Lubbock development board to the Server. The tests will be run on this development board.

• Check the status of the TestMaster on the console. The status should be "TestMaster running".

Client side process

The following is the general process to follow if you are to execute tests remotely in asynchronous mode.

• Install TestClient and TestDriver on the PC to be used as the Client.

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

• Create the test job, by placing the test package created and ROM image to be used for the 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 sent to the TestMaster and, if there are several test jobs waiting to be executed on the server, it will be held in a queue.

  When it is ready to be run, the test job will then be sent to the TestDriver, which executes the tests (defined in the test package) on the Lubbock development board, 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 will be displayed on the TestClient automatically.

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

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

• Retrieve the test results from the Server to the Client using the testdriver results command. The results will then be stored in a testresult.zip file, within the defined location.

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

More detailed information on the above steps are available in How to run test packages remotely.

• Installing software for remote testing

• How to run test packages remotely

• Using TestDriver