How to Generate Android Testing Report in HTML Automatically

Question

I would like to automatically generate unit testing report in html format for Android application on Hudson continuous integration server.

Therefore, I try to run test cases first and gather test result files in xml format. Then, I use JUnitReport Task to transform the XML result files into HTML format.

I run test cases through Android instrumentation framework. However, it only provides verbose output information rather than the standard JUnit XML format. I have no idea how to generate HTML unit test report without JUnit XML result files.

If I run test cases using Eclipse, it can export results in XML files with time consumed information per test case. Those XML files can be transformed into HTML by JUnitReport Task correctly. As a result, it seems that it is possible to collect the test result with time consumed information.

Is there any way to get the standard JUnit XML result file automatically after running test cases on Android instrumentation framework?

Answer 1

We had similar problem in our company. We checked all the available open-source solutions and none of them was really perfect. So we developed and just open-sourced a solution for it. I still do not say an "ultimate" one but certainly much better than either athena or the python reporter or any after-test analysis. You can find it here: http://code.google.com/p/the-missing-android-xml-junit-test-runner/

It provides:

• separate XML file per each package involved
• XML files are generated on the device (need to be adb pull'ed after test)
• timing of the tests is fully supported
• we have full stack trace reported in failure/error case

Instead of analysing java source code (as in athena) or analysing the output (the python script), we extended android instrumentation runner. So we get all the benefits of using standard command line options for test selection, coverage enabling etc. - all described here: http://developer.android.com/guide/developing/testing/testing_otheride.html#RunTestsCommand.

We were able to successfully run the code using standard test rules with coverage analysed by emma, all nicely reported in Jenkins.