!!! JUnit version 3.8 or later expected

Question

My Android studio project has an app module which is android framework dependent, I have created a new module called domain and it contains only pure java classes and a few test classes.

In this module's build.gradle file, I have added junit and mockito libraries for testing purpose as follows:

apply plugin: 'java'
sourceCompatibility = 1.7
targetCompatibility = 1.7
dependencies {
    testCompile 'junit:junit:4.11'
    testCompile 'org.mockito:mockito-core:1.9.5'
    compile project(':common')
    compile project(':model')
    //test dependencies
}

But Android Studio is giving me !!! JUnit version 3.8 or later expected error message whenever I try to execute the test class.

All the suggested solutions to this problem is to open the Project Structure | Modules | Dependencies, and move the junit-4.7.jar up, so that it comes before Android 1.6 Platform in the classpath.

In fact, I have tried to implement this solution but the problem still exists. Image of my dependencies structure

Any idea on how to resolve this issue?

What does your Run/Debug Configuration look like for your tests? Specifically, what does the property "Use classpath of module" say for your tests? You can find this on _Run_ -> _Edit Configurations_, then select a configuration on the left. — Patrick McLaren, Mar 20 '15 at 17:47
I could solve it by removing `unitTest.returnDefaultValues`, check: https://stackoverflow.com/a/44820309/965569 — Chiara, Jun 29 '17 at 08:48

score 50 · Answer 1 · answered Aug 28 '15 at 09:30

50

I've already solved this just now. It may help you... maybe. A little instruction:

Go to Run -> Edit Configurations
Delete JUnit configuration on left panel

answered Aug 28 '15 at 09:30

voronnenok

712
6
6

It works for me. Probably it clean undesirable cache. – Paulo Nov 08 '15 at 13:45
But after you delete the Unnamed JUnit config, what do you run for (J)Unit Test? – Robert R Evans Dec 28 '15 at 22:16
1

That worked for me, seems to be common when you use android and both unit tests. – alxsimo Feb 13 '16 at 16:44
Didnt work for me and now I don't know how to restore my Unit test configuration – Kaloyan Roussev Mar 17 '16 at 17:54
@J.K. that's what i was worried about. Did you ever figure out how to have both instrumentation tests and unit tests? – Steve's a D Apr 02 '16 at 13:28
@SteveG this is how I restored my configuration: http://stackoverflow.com/questions/36068170/how-to-restore-a-deleted-runconfiguration-in-android-studio – Kaloyan Roussev Apr 03 '16 at 21:55
Thank you, it works for me building kotlin in IDEA – Wednesday May 19 '17 at 12:15
Worked for me as well! – alextc Jun 21 '17 at 04:45
Worked for me thanks. – Aaron Dancygier Oct 11 '17 at 21:52

score 8 · Answer 2 · answered Jul 07 '15 at 14:26

8

I've managed to solve it with simply editing the project's iml and moving order enrty for junit , in my case:

<orderEntry type="library" exported="" scope="TEST" name="junit-4.13-SNAPSHOT" level="project" />

up to be the first orderEntry after </content>

answered Jul 07 '15 at 14:26

Rotem Slootzky

688
10
21

Din't fix the problem for me. – ckp Jun 07 '17 at 15:09
@Rotem Slootzky Thanks for the fix! Any bug tickets you can point us to? Cheers! – beerBear Apr 23 '18 at 03:48

score 0 · Answer 3 · answered Dec 18 '15 at 19:35

I had this but the reason was different..I had inadvertently set my build variant to Release and didn't have any signing info specified so nothing could be built and run on the device.

The cryptic error it gave me was this same one when I tried running the integration tests...didn't notice the app was also disabled :-P Set it back to Debug and it worked fine.

score -7 · Accepted Answer · answered Mar 25 '15 at 16:36

-7

I managed to solve the problem by by changing the following in .iml file

from:

 <component name="NewModuleRootManager" inherit-compiler-output="true">

to:

  <orderEntry type="inheritedJdk" />

answered Mar 25 '15 at 16:36

Fshamri

1,346
4
17
32

This doesn't make sense. These are different tags. goes inside . – elliptic1 Apr 20 '15 at 13:34
This is not a good practice as the end-user of your project can import your project and Intellij will recreate the *.iml file. – Kevin Crain Nov 08 '16 at 17:39
Found on my side that the problem is cached references for older dependencies and in this case this solution is leading other fellow developers to anti-patterns, this is especially bad if the developer starts his journey following posts like this. Do not modify the *.iml, its somewhere in the official Intellij documentation – Kevin Crain Nov 09 '16 at 10:38

!!! JUnit version 3.8 or later expected

4 Answers4

Linked