How to run test packages remotely

When executing tests remotely, you first need to create a test package using TestDriver, and specify the ROM image to be used for the test. You then need to include the test package and ROM image in a test job, and send it to the TestMaster on the server side, using TestClient.

If several test jobs have been submitted, the test job will be placed in a queue by the TestMaster and then executed by TestDriver on the Lubbock development board. It is possible to check the progress status of the test job at any time.

The following sections describe the commands and arguments to use when running test packages remotely. These include executing the test packages remotely (either synchronously or asynchronously), cancelling a test job, checking the status of TestMaster, checking the status of the test job, and retrieving the test results.

For further information on creating the actual test packages, see Building test packages.

The command line syntax for running a test package remotely is as follows:

>testdriver runremote -m <mode> --tp <testpackage> -i <working_path> -r <rom_image> --srv <remote_server> --cl <client_name>

The following arguments and options are used with the runremote command.

-m <mode> Specifies whether the user should receive results and updates synchronously (while the job is being processed), sync, or asynchronously (any time after the job has finished), async. --tp <testpackage> Specifies the name of the test package to be used. -i <working_directory> Specifies the current working directory for all the input files (ROM image file and test package) to be submitted to the TestMaster. This is also the location in which all the results will be generated when processing a job in sync mode. [-r <rom_image>] Specifies the name of the ROM image file to be used. This is optional. If specified, the Lubbock development board will be flashed. [--srv <remote_server>] Defines the host name or IP address of the remote PC and the name of the remote service, for example //lon-test01/RemoteTestDriver or //100.16.163.146/RemoteTestDriver. This is optional and if specified, the values in the client.properties file are overridden. [--cl <client_name>] Defines a unique name for registering the client with the TestMaster in sync mode.

To request the status of the TestMaster processes running on the Server, use the following command:

>testdriver masterstatus --srv <remote_server>

It is possible to check the status of the TestMaster at any time.

The sync/async mode allows you to specify how to receive progress information about the test job - either synchronously (sync) or asynchronously (async).

The following is an example of how to run tests synchronously:

>testdriver runremote -m sync --tp samplelegacysuite.tpkg -i D:\MyJobs\SomeJob -r sys$rom.zip --srv //lon-test01/RemoteTestDriver --cl foo

When using the sync mode, the TestClient will stay connected to the TestMaster in order to receive progress information.

The following is an example of running test packages remotely in asynchronous mode:

 >testdriver runremote -m async -i D:\\MyJobs\SomeJob --tp samplelegacysuite.tpkg -r sys$rom.zip 

When using the async mode, the TestClient will submit the test job to the TestMaster and then disconnect. It is then possible to retrieve progress information about the test job at any time using the jobstatus command (see below).

To check the status of a job that has been sent from the TestClient to the TestMaster, use the following command:

>testdriver jobstatus -j <job_ID> [--srv <remote_server>]

where:

<job_ID> is the unique identifier assigned to the job by the TestMaster, for example 1, 2 or 3 etc..

The status will show whether the job is still waiting in a queue or has been submitted, is executing, or has been completed. This command can be used at any time, but it is especially useful for requesting an update when the async command has been used.

To cancel a job that is being held in a queue by the TestMaster, type the following command:

>testdriver cancel -j <job_ID> --srv <remote_server>

where:

<job_ID> is the unique identifier assigned to the job by the TestMaster, for example 1, 2 or 3 etc..

--srv <remote_server> defines the host name or IP address of the remote PC and the name of the remote service, for example //lon-test01/RemoteTestDriver or //100.16.163.146/RemoteTestDriver. This is optional and if specified, the values in the client.properties file are overridden.

To check the test results produced after the job is finished, use the following command:

>testdriver results -j <job_ID> -c <collection_path> [--srv <remote_server>]

where:

<job_ID> is the unique identifier assigned to the job by the TestMaster, for example 1, 2 or 3 etc..

<collection_path> is the directory where the results are stored as HTML reports in a file called testresults.zip.

--srv <remote_server> defines the host name or IP address of the remote PC and the name of the remote service, for example //lon-test01/RemoteTestDriver or //100.16.163.146/RemoteTestDriver. This is optional and if specified, the values in the client.properties file are overridden.

• Introduction to running tests remotely

• Installing software for remote testing

• Using TestDriver