Only run UI tests from org.wordpress.android.e2e on Firebase Test Lab #10069
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
JavonDavis
approved these changes
Jun 20, 2019
Contributor
JavonDavis
left a comment
JavonDavis
left a comment
There was a problem hiding this comment.
Let's go ahead and merge and see how stable they are 👍🏽
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For the past month or so we have been running connected tests every night on Firebase Test Lab (see #9836). Unfortunately, these have proven to be quite flaky. This change is to only run the UI tests (in the
org.wordpress.android.e2epackage) in the nightly run. As well as eliminating the most flaky test (WPScreenshotTest), it speeds up the tests considerably which will be helpful if we decide to move the runs to each PR.To test:
Update release notes:
RELEASE-NOTES.txt.