Thank you everyone for your replies.
I was able to resolve this error. As hinted above, the problem lied in
my project settings.
In my test project, instead of referencing project B directly, I was
able to export the class files from project A.
(Under the Order and Export tab in the Java Build
Exactly...
Let me give you my example (and you can extrapolate it to your
situation)
I had project B that depends on project A (a set of exception classes
exported as an external jar)
Android Test project C called classes in project B and raised expected
exceptions defined in project A
I get this error as well, I believe it depends on the order of imports
within your test project. If you have lib1 added to both the test and
tested project, you ll get something of that sort Still trying to
sort it out.
On Oct 14, 4:31 am, Brett Chabot brettcha...@android.com wrote:
I'm not
I'm not sure what that exact error message means, but my guess is the
problem has to do with your test to project mapping. An
instrumentation (which is what your test project uses to access
classes in your project under test), can only be targeted to one
android application. Try splitting up your
4 matches
Mail list logo
