launch checks fail for cob_controller_configuration_gazebo about cob_robots HOT 3 CLOSED

should be fixed by adding default values
(see fmessmer@7af9e7c)

However, how do rostest launch file checks work? Can't you specify a value for the arguments for each check?
Because we also have several other launch files with launch file arguments, where a default value does not make sense (e.g. the new generic_controller.launch files)

from cob_robots.

we should not put in default values if they make no sense. The workaround is to exclude the files where we need launch arguments without default from the roslaunch tests by renaming them to *.xml. Example see cob_bringup.

from cob_robots.

I think this is no longer an issue as all tests pass with #279
Thus, I think we can close this!

from cob_robots.