New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document testApkTarget
#13
Comments
I was having similar problems, so I'm glad this issue was opened. The documentation is definitely sparse right now. |
TBH, I'm not a gradle expert so I might have got this wrong. testApkTarget should be the target that generates the APK, and connectedAndroidTestTarget should be the target that runs it. At least that's how it's meant to be, and I hope I can get rid of testApkTarget and somehow discover it from connectedAndroidTestTarget. Can you show me a typical gradle configuration where the default setup won't work? I'll try to optimize the error messages for that configuration if possible. |
Pretty much any time that there are build flavors is the issue, I think. I can try to set up a demo on github later. |
I have the same issue with build flavors, tried it with version 0.4.
|
I have been having the same problem with pullScreenshots. Is this being worked on or is this project dead? |
hmm, I'm able to repro if use productFlavors {} to the example app. Looking into it, I can probably make the output better, but the workaround is to use
|
I couldn't get my tests working using |
Documented in the wiki https://github.com/facebook/screenshot-tests-for-android/wiki/Gradle-Setup |
I added the plugin to my build, with the instructions found in http://facebook.github.io/screenshot-tests-for-android/#getting-started and then tried running
gradle tasks
. I got the error:Through looking through the stacktrace and googling I found #1 and the fact I need to do the following to inform screenshots about the name of the test task:
Which will be different for a lot of users. It would be good if either the docs mentioned this or there was a more helpful error message when it's not configured properly.
The text was updated successfully, but these errors were encountered: