The Beaker results model does not match JUnit's very closely at all, so when Beaker is generating JUnit XML formatted results we have to kind of cram it in. There are a few corner cases which currently do not work very well.

The JUnit XML format has package, class, and name (as in, Java package, Java class, and test method name) which is supposed to correspond to the JUnit test methods. Jenkins displays these as <package>.<class>.<name>.

In Beaker we have tasks with filesystem-path-style names (e.g. /distribution/beaker/dogfood) and task results. In the RHTS tradition the results are named after the task with a path suffix (e.g. /distribution/beaker/dogfood/yum_install) but there are many other possibilities. For example, Beakerlib uses plain hyphen-separated result names (no slashes) and Beaker itself has the special /start result for the installation.

Currently to produce the JUnit XML we put the task name into class="" and the result name into name="", re-using the web UI's result prefix stripping logic. That works well for some common cases:

Task /distribution/beaker/dogfood
Result /distribution/beaker/dogfood/yum_install
in Jenkins appears as /distribution/beaker/dogfood.yum_install

Task /distribution/beaker/setup
Result Build-Beaker-from-git
in Jenkins appears as /distribution/beaker/setup.Build-Beaker-from-git

However the common case of:
Task /distribution/beaker/dogfood
Result /distribution/beaker/dogfood
appears in Jenkins as /distribution/beaker/dogfood../
but should probably instead be /distribution/beaker/dogfood.(none)
We want name="(none)" to distinguish it from the overall task which has no name="" attribute.

Also the ubiquitous installation result:
Task /distribution/install
Result /start
appears in Jenkins as /distribution/install./start
We should strip leading slashes from the result names.

Internal slashes are okay, as in
/distribution/beaker/dogfood.rhts_task/exit
which is suboptimal but makes reasonable sense.