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 shell am instrument -w
jp.cyberagent.testgrid.android.sample.test/android.test.InstrumentationTestRunner
Adding "-e package jp.cyberagent.testgrid.android.sample.test" has the same
problem.
whereas this will run it okay:
adb shell am instrument -w -e class
jp.cyberagent.testgrid.android.sample.test.SampleActivityTest
jp.cyberagent.testgrid.android.sample.test/android.test.InstrumentationTestRunner
Now the question is: WHY?
On Friday, October 26, 2012 9:12:17 AM UTC+9, Patrick Boos wrote:
>
> 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 between how
> eclipse runs those tests?
>
> On Wednesday, August 29, 2012 5:35:52 PM UTC+9, blizzard wrote:
>>
>> 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 purpose
>>
>>
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
