Revision as of 08:39, 1 April 2011

OTS Usage

Test execution

Using conductor

Conductor is the executer in the ots-worker. You can use conductor to test device flashing and for semi-automatic test executions.

To test flashing and basic test execution:

conductor --imageurl=http://192.168.1.1/image.tar.gz 

The conductor flasher the image to the device and executes all available test packages.

To list all supported options:

conductor --help

Using ots_trigger

Note: Before starting to execute tests with ots_trigger, verify that your ots-worker is configured correctly. That can be done with conductor, see the topic above.

ots_trigger is tool for triggering a testrun to OTS server.

How to install ots_trigger.

Before you can trigger a testrun, you need to have all following:

• OTS server up-and-running [1]
• OTS worker with hardware configured [2]
• Image with eat-device package (enabled test automation environment to hardware) [3]

And one of the following options:

• Test package installed to the device
• Test package installed to the ots-worker or
• Test plan [TODO LINK]

Okey, now we are ready to get dirty.

If we have test package(s) installed into the device and we want to execute all of them:

ots_trigger --server=192.168.1.1/xmlrpc --build_id=nightly_testing --image=http://url.to.image/image.tar.gz --sw_product=meego_n900 --email=my.name@company.com

Let me explain the parameters.

• server: Defines the address of the OTS server. If you are not using logger plug-in, the address is then 192.168.1.1:8080.
• build_id: Free string to define the image build id.
• image: Url path where the image is located. Yes, it must be on the http server.
• sw_product: The default SW test execution options, you have defined the sw_product in /etc/ots_server.conf.
• email: Who has requested the testrun and to whom to send notifications.

That was simple. Next you want to execute only one package, no problem, just define test package name to ots_trigger:

ots_trigger --server=192.168.1.1/xmlrpc --build_id=nightly_testing --image=http://url.to.image/image.tar.gz --sw_product=meego_n900 --email=my.name@company.com --testpackages=my-test-package1-tests

In to the testpackages option, you can define multiple packages like this:

--testpackages=my-test-package1-tests,my-test-package2-tests

If you want to add more people to receive email after the execution is done, just add more email addresses to --email option:

ots_trigger --server=192.168.1.1/xmlrpc --build_id=nightly_testing --image=http://url.to.image/image.tar.gz --sw_product=meego_n900 --email=my.name@company.com,second.name@company.com

If you have test package installed to your ots-worker machine, that can be executed with --hostpackages:

ots_trigger --server=192.168.1.1/xmlrpc --build_id=nightly_testing --image=http://url.to.image/image.tar.gz --sw_product=meego_n900 --email=my.name@company.com --hostpackages=my-test-package1-tests

For optimizing the execution time, see distribution models section below.

To list all supported options:

ots_trigger --help

Distribution models

Default

Perpackage

Optimized