feat(waitFor): Automatically advance Jest fake timers #878
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:
Closes #873
Why:
There's little value in
waitFor
if one has to advance timers by themselves.How:
Copy implementation from
@testing-library/dom
.There's an opportunity to write a more generic
waitFor
that we can share across Testing Library that specific host configs build on top on (e.g. also running MutationObserver in/dom
). But that requires more coordination (starting with an extensive test suite). For now this hopefully suffices (pending testing in actual codebases).Checklist: