java.lang.NoClassDefFoundError while running JUnit test in Netbeans

Question

I am building an Android hello world application in Netbeans. It's building properly and I am able to run in the emulator also.

But when creating and running the Junit test I get a java.lang.NoClassDefFoundError.

How can I fix this problem?

Edit your question to include the entire error message and stacktrace. — BalusC, May 26 '10 at 12:37

score 16 · Answer 1 · answered Aug 26 '11 at 21:46

16

Check the manifest of your test project, for example HelloWorldTest/AndroidManifest.xml. The android:targetPackage attribute of the instrumentation markup should target the package in your application, for example, com.example.helloworld. Not the test package of your test project (eg. com.example.helloworld.test).

answered Aug 26 '11 at 21:46

philippe_b

38,730
7
57
59

*facepalm* you just saved me 1 hour of searching. It's a common mistake and yet I tend to overlook it from time to time :) – marsbear Aug 17 '12 at 12:39
3

Eh eh _I_ lost an hour myself with that mistake. :) – philippe_b Aug 17 '12 at 15:31

score 3 · Answer 2 · answered May 14 '13 at 15:20

3

Simply AndroidManifest.xml -> manifest -> package of main application should match AndroidManifest.xml -> manifest -> instrumentation -> android:targetPackage of the test application.

answered May 14 '13 at 15:20

Eng.Fouad

115,165
71
313
417

1

But if he runs simply no instrumentation test but plain old jUnit? – JacksOnF1re Apr 02 '15 at 16:28

score 0 · Answer 3 · answered May 26 '10 at 12:57

The full error message contains the name of the class, that wasn't found on the classpath. Double check if the classpath that is used for running the test includes all required classes and libraries (your class files, junit.jar, android specific libaries).

score 0 · Answer 4 · answered May 26 '10 at 13:29

0

I find that a rebuild usually finds the classes (as it is a classpath issue). Netbeans seems to aggressively compile existing tests, but the main source code (from a maven setting at least) is not always available.

I've started running full builds to try address this. There might be a plugin that addresses this but I haven't found it yet.

EDIT: This might help.

answered May 26 '10 at 13:29

gpampara

11,989
3
27
26

I think he has more a android-netbeans-integration problem. you mentioned a problem which occurs if compile on save is enabled for the project sources too. – Karussell Mar 28 '11 at 20:27

score 0 · Answer 5 · edited May 23 '17 at 12:23

0

I don't know about netbeans specifics, but the problem is probably the same.

FragmentActivity can not be tested via ActivityInstrumentationTestCase2

Your test project can be using a different android compatibility library than your main project, and that causes this weird errors.

edited May 23 '17 at 12:23

Community

1
1

answered Oct 24 '11 at 14:23

Draiken

3,805
2
30
48

java.lang.NoClassDefFoundError while running JUnit test in Netbeans

5 Answers5

Linked