(→How to add support for custom test target) |
|||
| Line 25: | Line 25: | ||
=== How to add support for custom test target === | === How to add support for custom test target === | ||
| - | The user must implement Python module ''customflasher'' and have it available in PYTHONPATH in Worker PC. In that module, the user can define all the steps and maneuvers that are necessary before his/her test target is ready for test execution. | + | The user must implement Python module ''customflasher'' and have it available in PYTHONPATH in Worker PC. In that module, the user can define all the steps and maneuvers that are necessary before his/her test target is ready for test execution. ''Customflasher'' is required to leave test target in such a state that establishing an SSH connection from Worker PC to the test target will succeed. |
Conductor source code includes a reference implementation for ''customflasher'' in [http://gitorious.org/qa-tools/ots/trees/master/ots.worker/ots/worker/conductor/defaultflasher.py defaultflasher.py] file. | Conductor source code includes a reference implementation for ''customflasher'' in [http://gitorious.org/qa-tools/ots/trees/master/ots.worker/ots/worker/conductor/defaultflasher.py defaultflasher.py] file. | ||
Contents |
OTS Worker comes with a component named as Conductor. Conductor includes a command line interface that can be used to manually execute one or more test packages from Worker PC. The test result files are collected to a local folder (under ~/conductor/None) from where the user can examine them.
Here's an example how to process two test packages using Conductor from command line:
# sudo conductor -u http://my.build.host/image --dontflash -t mypackage1-tests,mypackage2-tests
The URL in above command is ignored.
Custom Flasher is a component used by Conductor to set up and prepare the test target for the test execution from Worker PC. Typically this includes flashing the software image to hardware that is serving as the test target, and then booting up the hardware.
The user must implement his/her own Custom Flasher for Conductor to be able to prepare the test target.
If Custom Flasher is not available at Worker PC, Conductor skips the phase of preparing the test target. Typically this behaviour is useful only when running Conductor manually from command line.
The user must implement Python module customflasher and have it available in PYTHONPATH in Worker PC. In that module, the user can define all the steps and maneuvers that are necessary before his/her test target is ready for test execution. Customflasher is required to leave test target in such a state that establishing an SSH connection from Worker PC to the test target will succeed.
Conductor source code includes a reference implementation for customflasher in defaultflasher.py file.