The README for android-junit-report mentions some caveats about the report file format, the main ones being that:

- All suites are dumped in a single file; and
- No redundant information is given.

Pulse is flexible enough in its handling of these types of reports to read this output, but I’m not surprised that some tools aren’t, as it differs from the junit task’s output.

However, today I have added a new feature to android-junit-report that allows you to generate multiple output files – oe per suite. Perhaps Quickbuild will have more luck with them:

https://github.com/jsankey/android-junit-report

Re: the license, this is with the source code in GitHub (Apache 2). Commercial distribution is fine.

I use the steps suggested above and I am able to get a basic XML file generated after running my test cases in Android. However when I try to use that with an industry accepted CI tool like Quickbuild, its not able to consume the XML file and throws errors.

Wonder if the XML file generated is pure JUnit-XML or something that works with Pulse but may/maynot work with other CI tools or standard XML-HTML converters to give me a nice GUI interface to look at tests run/pass/fail etc?

Another question I have is on the jar file that is mentioned, what licensing terms is it released under? Can I use it for commercial distribution as part of my application?

Regards

My post was not to suggest that there was no way to run an Android build on a CI server previously, so I think it’s a stretch to call that an “omission”. The piece that was missing, as far as I was aware, was some way to get nicely integrated test reporting. Although the tests would run and appear in the build log, many CI servers support richer integration and reporting of test results. To do this they need access to a parseable test report. Hence my new runner that produces such reports.

My new runner itself could equally be used with a Maven build, provided your plugin allows the user to customise the test runner somehow. In fact it could be nice to figure out how to put the two together for people that prefer Maven!