fix: configure dom-testing-library to flush Svelte changes #439
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.
Overview
While working on new examples for Svelte 5, I found a problem with this library's interop with
@testing-library/user-event
- depending on project setup,await user.click()
et. al. does not wait for Svelte to flush changes.We were missing a call to
configure
to@testing-library/dom
to configure theeventWrapper
(forfireEvent
) andasyncWrapper
(foruser-event
) options. This fixes the issue foruser-event
, and happily, removes the need for an async re-export offireEvent
once we're able to drop Svelte 3/4, thanks to the newflushSync
export fromsvelte
Related (old) issue: #250
Change log
setup
function to complementcleanup
function that calls@testing-library/dom::configure
withtick
andflushSync
setup
intobeforeEach
for Jest and Vitest