Geek Answers Handbook

Android device testing - resolution and verification issues

I just switched my Android project and my unit test does not work ... I get errors like

WARN/dalvikvm(575): VFY: unable to resolve static field X in .....
WARN/dalvikvm(575): VFY: unable to find class referenced in signature

These errors come only from my unit tests, where the classes defined in it cannot even see other classes defined in the unit test.

Before each project had its own directory with copies of third-party jar files. I read that Dex does weird things with links, but was unable to figure out how to fix this problem. Is there a better way to do this? I would like to see an example of a large Android workspace where there are several projects, links to jar, etc.

Can this be fixed using the Order / Export setting?

The project is structured as follows:

  • Eclipse workspace (class variable PROJECT_HOME)
  • Lib
    • Third Party Banks
    • android.jar
  • Java A Project
    • Included in PROJECT_HOME
  • Java Project B
    • Included in PROJECT_HOME
    • Depends on project A
  • Android project
    • Depends on A and B
    • Included in PROJECT_HOME
  • Android Testing Project
    • Depends on projects A, B, Android
    • Included in PROJECT_HOME
+5
source share
1 answer

Do not include a third-party jar in a test project. Just export it to the project being tested: project properties -> java build path -> order and export. Once this is done, you will be able to clean and work fine.

+1
source

More articles:


All Articles