There'd be an argument to be made here for test_name, class_name, testcase_name, but I'm easy going on it— would like to get this merged one way or another.

Yes, class_name and testcase_name would be more readable imo.

Can you please create the PR against ros_comm using these new keyword arguments. Are there any other cases which you have in mind which could be updated to use these?

Update names. Two additional thoughts:

• Would we consider adding the option to attach stdout to non-failing test?
• Should the <system-out/> element by moved inside <testcase/>? This seems to be scheme used by nose's XML reports, eg: http://nose2.readthedocs.io/en/latest/plugins/junitxml.html

Will supply PR to ros_comm for roslaunch-check shortly.

Would we consider adding the option to attach stdout to non-failing test?

Sounds good to me. Can be helpful to know what was happening.

Should the <system-out/> element by moved inside <testcase/>?

As long as it is compliant which how it is being parsed, how Jenkins interprets the result and we have the output on a per-test level that sounds good to me too.

I think this is good to go now. Example outputs and Jenkins screencaps in ros/ros_comm#897.

Based on you comment (ros/ros_comm#897 (comment)) and some testing (afaik Jenkins won't show any system-out if the test passed and the location of the system-out in the case of the failing test doesn't make a difference it is shown either way) can you please remove the stdout related changes from the PR for now (basically the last commit)?

I confirm that Jenkins doesn't show stdout on success. Lame.

I've withdrawn that commit.

Thanks for the patch and iterating on it.