Currently the pyros tests are testing integration with sample ROS systems.
While it is very useful to ensure everything is working as expected (versus requiring specs/mock during unittest & have integration tests at a later stage), it triggers a conflict between :
ROS is inherently multiprocess.
Python Test Framework are by default "mono process", loading only one interpreter to run all tests.
After chatting with @stonier, another possible solution might be to use roslaunch or rosunit/rostest to launch a ROS node in its own subprocess. We need to investigate if this is doable in suchcases.
Currently the pyros tests are testing integration with sample ROS systems.
While it is very useful to ensure everything is working as expected (versus requiring specs/mock during unittest & have integration tests at a later stage), it triggers a conflict between :
Possible solutions are :