@floris Sligthly of topic but probably helpful: As long as performance of the test infrastructure is not critical for you (in most cases not the case) and the effect of Pythons GIL on multi-threading is no issue for you (usually not the case as well) or could be workaround with multiprocessing (unfortunately limited by the machines # of "real" processors) I would recommend to use `pytest` for "physical integration testing" instead. I consider `gtest` and `rostest` suitable for "ROS node/nodelet unit testing" only so far. In case several ROS nodes/nodelets are executed (in production) on a single machine they can be suitable for "ROS node/nodelet integration testing" as well. As soon as ROS nodes are executed (in production) on "physically separated" machines w.r.t. to application context `gtest` and `rostest` is a rather bad fit (because "too far" from production). However I am open for productive disagreement/feedback :) --- [Visit Topic](https://discourse.ros.org/t/revising-the-gtest-tutorial/4588/4) or reply to this email to respond. If you do not want to receive messages from ros-users please use the unsubscribe link below. If you use the one above, you will stop all of ros-users from receiving updates. ______________________________________________________________________________ ros-users mailing list ros-users@lists.ros.org http://lists.ros.org/mailman/listinfo/ros-users Unsubscribe: