Just in case anyone else wanders across this post, I found some info on project setup her: http://stackoverflow.com/questions/468220/how-do-you-run-android-instrumentation-tests-from-eclipse
On Aug 5, 11:33 pm, Alex G <quixop...@googlemail.com> wrote: > okay that makes sense, thankyou. I've been googling for a while and I > can't really find any good resources on how to setup as a single > project, everyone is using the standard two projects, can anyone point > me to something? > > I'm still finding it hard to believe that theres no way to share the > code across the two projects, I've tried making the third party jar a > required export in the project I am testing but I still get the same > error. > > Cheers > > On Aug 5, 6:57 pm, fadden <fad...@android.com> wrote: > > > On Aug 5, 10:11 am, Alex G <quixop...@googlemail.com> wrote: > > > > Thanks, I'll give that a try. Is it only the case that you need a > > > single project if you have a third party library? The reason I ask is > > > that all of the blogs and discussions I have found about unit testing > > > have advocated using two projects. > > > Having two copies of the same class will sometimes cause you grief. > > "dexopt" does various optimizations with the copy it finds, so if you > > manage to use a different copy at run time the VM will throw an > > exception (the optimizations can't be re-done on the fly to factor in > > differences between the two versions of the class). > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---