test: fix async tests resolved in random order #6143
Merged
Conversation
This file contains 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
Josh-Cena
added
the
pr: maintenance
|
✔️ [V2] 🔨 Explore the source changes: 6adfcd6 🔍 Inspect the deploy log: https://app.netlify.com/sites/docusaurus-2/deploys/61c1adb7b5d0ea0008c40234 😎 Browse the preview: https://deploy-preview-6143--docusaurus-2.netlify.app |
|
⚡️ Lighthouse report for the changes in this PR:
Lighthouse ran on https://deploy-preview-6143--docusaurus-2.netlify.app/ |
|
Size Change: 0 B Total Size: 658 kB ℹ️ View Unchanged
|
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.
Motivation
Sometimes the docs tests are not resolved in the correct order, resulting in the snapshots being updated randomly. This is because we didn't
awaitourexpectcall. I normalized these async tests to the right format.Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
It seems jest tests always succeed on the CI though, I wonder if it's because of some niceties of the GH Actions node...