Revision as of 13:01, 10 September 2010

OTS User Documentation

Related Documentation

• Quality/QA-tools/OTS/Glossary

OTS Worker

Conductor

Conductor is a component in OTS Worker. Basically it does three things:

1. Prepare the test target (e.g. device) for testing by using user-defined script (see Custom Flasher below).
2. Execute testrunner-lite at Worker once for each test package.
3. Send test results to OTS server (this applies only if initiated from OTS server)

Conductor has got a command line interface. It can be used to manually execute one or more test packages from Worker PC. In this case, sending test results to OTS server is disabled. The test results are collected to a local folder (~/conductor/None) from where the user can examine them.

Here's an example how to process two test packages using Conductor on command line:

# sudo conductor -u http://my.build.host/sw/image/file -t mypackage1-tests,mypackage2-tests

The URL in above command is ignored if Custom Flasher is not available.

Custom Flasher

Custom Flasher is used by Conductor to set up and prepare the test target before the testing may begin. Typically this includes flashing the software image to hardware that is serving as the test target and then booting up the hardware.

Conductor tries to import Python module named customflasher. If it cannot be imported, Conductor simply skips the phase of preparing the test target.

By implementing your own customflasher module you can define all the steps and maneuvers that are required to get your test target ready for test execution. The source code of Conductor includes a reference implementation for customflasher in defaultflasher.py file.