(Created page with "= OTS User Documentation = == Related Documentation == * Quality/QA-tools/OTS/Glossary == OTS Worker == === Conductor === Conductor is a component in OTS Worker. Basical…") |
|||
| Line 10: | Line 10: | ||
Conductor is a component in OTS Worker. Basically it does three things: | Conductor is a component in OTS Worker. Basically it does three things: | ||
| - | # Prepare the test target (e.g. device) for testing by calling user-defined external tool (see | + | # Prepare the test target (e.g. device) for testing by calling user-defined external tool (see Custom Flasher below). |
# Execute testrunner-lite at Worker once for each test package. | # Execute testrunner-lite at Worker once for each test package. | ||
# Send test results to OTS server (but this applies only if executing as part of full OTS setup) | # Send test results to OTS server (but this applies only if executing as part of full OTS setup) | ||
| Line 16: | Line 16: | ||
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. | 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 | + | 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 | + | '''sudo conductor -u http://my.build.host/sw/image/file -t mypackage1-tests,mypackage2-tests''' |
| + | |||
| + | ==== Custom Flasher ==== | ||
| + | |||
| + | Custom Flasher is used by Conductor to set up and prepare the test target. 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. | ||
Contents |
Conductor is a component in OTS Worker. Basically it does three things:
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
Custom Flasher is used by Conductor to set up and prepare the test target. 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.