Clarify warning when making changes to UI tests #38645
Merged
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.
Any change to a UI test file currently gives this warning:
This is a useful warning for folks well versed in our UI testing to prevent blocking a test build with changes that could have been tested in Drone, but not as great for people with less experience who are making small changes and might view this warning as a requirement for merging a PR with changes to a UI test file.
New warning (updated to 2021 from 2020 since screenshot was taken 馃う ) -- message is kind of verbose, if others have ideas on how to make it more concise/clear.:
Currently, Drone will not pass with
[test all browsers]
specified -- there's more discussion here about differences between our test environment and Drone that might cause this problem, but looking at a couple recent failures using the[test all browsers]
tag (here's one), I wonder if things might just time out on Drone when testing all browsers. Here's some of the log: