verify how to start/stop modules (i.e. simulator) within testing infrastructure about robot-testing-framework HOT 3 CLOSED

It may also be interesting to investigate how to automatically start the yarpserver, it seems a feature users are interested in, see robotology/yarp#394 (comment) .

from robot-testing-framework.

Well, this is where the RTF becomes useful. A fixture manager can be assigned for every test suits which does the job. For YARP, there is the yarpmanager fixture manager implemented in the icub-tests repository. A set of modules (simulator, robot interface,...) can be arranged in a XML file and given to the yarpmanager fixture manager in the test suite. The yarpmanager runs all the modules, establishes the connections and monitors that the modules are properly running during the test run. If one of the modules crashes (i.e., fixture collapses) during the test run, the yarpmanager retry to run the modules and rerun the test suit. Here is an example:

<suit name="Camera Test Suite">
    <description> Testing icubSim cameras</description>
    <environment>--robotname icubSim</environment>
    <fixture param="--fixture myapp.xml"> yarpmanager </fixture>
    <test type="dll" param="--from right_camera.ini"> CameraTest </test>
    <test type="dll" param="--from left_camera.ini"> CameraTest </test> 
     ...
</suit>

Where myapp.xml is a usual yarpmanager application file!

from robot-testing-framework.

accomplished in the new framework.

from robot-testing-framework.