mahmud83 / maven-android-plugin

Automatically exported from code.google.com/p/maven-android-plugin
0 stars 0 forks source link

apk renameInstrumentationTargetPackage does not update the test runner target #428

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. configure android-maven-plugin with renameInstrumentationTargetPackage to 
some new package
2. configure android-maven-plugin with renameManifestPackage to some new package
3. mvn install

What is the expected output?
Tests run against the renamed package on the device using the renamed test 
runner

What do you see instead?

[ERROR] Failed to execute goal 
com.jayway.maven.plugins.android.generation2:android-maven-plugin:3.8.0:internal
-integration-test (default-internal-integration-test) on project talko-test: 
emulator-5554_Nexus4_4.3_unknown_AndroidSDKbuiltforx86 :   Test run failed to 
complete: Unable to find instrumentation info for: 
ComponentInfo{PACKAGE.IN.MANIFEST.BEFORE.RENAME/FULLY.QUALIFIED.TEST.RUNNER.BEFO
RE.RENAME} -> [Help 1]

What version of maven-android-plugin are you using?
3.8.0

What are the complete output lines of "mvn -version" on your machine?

Apache Maven 3.1.1 (0728685237757ffbf44136acec0402957f723d9a; 2013-09-17 
08:22:22-0700)
Maven home: /usr/local/Cellar/maven/3.1.1/libexec
Java version: 1.6.0_45, vendor: Apple Inc.
Java home: /Library/Java/JavaVirtualMachines/1.6.0_45-b06-451.jdk/Contents/Home
Default locale: en_US, platform encoding: MacRoman
OS name: "mac os x", version: "10.9", arch: "x86_64", family: "mac"

Please provide any additional information below.

I'm guessing the the instrumentation info is pulled from the Android manifest 
and not updated with the renameInstrumentationTargetPackage and 
renameManifestPackage info

Original issue reported on code.google.com by xcolw...@gmail.com on 22 Nov 2013 at 6:16

GoogleCodeExporter commented 9 years ago
If this is confirmed a bug, I would be happy to work on a patch to fix it.

Original comment by xcolw...@gmail.com on 26 Nov 2013 at 12:48

GoogleCodeExporter commented 9 years ago
Just a heads up for anyone else who may encounter this - I moved away from 
using android-maven-plugin's integration tests to Square's Spoon [1]. Spoon 
uses the information in the APK to run tests, which works great with the 
renamed packages.

1. https://github.com/square/spoon

Original comment by xcolw...@gmail.com on 30 Nov 2013 at 1:00

GoogleCodeExporter commented 9 years ago
We are no longer using the issue tracking system on Google Code. Please refile 
this issue on https://github.com/jayway/maven-android-plugin/issues if you 
still have this problem with the latest release of the Android Maven Plugin

Original comment by mosa...@gmail.com on 19 May 2014 at 4:20