Merge into testing libraries and recommend over fireEvent
See original GitHub issueNow that this package is mentioned in the testing library docs, it would be nice to expand it enough to be recommended over fireEvent
in most cases and include it in the original packages. We should think about what common user interactions are missing that are tricky to implement with fireEvent
. Other testing tools like Cypress could be good inspiration.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:26
- Comments:21 (18 by maintainers)
Top Results From Across the Web
Setup - Testing Library
Configuring Jest with Test Utils If you're using TypeScript, merge this into your tsconfig. json .
Read more >reactjs - Web & mobile cross platform tests by merging react ...
I tried to merge both libraries for cross platform tests when using react-native-web, by resolving file extensions by platform so I can ...
Read more >Migration to 7.0 | React Native Testing Library - Open Source
As the version 7.0 involves merging two libraries together, there are two variants for migration guide, dependent on library you used previously:.
Read more >eslint-plugin-testing-library - npm
Start using eslint-plugin-testing-library in your project by running `npm ... prefer-user-event, Suggest using userEvent over fireEvent for ...
Read more >An Engineer's Guide to Automated Testing: React Native Apps
React Native Testing Library (RNTL) is equipped with utility functions ... Many engineers will often recommend the use of RNTL over Enzyme.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Ok, after thinking about this and feeling revitalized thanks to @nickmccurdy’s personal interest, I’m motivated to making this happen. Let’s make this happen, and in the next day or two. We can leave this package without a major version bump (though perhaps we’d do a major version bump akin to https://npm.im/dom-testing-library to announce the deprecation of the package), and we can do a minor version bump to DOM Testing Library when we add the feature.
I’ll be working on this for the next day or two. FYI @testing-library/all-maintainers
To be honest, the way user-event handles the events is how I expected testing-library to handle them the first time I use it. I think this is a good idea.