Quality/QA-tools/OTS/DeveloperDocs/CoOperationBetweenOtsConductorAndTestrunnerLite

Co-operation with testrunner-lite

OTS worker starts conductor (part of OTS) for each test run. Conductor starts testrunner-lite, a tool for running tests on remote devices according to Test Plan XML. More information in testrunner-lite wiki: http://wiki.meego.com/Quality/QA-tools/Testrunner-lite.

Usage:

testrunner-lite [options]

Example:

testrunner-lite --file=tests.xml --output=~/results.xml --verbose

For a complete list of options run

testrunner-lite --help

How OTS conductor starts testrunner-lite

Conductor starts testrunner-lite using command line interface (CLI) inside the same shell. Conductor runs a base testrunner-lite command with some extra options resolved from the test run options.

Base command example without extra options:

/usr/bin/testrunner-lite --semantic --verbose --automatic --ci --file=/path/to/some-package-tests.xml --output=/path/to/some-package-results.xml --logid=1

Example with some extra options currently supported by OTS:

/usr/bin/testrunner-lite --semantic --verbose --automatic --ci --file=/path/to/some-package-tests.xml --output=/path/to/some-package-results.xml --logid=1 --filter="some-test" --logger=/logger/ots/%s/ --target=root@some.host --rich-core-dumps="/path/to/richcore-dumps" --resume=exit

Signaling between OTS conductor and testrunner-lite

There are currently three cases where conductor and testrunner-lite communicate using POSIX signaling.

Connection failure

Edit page for the sequence diagram

Intentional (explicit) reboot

Edit page for the sequence diagram

Expected reboot

Edit page for the sequence diagram