Fix error messages when used with flavors about screenshot-tests-for-android

[tdrhq]

(I should preface this by saying that while I wrote all the gradle scripts here, I'm by no means a gradle expert so I might be wrong about what I'm going to say, but here goes:)

you need to set up both testApkTarget and connectedAndroidTestTarget. The first is the one that generates the APK, the second is the one that runs the tests on the devies. So it looks like the flavored target you listed should actually be the connectedAndroidTestTarget configuration.

In theory I should be able to figure out the testApkTarget from connectedAndroidTestTarget and simplify the configuration. I'll see if I can make that work somehow, but in the meantime can you try my suggestion and see if this works?

[Kusand]

Got it now. I'd update your documentation to reflect that testApkTarget
needs to be "package" and the connectedAndroidTestTarget
needs to be "connected". I'm pretty sure this is only needed
because I'm using flavors. Having it automatically respect flavors would
also be nice.

On Thu, Dec 3, 2015 at 1:34 PM, Arnold Noronha [email protected]
wrote:

(I should preface this by saying that while I wrote all the gradle scripts
here, I'm by no means a gradle expert so I might be wrong about what I'm
going to say, but here goes:)

you need to set up both testApkTarget and connectedAndroidTestTarget. The
first is the one that generates the APK, the second is the one that runs
the tests on the devies. So it looks like the flavored target you listed
should actually be the connectedAndroidTestTarget configuration.

In theory I should be able to figure out the testApkTarget from
connectedAndroidTestTarget and simplify the configuration. I'll see if I
can make that work somehow, but in the meantime can you try my suggestion
and see if this works?

—
Reply to this email directly or view it on GitHub
#17 (comment)
.

[gpeal]

I also had to do this and it resolved my issue. Documentation around this would be incredibly helpful!

[Kusand]

I've added documentation in The Gradle Setup wiki page, in the hopes of helping others.

[kylannjohnson]

I needed to do this

// This task reports the location of the Test APK generated by the build for use by Facebook Screenshot Tests
task packageDebugAndroidTest(dependsOn: 'assembleDebugTest') {
  outputs.dir file("${buildDir}/outputs/apk").listFiles().findAll {it.name.contains('androidTest-unaligned')}
}

[athkalia]

Having a similar problem related to flavors.
After the usual

gradlew :<mylibraryname>:screenshotTests

(note that this is a library project and 'mylibraryname' is just a dummy name)
I am getting a:

> Task with path 'packageDebugAndroidTest' not found in project ':<mylibraryname>'.

Instead there is a 'packageProductionDebugAndroidTest' defined task where 'Production' is a flavor.
Isn't there a way to pick that up automatically?

[SergeyShustikov]

I facing with the same problem.

[xiphirx]

The rewrite generates tasks per flavor.