Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Convert to ROS2 rostest #23

Closed
davetcoleman opened this issue Feb 22, 2019 · 4 comments
Closed

Convert to ROS2 rostest #23

davetcoleman opened this issue Feb 22, 2019 · 4 comments
Assignees

Comments

@davetcoleman
Copy link
Member

MoveIt 1 uses rostest a fair amount. In ROS 2 the exact replacement is still under development according to @wjwwood so there is not great documentation yet.

This issue will track the progress of us understanding how to do the conversion.

@wjwwood
Copy link
Contributor

wjwwood commented Feb 23, 2019

This is probably a better link than that discourse post:

ros2/launch#161 (found via the ROS 2 Dashing ticket: ros2/ros2#607)

The above gets you the functionality of rostest, but not an XML frontend, if you're wanting to continue use that pattern like rostest from ROS 1, that's also being worked on, but tracker here:

ros2/launch#163 and ros2/design#207 (again via ROS 2 Dashing ticket: ros2/ros2#607)

There was also the idea to support existing roslaunch and rostest files from ROS 1, but that's not being tracked anywhere, and I am not aware of anyone working on it or any of the technical risks for it.

JafarAbdi pushed a commit to JafarAbdi/moveit2 that referenced this issue Oct 28, 2019
…ng_interface

Starting point moveit_ros_planning_interface
@shivaang12
Copy link
Contributor

@davetcoleman I was looking for testing relate stuff for Moveit hackathon tomorrow. Let me know if there are any specific thing you want to get done.

@davetcoleman
Copy link
Member Author

@shivaang12 this is a better question for @henningkayser as he leads MoveIt 2 development

@tylerjw is there a place to get CodeCov reports outside of specific PRs? Like a badge we can put on the README? Would be good to point @shivaang12 there.

See also: Integration/Unit Tests Tutorial

@henningkayser
Copy link
Member

Closing this, remaining efforts are discussed in #216

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants