[test] Fix flaky tooltip test #47589
Draft
+12
−5
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
Netlify deploy previewhttps://deploy-preview-47589--material-ui.netlify.app/ Bundle size report
|
ZeeshanTamboli
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR fixes a flaky browser-only Tooltip delay test by switching from deprecated
TransitionPropstoslotProps.transition, removing the unreliableflushMicrotasksstep, and asserting the boundary aroundleaveDelay(still mounted atleaveDelay - 1, then closing atleaveDelay). It then advances the clock slightly past the configured transition timeout to allow the exit transition to fully complete and Popper to setexited, ensuring the tooltip unmounts deterministically.I ran the CI 7 times after this commit: b44344a and all the run passes.