Update tests from fireEvent
to userEvent
#44952
Merged
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?
Migrate
fireEvent
usages to@testing-library/user-event
.In this case, I decided to start by looking at instances of
fireEvent.click
as the PR would be too large if all instances offireEvent
were included.And hopefully, by addressing these by method it will be helpful for others trying to migrate from
fireEvent
and learn about which methods to move to.Why?
The
user-event
library provides a more realistic simulation of how a user interacts with the DOM and is the preferred method according to Testing Library docs and our own docs:https://github.com/WordPress/gutenberg/blob/trunk/docs/contributors/code/testing-overview.md#user-interaction
How?
Testing Instructions
Make sure all tests pass by running
npm run test:unit [file-name]
for the following: