stephenmathieson/grunt-jslint — pull request #5 by sbrandwoo (2012-12-12 19:50:27+00:00)
Title: Improve the XML generated for JUnit files, so Jenkins can read it better

This is a bit rough, so I'm welcome to comments about the structure and how you think it fits into the rest of the code base. It's possible that the jslint.js changes should be separated out to a junit-only function.

Basically the changes are to improve how the JUnit XML report can be processed by Jenkins:
- Use a dot-separated string (called `classname`) that Jenkins understands, so that results can be broken down by package.
- Put only one failure reason in each test case, because Jenkins will only display one of them
- Because of the above, generate an almost-unique ID for each error that can be used in the test case name.

The result is a better report in Jenkins, but I don't know if I have sacrificed compatibility elsewhere.

What do you think?