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
Support for multiple build variants #1
Comments
what command do you typically use to run your tests? I probably need to make this line customizable: https://github.com/facebook/screenshot-tests-for-android/blob/master/plugin/src/main/groovy/com/facebook/testing/screenshot/build/ScreenshotsPlugin.groovy#L72 |
|
ah, looks like I have a bug in https://github.com/facebook/screenshot-tests-for-android/blob/master/plugin/src/main/groovy/com/facebook/testing/screenshot/build/ScreenshotsPlugin.groovy#L17 where I'm reading the property before you get a chance to set it which kind of defeats the purpose. Let me fix this. |
I landed a fix: 7b3e997 Would you be able to install the jars into a local maven to test this out? If it works, I'll deploy it as a new version early next week (will try to bundle it with other bugs) |
Yep, that fixes it for me. At least it gets me to another error. I'll take a look at that tomorrow. |
Still having issues? I'm closing this task out for now, but feel free to open another one for the new issues! |
Please update it the plugin jar on Maven. |
@arpit130, I have updated the jar on maven central and bumped the version to 0.2.2. Let me know if you find any issues |
FIX issues with scope storage
Thanks for releasing this! I've been looking forward to taking a look at it.
My app has a bunch of build types and a couple build flavors yielding lots of different build variants. When I follow the docs to add your project and run a simple test, I get the following error:
It looks like the plugin is trying to find the
packageDebugAndroidTest
task, which doesn't exist in my app. Instead, I would like to use thepackagePlayInternalDebugAndroidTest
task.Looking around in the plugin, I found this, which suggests that I can configure the plugin like so:
Even with this line, I get the same error. Any advice?
The text was updated successfully, but these errors were encountered: