Unfortunately, the camera ran out of "SD card" during the discussion. :|
Workshop Abstract: pub.uni-bielefeld.de/publication/2602725
There were basically two remarks:
1) SCXML syntax which is not user friendly!
→ Answer: We already working on a INI syntax for automated SCXML generaton.
2) Maybe there is a need for more (rich) information about the scenario?
→ Answer: We could embed RDFa in the SCXML file!
Result: We will try to integrate FSMTesting in MORSE!
Robot simulators, like the MORSE project, provide a safe and readily available environment for robot system testing, reducing the effort for testing drastically. In principle, simulation testing is automatable, and thus a good target for Continuous Integration (CI) testing. However, so far, high-level scenario tests still require complex component setup and configuration before they can be run in the simulator. An added complication is, that there is no standard for starting, configuring, or monitoring software components on todays robots. Often, high-level tests are carried out manually, implementing a tailored solution, e.g, via shell scripts or launch files, for a specic system setup. Besides the eort of manual execution and supervision, current tests mostly do not take timing and orchestration, i.e., required process start-up sequence, into account. Furthermore, successful execution of components is not verfied, which might lead to subsequent errors during the execution chain. Most importantly, all this knowledge about the test and its environment is implicit, often hidden in the actual implementation of the tailored test suite. To overcome these issues, this contribution introduces a generic and congfiurable state-machine based process to automate a) environment setup, b) system bootstrapping, c) system tests, d) result assessment, and e) exit and clean-up strategy.