-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use fake timers in DatePicker tests #40800
Conversation
This change results in this unexpected failure:
I'm not quite sure what's going on. Assumedly |
Size Change: 0 B Total Size: 1.24 MB ℹ️ View Unchanged
|
Mhh, that's unexpected. Let's merge #40801 first, rebase on |
e73646c
to
8751914
Compare
Done 🤞 |
Tests are still failing, and so I looked a bit more into what could be the reason:
Previously, not using fake timers made it so that these functions were not run (probably the expect assertion happened before them). Not sure if there's a way to fix this on our end. We could open an issue in the
|
Nice sleuthing! 🕵️
Hm, is this because it's not a real DOM? I think we'd need to reproduce the issue in a real browser before opening a bug report. I'm getting pretty far away from my main objective 😅 so I'll put this on the backburner for now. |
Yes, it could well be caused by how the Let's save this for a rainy day |
What?
Switches the DatePicker unit tests to use fake timers in line with @ciampo's feedback in #40754 (comment).
Why?
How?
Testing Instructions
npm run test
Screenshots or screencast