@testing-library/user-event

Fire events the same way the user does

Downloads in past

Stats

StarsIssuesVersionUpdatedCreatedSize
@testing-library/user-event
1,8344514.4.34 months ago3 years agoMinified + gzip package size for @testing-library/user-event in KB

Readme


!Build Statusbuild-badgebuild !Code Coveragecoverage-badgecoverage !versionversion-badgepackage !downloadsdownloads-badgenpmtrends !MIT Licenselicense-badgelicense !All Contributorsall-contributors-badge !PRs Welcomeprs-badgeprs !Code of Conductcoc-badgecoc !Discorddiscord-badgediscord
!Watch on GitHubgithub-watch-badgegithub-watch !Star on GitHubgithub-star-badgegithub-star !Tweettwitter-badgetwitter

The problem

From testing-library/dom-testing-library#107:
... it is becoming apparent the need to express user actions on a web page using a higher-level abstraction than fireEventfire-event

The solution

user-event tries to simulate the real events that would happen in the browser as the user interacts with it. For example userEvent.click(checkbox) would change the state of the checkbox.
The more your tests resemble the way your software is used, the more confidence they can give you.guiding-principle

Issues

Looking to contribute? Look for the Good First Issuegood-first-issue label.

🐛 Bugs

Please file an issue for bugs, missing documentation, or unexpected behavior.
See Bugsbugs

💡 Feature Requests

Please file an issue to suggest new features. Vote on feature requests by adding a 👍. This helps maintainers prioritize what to work on.
See Feature Requestsrequests

❓ Questions

For questions related to using the library, please visit a support community instead of filing an issue on GitHub.

Contributors

We most sincerely thank the people who make this project possiblecontributors. Contributions of any kind are welcome! 💚

License

MIT