Class Not Found Exception when running JUnit test

Question

I am getting this error when running JUnit test in Eclipse:

Class not found com.myproject.server.MyTest
java.lang.ClassNotFoundException: com.myproject.server.MyTest
    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)
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.loadClass(RemoteTestRunner.java:693)
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.loadClasses(RemoteTestRunner.java:429)
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:452)
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
    at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)

I've tried adding JUnit library in the classpath although I'm using maven, and the JUnit library is in the POM dependency.

I already have tried cleaning the project and created a new JUnit test case using the JUnit plugin for Eclipse, still getting the same error.

try running `mvn clean test` once it will compile all the test classes — jmj, Jul 08 '12 at 06:47
Can you please check if com.myproject.server.MyTest is there in bin folder? I mean if it is not compiled due to compile or build path error you will get this error. — vikas, Jul 08 '12 at 12:22
Possible duplicate of [Eclipse - java.lang.ClassNotFoundException](http://stackoverflow.com/questions/1052978/eclipse-java-lang-classnotfoundexception) — Amos M. Carpenter, Dec 11 '15 at 01:22
In my case running tests using Maven worked, but if I right-click on a test class and choose Run As -> JUnit Test, it reported ClassNotFoundException. I fixed it by right-clicking on the project and going to Properties -> Builders and then moving Maven Project Builder above the Java Builder — xorcus, Mar 29 '16 at 21:45
Judging from other answers (solved by clean/rebuild, restarting Eclipse, making some dummy change, delete the .metadata folder, change order of classpath items, restoring defaults) and my own experience, this is some kind of race condition bug in Eclipse, even in 2023. In my case it could not find a resource file: `java.io.FileNotFoundException: class path resource [foo/appStuff.xml] cannot be opened because it does not exist` Then after fiddling around it suddenly started to work. With same settings as before. — David Balažic, Apr 25 '23 at 12:41

score 149 · Accepted Answer · edited Jan 20 '17 at 09:20

149

This appears to occur because only the source code is compiling when you use mvn clean compile (I'm using maven 3.1.0 so I'm not sure if it always behaved like this).

If you run mvn test, the test code will compile as well, but then it runs the tests (which may not be immediately desirable if you're trying to run them through Eclipse.) The way around this is to add test-compile to your Maven command sequence whenever you do a mvn clean. For example, you would run mvn clean compile test-compile.

edited Jan 20 '17 at 09:20

kryger

12,906
8
44
65

answered Jul 21 '13 at 02:58

Newtrino

1,613
1
11
4

1

I had this happen once and slomek's answer worked and then this same error happened again so I had to try this as well. It works fine again now, so to be safe you may want to do both of these things. – Roger Sep 22 '14 at 14:20
Thanks, its worked for me. But in my case, its not worked till close and reopened the project in eclipse. – Paramesh Korrakuti Jul 22 '15 at 10:25
In simple words do a 'mvn clean test-compile' and then run your Junit tests in eclipse. It worked for me. Thanks. – Sreram Balasubramaniyan Aug 22 '18 at 06:05
what if that is a n ant project – Abdul May 11 '21 at 10:15

score 119 · Answer 2 · answered Nov 14 '12 at 09:05

119

I had a similar problem with my tests and found somewhere in the Web, that you have to go to Build Path in your project's properties and move Maven Dependencies above JRE System Library. That seems to have worked for me.

answered Nov 14 '12 at 09:05

slomek

4,873
3
17
16

1

Thanks this solved my problem. The actual test was getting the class not found error when I tried to run it. I think this is probably a preferable first step before adding extra mvn build targets. – Roger Sep 19 '14 at 16:20
9

This method is described with screenshots in [this](http://ihategeek.wordpress.com/2012/04/18/eclipse-junit-test-class-not-found/) post (in case the steps aren't clear from @slomek's answer above) – nhylated Nov 19 '14 at 08:25
2

I could not move Maven Managed Dependencies above JRE System Library in Eclipse Mars 2, but I could right-click on the project and go to Properties -> Builders and then move Maven Project Builder above the Java Builder and it worked for me. – xorcus Mar 29 '16 at 21:43
I tried all of the above and it didn't work, I also could not move the Maven Dependencies about JRE System Library but that was under the Libraries tab. Then I went to Build Path -> Order & Export -> as was able to move Maven Dependencies above JRE System library. Then I built the project and ran a Maven install, then the test ran successfully. – Megan Aug 02 '16 at 14:31
In my case, changing the order of Maven Dependencies from Build Path configuration did not worked for me. I changed its order from Run configuration. it worked. For those steps read my answer. – Shadyar Sep 22 '20 at 04:10

score 33 · Answer 3 · edited May 23 '17 at 12:26

33

I faced the same problem and I was able to fix it using @slomek's answer but the issue resurfaced after that.

I finally fixed it by adding my project's output folder to the JUnit test's run configuration. Steps are:

Find your project's output folder from Project properties -> Java Build Path -> Default output folder
- Usually this is <project-folder>/bin
Go to Run -> Run Configurations...
Click on the unit test's run configuration and click on the Classpath tab
Explicitly add your project's output folder under User Entries - even if the project is already included there
- Click on Advanced -> Add folder to add the output folder

This issue might be due to weird project setup in Eclipse - e.g. source folder with nested maven projects imported as a single project/folder (at least that was how my project was setup).

edited May 23 '17 at 12:26

Community

1
1

answered Nov 21 '14 at 13:34

nhylated

1,575
13
19

1

Thank you so much; I had this problem. Your fix worked for me; the top two didn't. Up-voted. – rbncrthms Apr 07 '15 at 15:27
1

Absolutely brilliant! Been scratching my head for ages over this. Thanks! – RayCh Jul 15 '20 at 08:46
Thank you so much. I could never fix this myself. Mine is an Ant Project though, your solution works. – Mohit Sep 11 '20 at 08:29

score 18 · Answer 4 · answered Mar 04 '16 at 06:57

18

If this problem occurs in Eclipse only, executing command Project -> Clean... on selected project may help.

answered Mar 04 '16 at 06:57

johanwannheden

852
8
8

Thanks - it actually worked for me - JAVE EE eclipse gradlew – Abdeali Chandanwala Dec 10 '18 at 13:24
Ensure we select particular project while cleaning, not all. – Ram Oct 01 '20 at 03:22

score 14 · Answer 5 · answered Sep 28 '15 at 07:40

14

After having tried everything here with no improvement, I solved my issue by just restarting Eclipse

answered Sep 28 '15 at 07:40

Berit Larsen

739
1
12
29

score 11 · Answer 6 · answered Sep 30 '19 at 19:47

11

I fixed my issue by running maven update. Right click project your project > Maven > Update Project

answered Sep 30 '19 at 19:47

Azianese

554
7
21

This is what I do all the time and it resolves the issue.. – rslj May 13 '21 at 15:13

score 5 · Answer 7 · answered Oct 06 '15 at 15:47

5

In my case I had a wrong maven directory structure.

Which should be like:

/src/test/java/ com.myproject.server.MyTest

After I fixed that - everything worked like a charm.

answered Oct 06 '15 at 15:47

ITisha

902
2
12
14

score 3 · Answer 8 · answered Jun 01 '16 at 13:37

3

In my case, only next steps helped me to resolve this issue:

Project->properties->Run/Debug Settings.
In "Launch configurations for '.....'" select classes/projects
Edit -> Classpath -> "Restore Default Entries"

answered Jun 01 '16 at 13:37

Roman Romaniuk

81
1
3

Thanks!! Only this one helped me!! – sumandas Nov 08 '17 at 13:25

score 2 · Answer 9 · answered Aug 12 '19 at 22:10

2

It seems compile issue. Run project as Maven test, then Run as JUnit Test.

answered Aug 12 '19 at 22:10

Yao Li

2,071
1
25
24

score 1 · Answer 10 · edited Sep 26 '17 at 06:55

Earlier, in this case, I always did mvn eclipse:eclipse and restarted my Eclipse and it worked. After migrating to GIT, it stopped working for me which is somewhat weird.

Basic problem here is Mr Eclipse does not find the compiled class. Then, I set the output folder as Project/target/test-classes which is by default generated by mvn clean install without skipping the test and proceeded with following workaround:

Option 1: Set classpath for each test case

Eclipse ->Run ->Run Configurations ->under JUnit->select mytest -> under classpath tab->Select User Entries->Advanced->Add Folder -> Select ->Apply->Run

Option 2: Create classpath variable and include it in classpath for all the test cases

Eclipse ->Windows ->Classpath Variables ->New->[Name : Junit_test_cases_cp | path : ]->ok Then go to Eclipse->Run ->Run Configurations ->JUnit->select mytest ->under classpath tab ->Select User Entries->Advanced->Add classpath variables->Select Junit_test_cases_cp->ok->Apply->Run

This is the only thing currently working for me after trying all the suggestions online.

score 1 · Answer 11 · answered Jul 31 '14 at 07:11

I had the similar problem with my Eclipse Helios which debugging Junits. My problem was little different as i was able to run Junits successfully but when i was getting ClassNotFoundException while debugging the same JUNITs.

I have tried all sort of different solutions available in Stackoverflow.com and forums elsewhere, but nothing seem to work. After banging my head with these issue for close to two days, finally i figured out the solution to it.

If none of the solutions seem to work, just delete the .metadata folder created in your workspace. This would create an additional overhead of importing the projects and all sorts of configuration you have done, but these will surely solve these issue.

Hope these helps.

As a note...doing this will require you to rebuilt your environment. So while it can solution just be aware of what you are about to do... — Bob, Mar 13 '19 at 22:06

score 1 · Answer 12 · edited Jun 12 '19 at 13:42

NoClassDefFoundError really means it can't initilize the class. It has nothing to do with finding the class. I got this error when calling trim() on a null String.

JUnit won't show NullPointerException. The string isn't null when running normally because I'm fetching the string from a properties file which is not availible for tests.

My advice is to remove pieces from the class until your tests start passing. Then you can determine which line is giving the error.

Shadyar · Answer 13 · 2020-09-28T12:36:28.913

In my case, changing the order of Maven Dependencies from Build Path configuration did not work for me. I changed its order from Run configuration.
Follow these steps:
• Go to Run -> Run Configurations...
• Click on the unit test's run configuration and click on the Classpath tab.
• check Use temporary JAR to specify classpath (to avoid classpath length limitations).
May be it is enough and your test works. You should try, so press Run button. If it did not work. Follow all previous steps again and without pressing Run button, go to the next step.
• In sub branches of User Entries move Maven Dependencies above your project or test class.
• Click Run button.

score 1 · Answer 14 · answered Nov 26 '20 at 13:57

1

For me I had to put the project x/src/test/java/ at the bottom of the "order and export" in the "java build path"

answered Nov 26 '20 at 13:57

fayabobo

81
1
1
7

score 0 · Answer 15 · answered Mar 03 '15 at 10:10

0

These steps worked for me.

Delete the content of local Maven repository.
run mvn clean install in the command line. (cd to the pom directory).
Build Project in Eclipse.

answered Mar 03 '15 at 10:10

Jake Graham Arnold

1,416
2
19
40

score 0 · Answer 16 · answered Apr 09 '15 at 11:56

0

1- mvn eclipse:eclipse

2- project clean all projects

3- restart

answered Apr 09 '15 at 11:56

Toumi

2,925
4
37
31

score 0 · Answer 17 · answered May 04 '17 at 14:32

It's worth mentioning as another answer that if you're using eGit, and your classpath gets updated because of say, a test coverage tool like Clover, that sometimes there's a cleanup hiccup that does not completely delete the contents of /path/to/git/repository/<project name>/bin/

Essentially, I used Eclipse's Error Log View, identified what was causing issues during this cleanup effort, navigated to the source directory, and manually deleted the <project name>/bin directory. Once that finished I went back to Eclipse and refreshed (F5) my project and the error went away.

score 0 · Answer 18 · answered Sep 18 '17 at 21:15

0

It can also be due to "[ERROR] No compiler is provided in this environment. Perhaps you are running on a JRE rather than a JDK?"

answered Sep 18 '17 at 21:15

William

491
5
9

score 0 · Answer 19 · answered May 18 '18 at 09:50

I had the same problem with a Gradle project with a test SourceSet with two resource directories.

This snippet comes from a main-module.gradle and adds a resource dir to the test SourceSet:

sourceSets {
    test {
        resources {
            srcDir('../other-module/src/test/resources')
        }
    }
}

Doing this I had two resource directories related to the test SourceSet of the project main-module:

../other-module/src/test/resources src/test/resources (relative to the main-module folder, automatically added by the java plugin)

I find out that if I had two files with the same name in both the source directories, something in the process resources stage went wrong. As result, no compilation started and for this reason no .class were copied in the bin directory, where JUnit was looking for the classes. The ClassNotFoundException disappeared just renaming one of the two files.

score 0 · Answer 20 · answered Oct 11 '19 at 18:57

0

For project that does not use maven : This worked for me https://ihategeek.wordpress.com/2012/04/18/eclipse-junit-test-class-not-found/

Adding the jre and project src at the bottom in Order and exports in build path

answered Oct 11 '19 at 18:57

Groot

211
1
5
11

score 0 · Answer 21 · answered Dec 23 '19 at 11:59

0

Pls check if you have added junit4 as dependency.

e.g

<dependency>
    <groupId>junit</groupId>
    <artifactId>junit</artifactId>
    <version>4.11</version>
    <scope>test</scope>
</dependency>

answered Dec 23 '19 at 11:59

Ishan Liyanage

2,237
1
26
25

score -1 · Answer 22 · answered Jul 07 '17 at 10:07

-1

Check if your project is opened as a Maven project and not just a regular Java project. Actually a no-brainer, but that is exactly the same reason why you might miss it.

answered Jul 07 '17 at 10:07

Ben

2,314
1
19
36

score -1 · Answer 23 · edited Jun 12 '19 at 13:35

-1

I had faced the same issue. I solved it by removing the external JUnit jar dependency which I added by download from the internet externally. But then I went to project->properties->build path->add library->junit->choosed the version(ex junit4)->apply.

It automatically added the dependency. it solved my issue.

edited Jun 12 '19 at 13:35

jmajcan

77
1
1
11

answered Apr 16 '19 at 10:48

Agniva Dutta

33
5

score -1 · Answer 24 · answered Jun 27 '19 at 06:51

-1

Making some dummy change and saving the test class can solve the problem. It will build the .class automatically

answered Jun 27 '19 at 06:51

Lorenzo Lerate

3,552
3
26
25

score -6 · Answer 25 · answered Aug 22 '14 at 09:42

-6

Might be you forgotten to place the Main class and Test Case class in /src/test/java. Check it Once.

answered Aug 22 '14 at 09:42

Sathya

1

1

java.lang.ClassNotFoundException comes when class is already compiled but on run time due to classpath not set properly. – Nitin Mahesh Aug 04 '15 at 13:02

Class Not Found Exception when running JUnit test

25 Answers25

Linked