[android-developers] Re: Instrumentation failing with classnotfound on android.test.InstrumentationTestRunner
Note that the cmd line is:
adb shell am instrument -e class com.novoda.runbuddy.AllTests -w
com.novoda.runbuddy/android.test.InstrumentationTestRunner
and not as previously stated:
adb shell am instrument -e class com.android.samples.AllTests -w
com.novoda.runbuddy/android.test.InstrumentationTestRunner
The error is still apparent
On Aug 22, 12:18 pm, "Carl H." <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I am trying to follow the post on
> ApplicationInstrumentation:http://code.google.com/android/samples/ApiDemos/tests/src/com/android...http://code.google.com/android/samples/ApiDemos/tests/src/com/android...
>
> My setup is very similar then the example. I have the following in my
> manifest:
> http://schemas.android.com/apk/res/
> android"
> android:targetPackage="com.novoda.runbuddy"
> android:name="android.test.InstrumentationTestRunner"
> android:label="testInst" />
>
> And I start the instrumentation like this:
> adb shell am instrument -e class com.android.samples.AllTests -w
> com.novoda.runbuddy/android.test.InstrumentationTestRunner
>
> I get the following error message:
> INSTRUMENTATION_RESULT: shortMsg=Unable to instantiate instrumentation
> ComponentInfo{com.novoda.runbuddy/
> android.test.InstrumentationTestRunner}:
> java.lang.ClassNotFoundException:
> android.test.InstrumentationTestRunner in loader
> [EMAIL PROTECTED]
> INSTRUMENTATION_RESULT: longMsg=java.lang.RuntimeException: Unable to
> instantiate instrumentation ComponentInfo{com.novoda.runbuddy/
> android.test.InstrumentationTestRunner}:
> java.lang.ClassNotFoundException:
> android.test.InstrumentationTestRunner in loader
> [EMAIL PROTECTED]
> INSTRUMENTATION_CODE: 0
>
> I tried different combination and can not make the above work. The
> documentation is sparse so I am not sure where I am going wrong. Why
> would I get a class not found on android.test? There is no need for
> permission from what I take with the new SDK.
>
> Any ideas?
> ./Acsia
--~--~-~--~~~---~--~~
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
[EMAIL PROTECTED]
Announcing the new Android 0.9 SDK beta!
http://android-developers.blogspot.com/2008/08/announcing-beta-release-of-android-sdk.html
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~--~~~~--~~--~--~---
[android-developers] Re: Instrumentation failing with classnotfound on android.test.InstrumentationTestRunner
Did you notice there is one more AndroidManifest.xml file under the /tests
folder in ApiDemos...perhaps you are missing that...
We will add more information to the docs ...
On Fri, Aug 22, 2008 at 4:50 AM, Carl H. <[EMAIL PROTECTED]> wrote:
>
> Note that the cmd line is:
>
> adb shell am instrument -e class com.novoda.runbuddy.AllTests -w
> com.novoda.runbuddy/android.test.InstrumentationTestRunner
>
> and not as previously stated:
> adb shell am instrument -e class com.android.samples.AllTests -w
> com.novoda.runbuddy/android.test.InstrumentationTestRunner
>
> The error is still apparent
>
>
>
>
> On Aug 22, 12:18 pm, "Carl H." <[EMAIL PROTECTED]> wrote:
> > Hello,
> >
> > I am trying to follow the post on ApplicationInstrumentation:
> http://code.google.com/android/samples/ApiDemos/tests/src/com/android...http://code.google.com/android/samples/ApiDemos/tests/src/com/android.
> ..
> >
> > My setup is very similar then the example. I have the following in my
> > manifest:
> > http://schemas.android.com/apk/res/
> > android"
> > android:targetPackage="com.novoda.runbuddy"
> > android:name="android.test.InstrumentationTestRunner"
> > android:label="testInst" />
> >
> > And I start the instrumentation like this:
> > adb shell am instrument -e class com.android.samples.AllTests -w
> > com.novoda.runbuddy/android.test.InstrumentationTestRunner
> >
> > I get the following error message:
> > INSTRUMENTATION_RESULT: shortMsg=Unable to instantiate instrumentation
> > ComponentInfo{com.novoda.runbuddy/
> > android.test.InstrumentationTestRunner}:
> > java.lang.ClassNotFoundException:
> > android.test.InstrumentationTestRunner in loader
> > [EMAIL PROTECTED]
> > INSTRUMENTATION_RESULT: longMsg=java.lang.RuntimeException: Unable to
> > instantiate instrumentation ComponentInfo{com.novoda.runbuddy/
> > android.test.InstrumentationTestRunner}:
> > java.lang.ClassNotFoundException:
> > android.test.InstrumentationTestRunner in loader
> > [EMAIL PROTECTED]
> > INSTRUMENTATION_CODE: 0
> >
> > I tried different combination and can not make the above work. The
> > documentation is sparse so I am not sure where I am going wrong. Why
> > would I get a class not found on android.test? There is no need for
> > permission from what I take with the new SDK.
> >
> > Any ideas?
> > ./Acsia
> >
>
--~--~-~--~~~---~--~~
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
[EMAIL PROTECTED]
Announcing the new Android 0.9 SDK beta!
http://android-developers.blogspot.com/2008/08/announcing-beta-release-of-android-sdk.html
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~--~~~~--~~--~--~---
[android-developers] Re: Instrumentation failing with classnotfound on android.test.InstrumentationTestRunner
Hi Megha,
I did not notice that no, was looking at the site. I tried to add the
second androidManifest to my project under the "acceptance" folder
which is my test folder. When I try to compile and install the app
onto the device, I get the following error:
08-23 07:58:21.129: WARN/PackageParser(54): Unable to read
AndroidManifest.xml of /data/app/vmdl31345.tmp
08-23 07:58:21.129: WARN/PackageParser(54):
java.io.FileNotFoundException: AndroidManifest.xml
I did follow the instruction on changing the package name etc... I
have several questions:
1. Do I need to have the instrumentation in another app - thus
installing 2 different apps (signing them correctly I suppose)?
2. Why do you use the permission run_instrumentation? I thought there
was no need for it in 0.9?
More documentation here would be much appreciated indeed!
Thanks,
Car aka acsia
On Aug 22, 11:05 pm, "Megha Joshi" <[EMAIL PROTECTED]> wrote:
> Did you notice there is one more AndroidManifest.xml file under the /tests
> folder in ApiDemos...perhaps you are missing that...
> We will add more information to the docs ...
>
> On Fri, Aug 22, 2008 at 4:50 AM, Carl H. <[EMAIL PROTECTED]> wrote:
>
> > Note that the cmd line is:
>
> > adb shell am instrument -e class com.novoda.runbuddy.AllTests -w
> > com.novoda.runbuddy/android.test.InstrumentationTestRunner
>
> > and not as previously stated:
> > adb shell am instrument -e class com.android.samples.AllTests -w
> > com.novoda.runbuddy/android.test.InstrumentationTestRunner
>
> > The error is still apparent
>
> > On Aug 22, 12:18 pm, "Carl H." <[EMAIL PROTECTED]> wrote:
> > > Hello,
>
> > > I am trying to follow the post on ApplicationInstrumentation:
> >http://code.google.com/android/samples/ApiDemos/tests/src/com/android
> > ..
>
> > > My setup is very similar then the example. I have the following in my
> > > manifest:
> > > http://schemas.android.com/apk/res/
> > > android"
> > > android:targetPackage="com.novoda.runbuddy"
> > > android:name="android.test.InstrumentationTestRunner"
> > > android:label="testInst" />
>
> > > And I start the instrumentation like this:
> > > adb shell am instrument -e class com.android.samples.AllTests -w
> > > com.novoda.runbuddy/android.test.InstrumentationTestRunner
>
> > > I get the following error message:
> > > INSTRUMENTATION_RESULT: shortMsg=Unable to instantiate instrumentation
> > > ComponentInfo{com.novoda.runbuddy/
> > > android.test.InstrumentationTestRunner}:
> > > java.lang.ClassNotFoundException:
> > > android.test.InstrumentationTestRunner in loader
> > > [EMAIL PROTECTED]
> > > INSTRUMENTATION_RESULT: longMsg=java.lang.RuntimeException: Unable to
> > > instantiate instrumentation ComponentInfo{com.novoda.runbuddy/
> > > android.test.InstrumentationTestRunner}:
> > > java.lang.ClassNotFoundException:
> > > android.test.InstrumentationTestRunner in loader
> > > [EMAIL PROTECTED]
> > > INSTRUMENTATION_CODE: 0
>
> > > I tried different combination and can not make the above work. The
> > > documentation is sparse so I am not sure where I am going wrong. Why
> > > would I get a class not found on android.test? There is no need for
> > > permission from what I take with the new SDK.
>
> > > Any ideas?
> > > ./Acsia
>
>
--~--~-~--~~~---~--~~
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
[EMAIL PROTECTED]
Announcing the new Android 0.9 SDK beta!
http://android-developers.blogspot.com/2008/08/announcing-beta-release-of-android-sdk.html
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~--~~~~--~~--~--~---
[android-developers] Re: Instrumentation failing with classnotfound on android.test.InstrumentationTestRunner
I have made this work correctly and discuss it on my blog here:
http://devtcg.blogspot.com/2008/08/android-instrumentation-example.html
On Aug 23, 1:02 am, "Carl H." <[EMAIL PROTECTED]> wrote:
> Hi Megha,
>
> I did not notice that no, was looking at the site. I tried to add the
> second androidManifest to my project under the "acceptance" folder
> which is my test folder. When I try to compile and install the app
> onto the device, I get the following error:
>
> 08-23 07:58:21.129: WARN/PackageParser(54): Unable to read
> AndroidManifest.xml of /data/app/vmdl31345.tmp
> 08-23 07:58:21.129: WARN/PackageParser(54):
> java.io.FileNotFoundException: AndroidManifest.xml
>
> I did follow the instruction on changing the package name etc... I
> have several questions:
>
> 1. Do I need to have theinstrumentationin another app - thus
> installing 2 different apps (signing them correctly I suppose)?
> 2. Why do you use the permission run_instrumentation? I thought there
> was no need for it in 0.9?
>
> More documentation here would be much appreciated indeed!
>
> Thanks,
> Car aka acsia
>
> On Aug 22, 11:05 pm, "Megha Joshi" <[EMAIL PROTECTED]> wrote:
>
> > Did you notice there is one more AndroidManifest.xml file under the /tests
> > folder in ApiDemos...perhaps you are missing that...
> > We will add more information to the docs ...
>
> > On Fri, Aug 22, 2008 at 4:50 AM, Carl H. <[EMAIL PROTECTED]> wrote:
>
> > > Note that the cmd line is:
>
> > > adb shell am instrument -e class com.novoda.runbuddy.AllTests -w
> > > com.novoda.runbuddy/android.test.InstrumentationTestRunner
>
> > > and not as previously stated:
> > > adb shell am instrument -e class com.android.samples.AllTests -w
> > > com.novoda.runbuddy/android.test.InstrumentationTestRunner
>
> > > The error is still apparent
>
> > > On Aug 22, 12:18 pm, "Carl H." <[EMAIL PROTECTED]> wrote:
> > > > Hello,
>
> > > > I am trying to follow the post on ApplicationInstrumentation:
> > >http://code.google.com/android/samples/ApiDemos/tests/src/com/android
> > > ..
>
> > > > My setup is very similar then the example. I have the following in my
> > > > manifest:
> > > > > >http://schemas.android.com/apk/res/
> > > > android"
> > > > android:targetPackage="com.novoda.runbuddy"
> > > > android:name="android.test.InstrumentationTestRunner"
> > > > android:label="testInst" />
>
> > > > And I start theinstrumentationlike this:
> > > > adb shell am instrument -e class com.android.samples.AllTests -w
> > > > com.novoda.runbuddy/android.test.InstrumentationTestRunner
>
> > > > I get the following error message:
> > > > INSTRUMENTATION_RESULT: shortMsg=Unable to instantiateinstrumentation
> > > > ComponentInfo{com.novoda.runbuddy/
> > > > android.test.InstrumentationTestRunner}:
> > > > java.lang.ClassNotFoundException:
> > > > android.test.InstrumentationTestRunner in loader
> > > > [EMAIL PROTECTED]
> > > > INSTRUMENTATION_RESULT: longMsg=java.lang.RuntimeException: Unable to
> > > > instantiateinstrumentationComponentInfo{com.novoda.runbuddy/
> > > > android.test.InstrumentationTestRunner}:
> > > > java.lang.ClassNotFoundException:
> > > > android.test.InstrumentationTestRunner in loader
> > > > [EMAIL PROTECTED]
> > > > INSTRUMENTATION_CODE: 0
>
> > > > I tried different combination and can not make the above work. The
> > > > documentation is sparse so I am not sure where I am going wrong. Why
> > > > would I get a class not found on android.test? There is no need for
> > > > permission from what I take with the new SDK.
>
> > > > Any ideas?
> > > > ./Acsia
--~--~-~--~~~---~--~~
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
[EMAIL PROTECTED]
Announcing the new Android 0.9 SDK beta!
http://android-developers.blogspot.com/2008/08/announcing-beta-release-of-android-sdk.html
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~--~~~~--~~--~--~---
