austgl / robotium

Automatically exported from code.google.com/p/robotium
0 stars 0 forks source link

Test run failed: Unable to find instrumentation target package #130

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Followed steps from tutorial files
2. Tried to run the "Test Android Sample Application with Robotium" as specified
3. got a error: "Test run failed: Unable to find instrumentation target package"

What is the expected output? What do you see instead?

Test should be carried out as specified in tutorial.

What version of the product are you using? On what operating system?

I am running windows 7 professional

No other error messages appear, everything seems to be fine, except for this 
error msg.

Hope the information I gave helps you help me fix the problem.

Thank you for your time!

Original issue reported on code.google.com by bogdan.d...@gmail.com on 26 Jul 2011 at 7:02

GoogleCodeExporter commented 9 years ago
Manadged to fix that problem.

In AndroidCalculatorTest -> AndroidManifest.xml you have to edit

<instrumentation android:targetPackage="" 
android:name="android.test.InstrumentationTestRunner" />

to 

<instrumentation android:targetPackage="com.calculator" 
android:name="android.test.InstrumentationTestRunner" />\

Original comment by bogdan.d...@gmail.com on 26 Jul 2011 at 7:36

GoogleCodeExporter commented 9 years ago

Original comment by renasr...@gmail.com on 26 Jul 2011 at 8:47

GoogleCodeExporter commented 9 years ago
Thanks for posting your fix.

Original comment by tkdan...@gmail.com on 17 Aug 2011 at 10:10

GoogleCodeExporter commented 9 years ago
thank you bogdan

Original comment by seethala...@gmail.com on 20 Dec 2012 at 5:32

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
I have also done with this but still it is showing me error.

Original comment by Tlakh...@gmail.com on 1 Oct 2013 at 1:11

GoogleCodeExporter commented 9 years ago
I am also facing the same issue... any update how it got resolved at your 
end....

Original comment by rohitkot...@gmail.com on 28 May 2014 at 7:50

GoogleCodeExporter commented 9 years ago
Did anyone manage to fix this? Any update?

Original comment by s...@farmlogs.com on 15 Sep 2014 at 5:50