Hi, I'm getting this error below since I updated my Android Sdk Tool to version 22.0.1. My instrumentation runner in the run configurations was already set to JunitReportTestRunner and it was running without problems before the update.

06-07 16:30:12.889: E/AndroidRuntime(4966): java.lang.RuntimeException: Unable to instantiate instrumentation ComponentInfo{br.com.fisgo.fisgoimoveis.test/com.zutubi.android.junitreport.JUnitReportTestRunner}: java.lang.ClassNotFoundException: com.zutubi.android.junitreport.JUnitReportTestRunner in loader dalvik.system.PathClassLoader[/system/framework/android.test.runner.jar:/data/app/br.com.fisgo.fisgoimoveis.test-1.apk:/data/app/br.com.fisgo.fisgoimoveis-1.apk]

First of all, sorry for force-pushing so many updates to this pull request, I made some stupid mistakes at first.

This is more or less some proof of concept for you to review. Even with my changes we still have the problem that JUnitReportTestRunner.finish() and JUnitReportListener.close() are not called if the instrumented process crashes, leaving the XML document open with a missing </testsuites> tag.

I did some research on how to detect whether the process crashes. Unfortunately, none of the event methods in JUnitReportTestRunner seem to get called in that case. The only option seems to be to watch the Android log for an ActivityManager output like "Crash of app <package> running instrumentation". That solution would not exactly be elegant, but I would be willing to try it out unless you come up with a better idea how to detect a crashed test application. What do you think?

It looks like when there is an exception the new report is not produced and the old one is lying around, is that possible to delete existing report when the test starts ? also is that possible to catch exceptions and still produce report ?

when so many errors occured in the junitTests it will generate a result named junit-report.xml with error as follows: Caused by: org.dom4j.DocumentException: Error on line 493 of document file:///////junit-report.xml : XML document structures must start and end within the same entity. Nested exception: XML document structures must start and end within the same entity. at org.dom4j.io.SAXReader.read(SAXReader.java:482) at org.dom4j.io.SAXReader.read(SAXReader.java:264) at hudson.tasks.junit.SuiteResult.parse(SuiteResult.java:88) at hudson.tasks.junit.TestResult.parse(TestResult.java:187) the file content is:

I just downloaded the 1.4.7 JAR and ran a test on an Android 1.6 emulator, with all the default settings.

The test runner could not start as it now uses Context.getExternalFilesDir(), which is only available from SDK level 8 (Android 2.2).

Logcat showed the following:

I/JUnitReportTestRunner(  252): Created with arguments: [coverage]
I/JUnitReportTestRunner(  252): Defaulted report file to 'junit-report.xml'
E/dalvikvm(  252): Could not find method android.content.Context.getExternalFilesDir, referenced from method com.zutubi.android.junitreport.JUnitReportListener.openOutputStream
W/dalvikvm(  252): VFY: unable to resolve virtual method 4: Landroid/content/Context;.getExternalFilesDir (Ljava/lang/String;)Ljava/io/File;
W/dalvikvm(  252): VFY:  rejecting opcode 0x6e at 0x0037
W/dalvikvm(  252): VFY:  rejected Lcom/zutubi/android/junitreport/JUnitReportListener;.openOutputStream (Ljava/lang/String;)Ljava/io/FileOutputStream;
W/dalvikvm(  252): Verifier rejected class Lcom/zutubi/android/junitreport/JUnitReportListener;
D/AndroidRuntime(  252): Shutting down VM

Hello,

I get failed install missing shared library errors using Android sdk tools 10. At first I though it was my setup with using android-mock and robotium but took out the test runner and everything was fine than tried your test runner again and got the same errors. Yes library was showing in apk form what I can see as far as classes.dex file space amounts.

Hi,

I made a quick mod to android-junit-report to record test times in the XML. Up to you if you want to merge it :)

Thanks for writing it, it's very useful!

Tim

Now test report file is saved under data directory of target package. Is it possible to save it under test package? I simply changed mTargetContext.openFileOutput(fileName, Context.MODE_WORLD_READABLE); to mTestContext.openFileOutput(fileName, Context.MODE_WORLD_READABLE); but no files generated.

Like I've already mentioned in my previous pull request, I believe it makes more sense to really just copy & paste the text form the source code to the README so that you only have to maintain it at one place and just copy it over when it changes in the future.

I'm aware this pull request will conflict with your recent changes to README, but you could just take my file as-is.

Currently, if running tests on an emulator/device with a locale which uses decimal commas instead of decimal points, the test duration attribute is output with a comma. This can upset JUnit XML parsers, certainly that of Jenkins.

Now the locale is fixed to English when writing out this XML attribute. Tested before/after on an emulator with German locale.

My android test application(Robotium application) works fine without report generation. I followed the procedure you have specified for report generation. 1.First added the jar to project/libs directory. 2.Modified the AndroidManifest file , which has the following content

I am not able to figure out the error. It would be very grateful if you can help me with this issue asap. :) .

Thanking you in advance