Running a unit test in Android Studio yields an exception

2,616 views
Skip to first unread message

Rainer Burgstaller

unread,
Jun 14, 2013, 12:48:27 AM6/14/13
to adt...@googlegroups.com
I have unit tests now working in Gradle, but when I try and run an individual test class in Android Studio (by right Click, run->ClassNameTest) then I get the following exception

/Library/Java/JavaVirtualMachines/jdk1.7.0_10.jdk/Contents/Home/bin/java -ea -Didea.launcher.port=7532 "-Didea.launcher.bin.path=/Applications/Android Studio.app/bin" -Dfile.encoding=UTF-8 -classpath "/Applications/Android Studio.app/lib/idea_rt.jar:/Applications/Android Studio.app/plugins/junit/lib/junit-rt.jar:/Users/rainer/Development/android-sdk-macosx/platforms/android-16/android.jar:/Users/rainer/Development/android-sdk-macosx/add-ons/addon-google_apis-google-16/libs/effects.jar:/Users/rainer/Development/android-sdk-macosx/add-ons/addon-google_apis-google-16/libs/usb.jar:/Users/rainer/Development/android-sdk-macosx/add-ons/addon-google_apis-google-16/libs/maps.jar:/Users/rainer/Development/android-sdk-macosx/platforms/android-16/data/res:/Users/rainer/Development/android-sdk-macosx/tools/support/annotations.jar:/Users/rainer/Documents/workspaces/privat/PtpWorkspace/OfParent/app/build/classes/debug:/Users/rainer/.m2/repository/com/google/android-support-v4/0.1/android-support-v4-0.1.jar:://Users/rainer/Documents/workspaces/privat/PtpWorkspace/OfParent/app/build/exploded-bundles/diego.aar/classes.jar:/Users/rainer/Documents/workspaces/privat/PtpWorkspace/OfParent/libraries/diego/libs/persistence-api-1.0.jar:/Users/rainer/Documents/workspaces/privat/PtpWorkspace/OfParent/app/build/exploded-bundles/diego.aar/libs/persistence-api-1.0.jar:/Users/rainer/Development/android-sdk-macosx/extras/android/m2repository/com/android/support/support-v4/13.0.0/support-v4-13.0.0.jar" com.intellij.rt.execution.application.AppMain com.intellij.rt.execution.junit.JUnitStarter -ideVersion5 com.myclass.WebdavSyncherTest
Exception in thread "main" java.lang.NoClassDefFoundError: junit/textui/ResultPrinter
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:186)
at com.intellij.rt.execution.application.AppMain.main(AppMain.java:113)
Caused by: java.lang.ClassNotFoundException: junit.textui.ResultPrinter
at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:423)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
... 3 more

Process finished with exit code 1


Another thing that is weird is that I get 2 Unit test options, one with the android icon (which yields "no test suites found") and another one which results in the before mentioned exception.

cheers
- Rainer

Siva Velusamy

unread,
Jun 14, 2013, 1:30:05 AM6/14/13
to adt...@googlegroups.com
Yes, unit tests don't work properly from the IDE yet. We'll fix them shortly.
> --
> You received this message because you are subscribed to the Google Groups
> "adt-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to adt-dev+u...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

Arild Jacobsen

unread,
Sep 17, 2013, 5:05:37 AM9/17/13
to adt...@googlegroups.com
By my estimation, it's been more than a "short" time since June 14th and yet I still encounter the same error message when trying to run junit tests from Android Studio. I really am frustrated by how many hoops I have to jump through to be able to run junit tests on my android projects... and don't talk to me about instrumentation, you can't do proper tdd with turnaround that slow.

Siva Velusamy

unread,
Sep 17, 2013, 11:22:20 AM9/17/13
to adt...@googlegroups.com
Sorry, my response was for instrumentation tests, which are now
supported. Unit tests won't be there until gradle supports it, and
that will take a while (see other threads in the mailing list
regarding this).
Reply all
Reply to author
Forward
0 new messages