test: prevent false-positive with fake timers#1010
Merged
ph-fritsche merged 1 commit intomainfrom Aug 2, 2022
Merged
Conversation
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 6c5f272:
|
Codecov Report
@@ Coverage Diff @@
## main #1010 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 87 87
Lines 1876 1876
Branches 679 679
=========================================
Hits 1876 1876 Help us with your feedback. Take ten seconds to tell us how you rate us. |
|
🎉 This PR is included in version 14.4.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What:
Prevent false-positive test due to slow test environment.
Why:
Sometimes the execution is delayed just enough to make this assertion fail.
Checklist: