Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Android Robotium NoClassDefFoundError

I was just trying to use Robotium in an Android JUnit Test, but the Testing always fails with an error:

java.lang.NoClassDefFoundError: com.jayway.android.robotium.solo.Solo

thrown at solo = new Solo(getInstrumentation(), getActivity()); in the setUp() method:

protected void setUp() throws Exception {
    super.setUp();
    solo = new Solo(getInstrumentation(), getActivity());
}

I read somewhere that this could be related to the Android SDK revision 17, but I cannot confirm this, as I first tried Robotium already with SDK 17.

The Robotium jar is properly added to the project build path.

Has anyone encountered similar problems?

Regards K.

like image 943
Micky Avatar asked Mar 26 '12 15:03

Micky


5 Answers

I had the same problem today. I solved by importing the jar into the libs directory of the test project and then adding it to the Build Path Libraries:

TestProject Properties -> Java Build Path -> Libreries -> Add JARs... -> TestProject/libs/robotium-solo-3.1.jar

like image 124
Roberto Leinardi Avatar answered Nov 13 '22 08:11

Roberto Leinardi


You will need to export the Robotium jar by going to Properties-> Java Build Path -> Order and Export. Then check the Robotium jar file.

like image 36
Renas Avatar answered Nov 13 '22 07:11

Renas


I did this configuration to solve the problem

enter image description here

Note : I put robotium first one.

like image 8
Mohammed Subhi Sheikh Quroush Avatar answered Nov 13 '22 08:11

Mohammed Subhi Sheikh Quroush


Had the same issue on SDK 17. Adding the robotium jar to lib and exporting helped. Also had to change the deprecated super call in the constructor from super(String,Class) to super(Class) to make it work.

like image 3
trial999 Avatar answered Nov 13 '22 07:11

trial999


What I did to fix the bug was :

  • Remove the libraries from the standard Java build path :
  • Right click on the project name > Properties > Java Build Path > tab Libraries > remove everything except the “Android X.X” (2.3.3 in my case) and the “Android Dependencies”
  • Rename the libraries folder from “lib” to “libs”
  • By doing that, all the libraries in the folder “libs” are found by the Android plugin and are added to the “Android Dependencies” item of the project
  • Clean the project (not exactly needed)

You are good to go !

like image 2
Shalin Avatar answered Nov 13 '22 08:11

Shalin