This repository was archived by the owner on Mar 3, 2023. It is now read-only.
Provide more context when test fails due to timeout in waitsFor
#17351
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.
Prior to this change, if a test timed out using
waitsFor
, you ended up with a fairly vague error message:If a test has multiple
waitsFor
calls, that error message leaves you wondering which one failed. 😭We ran into this problem when investigating #17325, in which the failing test included multiple places where the timeout could have occurred:
One option is to pass a custom error message to each
waitsFor
call. While that's still possible, we'd like the default error message to give you a better chance of diagnosing the problem. With the changes in this pull request, if you don't pass a custom error message,waitsFor
will show you the filename and line number where the timeout occurred.Example
Before
After