We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Right now, we have some androidTests that do not yet automatically run. We should build automation that runs these as part of our CI builds.
Open question: At what step(s) should we run them? PR? Main merge? Nightly?
Open question: What devices with what android versions?
Are there pros/cons to not just having it be part of every PR build?
The text was updated successfully, but these errors were encountered:
One options for this: https://github.com/marketplace/actions/android-emulator-runner
Sorry, something went wrong.
Done in #509
No branches or pull requests
Right now, we have some androidTests that do not yet automatically run. We should build automation that runs these as part of our CI builds.
Open question: At what step(s) should we run them? PR? Main merge? Nightly?
Open question: What devices with what android versions?
Are there pros/cons to not just having it be part of every PR build?
The text was updated successfully, but these errors were encountered: