ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question

Testing a fresh ROS installation on Slackware 14.2

asked 2016-09-16 04:12:26 -0600

anilinverse gravatar image

updated 2021-12-03 09:52:30 -0600

Evgeny gravatar image


After a joyful 4 day long session of coffee and swearing in different unparseable languages I can finally say: ROS and Gazebo are compiling from source and working on Slackware 14.2. Now the question:

How can I test a fresh installation of ROS? I'm a little new to it, so I just started roscore, got a beautiful "started core service [/rosout]" and ... what now? I'm browsing through wiki and can't really find a topic entitled "How to check if everything in your ROS is working in 500 easy steps", can anyone help a little or just point me in a general direction? Because I'm pretty sure after what I had to do to the source files to make them compile there should be a plentiful of bugs hidden in there.

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted

answered 2016-09-16 11:05:25 -0600

ahendrix gravatar image

Most packages have unit tests; particularly the core ROS packages. These will cover the basics like publish/subscribe, services, message generation, actionlib, and most of the other things that are testable in a command-line environment.

If you built with catkin_make, running tests is just catkin_make run_tests

If you built with catkin_make_isolated, things may be a bit more complicated; I haven't tried it but I think you can run catkin tests in catkin_make_isolated with catkin_make_isolated --catkin-make-args run_tests

Both commands will output the test status as they build, but you probably don't want to sift through all of that. Both runs should produce junit-style test result files; for catkin_make they'll be in the build folder; for catkin_make_isolated they may be scattered around the workspace.

In either case, catkin provides a small command-line tool that will walk the directory tree, gather test result files and summarize them: catkin_test_results

In addition to running the tests, I'd suggest that you run rviz and rqt manually to verify that they work; the GUI tools are rather difficult to test in an automated fashion.

edit flag offensive delete link more

Question Tools



Asked: 2016-09-16 04:12:26 -0600

Seen: 139 times

Last updated: Sep 16 '16