To clarify. Eclipse has the same problem. I on accident tested the single
test only where it worked.
On Thursday, August 23, 2012 5:56:18 PM UTC+9, blizzard wrote:
>
> Hello everyone,
>
> I'm having trouble executing instrumentation tests using the android maven
> plugin. I have followed the "li
I think I found the problem. It has to do with RUNNING ALL TESTS. Run each
test case one by one and the problem does not occur. No idea why. Maybe a
bug in running all tests?
For example. I have my SampleActivityTest extends
SingleLaunchActivityTestCase<...>.
This will have the problem:
adb she
Experiencing same problem. If I run the tests through eclipse they run fine
on 2.3.
But installing the apks by hand through adb and then running:
adb shell am instrument -w
${TEST_PACKAGE_NAME}/android.test.InstrumentationTestRunner
Gives me the given error. So questions is. What is different be
The purpose of Maven ?
Configuration controle ... release management ... reporting the list
goes on and on.
However, the problem I experience above occurs on both maven and ant builds.
On Tuesday, August 28, 2012 11:31:27 AM UTC+2, Jason Sesso wrote:
>
> I'm trying to understand mavens purp
I'm trying to understand mavens purpose
--
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...@go
I've had a major breakthrough on this.
I'm posting my progress here
http://stackoverflow.com/questions/12087948/test-apk-does-not-resolve-load-classes-from-main-apk-cannot-load-class-andr
My conclusion thus far is that android instrumentation tests do not support
FragmentActivity or other activi
6 matches
Mail list logo
