IntelliJ can't find classpath test resource

Question

I'm having a problem where IntelliJ 13.1.4, when running a unit test, can't find a ServiceLoader file in the src/test/resources directory of my module.

Please note before answering that I've done all of the following:

1. The module is a Gradle project, and if I run gradle test the unit test runs fine.
2. I've run this unit test successfully in IntelliJ in the past, and it found the module. (Maybe an earlier version of IntelliJ?)
3. I've double checked the IntelliJ module settings and the src/test/resources directory is marked as being a test resources directory. (See screenshot below.)
4. I'm dumping the unit test class's classloader's classpath in the class; it has the build/classes/test/ and build/classes/java directories, but neither build/resources/test/ nor build/resources/main/.
5. I've clicked the button to refresh all Gradle projects.

Any ideas on what else could be causing IntelliJ to fail here?

---

Screenshot of my module configuration, showing the Test Resource Folders setting.

Answer 1

In my case, I simply ran the tests through maven command line, i.e. a basic mvn clean install. After that it worked in IDEA.

Answer 2

I face a similar issue with IntelliJ 14. Despite having the necessary files in my resources folder and ensuring that the folder is specified as a resource in the module settings, IntelliJ intermittently fails to load my files onto the classpath.

One workaround is to add the required folder as a dependency for the module in the module settings.

First, click on the "+" button to add a new dependency.

Then, select the folder you wish to add to the classpath.

Then select the "classes" option.

Once that is done, re-build your module once and hopefully that should do the trick.

Ideally this should not at all be an issue. All files in the resource folder should directly be put in the classpath. However, every IDE has it's quirks.

Answer 3

I managed to get it working better by creating a test-resources directory parallel to the test directory (!).

Still seeing intermittent problems with this, though. Those times, it's possible to open the IntelliJ project settings and define the test resources as source instead (the Gradle project will remain unchanged).

Must be an IntelliJ bug, as I've experienced the same thing in Android Studio.

EDIT:

I found a workaround to the issue.

Add the following at the end of the Gradle config (and specify your test resources path):

task copyTestResources(type: Copy) {
    from "${projectDir}/src/test/resources"
    into "${buildDir}/classes/test"
}
processTestResources.dependsOn copyTestResources

Answer 4

I ran into the same issue, where Junit was failing(FileNotFound) because I had space in my root project folder. eg: my project/project1/....

• I removed the space from the root folder, my_project/project1/ all test passed properly.

Answer 5

When I was running into the same issue, it worked for me to once unmark the resources directory as resources root and then mark it again as resources root:

1. Right click on resources folder > Mark directory as ... > Unmark as Resources Root
2. Right click on resources folder > Mark directory as ... > Test Resources Root