[quote="fkromer, post:1, topic:2667"]
According to Developer Guide - Testing (ros2 wiki) Library unit testing (level 1) is done with gtest, unittest, nosetest (mainline C++ and Python) like in ROS1.
[/quote]
ROS 2 tries to be less opinionated than ROS 1. While `gtest`, `unittest`, and `nosetest` are supported (and heavily used to test ROS 2 code) they are not the only way. Integration with these tools is optional. E.g. ROS 2 also supports `gmock` (which ROS 1 doesn't do because of its difficult interaction with `gtest` when packaged separately). All of these testing frameworks are integrated using different ROS 2 packages. So adding support for more should be straight forward.
[quote="fkromer, post:1, topic:2667"]
But what about ROS node unit testing (level 2) and ROS node integration testing (level 3)? In ROS1 people ended up to develop custom solutions to do ROS node unit and integration testing because the restrictions and lack of useability of rostest, lack of generic tests nodes, etc.
[/quote]
At the moment we are using ROS 2 launch files as a replacement to an explicit `rostest` command. The package [launch_testing](
https://github.com/ros2/launch/tree/master/launch_testing) provides a few different ways to check the result of a test node. This can be either a simple return code of one process (which decides on the result of the launch file and tears down all the other processes) or it could rely on specific output to be printed (matched by plain strings or regex). While the current syntax and API is everything but pretty it is functional and we use that to cover a lot of ROS 2 code. E.g. the `demo_nodes_cpp` providing simple talker, listener and services are tested using that. Since the same [launch file template](
https://github.com/ros2/demos/blob/c6dd83c29115e056099dfc9fe3d48b35ca34e1d1/demo_nodes_cpp/test/test_executables_tutorial.py.in) is being used for multiple cases in this package it is a bit more complicated but it should provide an idea what is possible
and how it works.
---
[Visit Topic](
https://discourse.ros.org/t/test-framework-in-ros2/2667/2) 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: <
http://lists.ros.org/mailman//options/ros-users>
(text/plain)