I downloaded Robolectric deckard-gradle project from https://github.com/robolectric/deckard-gradle and imported to Android Studio.
On my first run i got
!!! JUnit version 3.8 or later expected:
java.lang.RuntimeException: Stub!
at junit.runner.BaseTestRunner.<init>(BaseTestRunner.java:5)
at junit.textui.TestRunner.<init>(TestRunner.java:54)
at junit.textui.TestRunner.<init>(TestRunner.java:48)
at junit.textui.TestRunner.<init>(TestRunner.java:41)
Error and i fixed this from .iml.
Then i got:
Class Not Found "my test class"
I tried dozens of solutions which i found in google about this problem but none of them worked.
UPDATE: Android Studio 1.1.0 has added JUNIT 4 testing support to the IDE. See more under: https://sites.google.com/a/android.com/tools/tech-docs/unit-testing-support. That should fix the STUB exception.
Option one of Alex is the right answer: I use it in two projects now and it is sad you have to do it this way but that's all you can do right now.
The detailed steps are:
By the way, for generating the output test-sources I had to add
apply plugin: 'idea'
idea {
module {
testOutputDir = file('build/test-classes/debug')
}
}
to the module's build.gradle
If you still get errors when trying to use the ui, go to the terminal included in android studio and use ./gradle clean check (or an equivalent command) which runs lint checks for your project and the tests. If anything goes wrong with your tests you'll be informed there and have the possibility to view the results on a html-page.
I was struggling with the same problem and finally got it to work with this solution (for Android Studio 1.0.2 and Robolectric 2.4):
Go to your module's *.iml and move the order-entry
with jdkType='Android SDK'
to the bottom of all other order-entry
-elements (this fixes the "Stub"-issue).
Also in the *.iml file add the following output-test
entry directly beneath the output
-element. It should look like this:
<output url="file://$MODULE_DIR$/build/intermediates/classes/debug" /> <output-test url="file://$MODULE_DIR$/build/test-classes" />
This works perfect for me. Now I am able to run tests directly from Android Studio and don't have to manipulate the class path. This is why I feel this is more convenient.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With