-
-
Notifications
You must be signed in to change notification settings - Fork 48
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 Robo Tests without Robo script #165
Comments
Oh, I didn't realize this was a use case. Thanks for reporting. Do you know if flank itself supports this? |
Yes, flank supports this but you must specify |
I was initially looking to effectively simulate prelaunch reports, without having to upload to Google Play. I've tried running this directly with the gcloud command without roboscript or robo-directives, which works. Let me check on what's involved with robo-directives, because maybe an empty set of robo-directives would work. |
Is the fix in fladle to allow a roboDirective to be specified without specifying a roboScript or an instrumentation APK? I can do this relatively quickly if this is what is needed. Please confirm. Thanks! |
I tried with flank, and it looks like it has a requirement that one of these be set:
I tried just setting fake robo-directives but it still would not run, so this looks like a limitation in flank currently. |
Ah, in that case, can you open an issue in the flank repository? Link it from here. It's likely we'll both need to make changes. |
FYI the underlying Flank issue was just resolved 🎉 |
@runningcode |
Please do! Thanks! |
This is an enhancement request to support robo tests without a robo script. Firebase Test Lab supports this, although it appears fladle does not. In the fladle source, the decision to do a robo test is based on the roboscript file path being non-null.
Issues sometimes come up with R8, ProGuard, or DexGuard that make robo testing the my release APK helpful in catching issues that might occur during first launch. However, DexGuard also obfuscates resource IDs which makes creating a roboscript for a release build much more difficult.
Being able to launch a robo test without a roboscript will enable my use case, but would also lower the barrier for others who want to run a robo test without recording a script.
The text was updated successfully, but these errors were encountered: