I've been getting a lot of hands-on time with React Testing Library recently and, for the most part, I really like it. Still, I get caught out from time-to-time, and this article has a lot of great advice on best practices. In particular (as I tweeted this week) I've found that following this guidance doesn't just make writing tests easier, it also gives you accessibility coverage for free, which is just awesome 😎
- Source
- Link to Original 🔗
- Published
- Categories
- JavaScript, Nuts & Bolts, Inclusion
- Tags
- React, testing, QA, Testing Library, assertions, mistakes, a11y, accessibility
Explore Other Notes
⬅ Newer
Hey now
Can you use progressive enhancement when building a web app (whatever that is)? Of course you can, HEY have proven so (not that it should have needed …
Older ➡
CSS only carousel
Carousels are the devil's work, but they remain incredibly useful and popular UI elements 😑 Having a solid implementation that will work without JavaScript, making it more lightweight and …
- <!DOCTYPE html> <html> <head> <title></title> </head> <body> <p>I've been getting a lot of hands-on time with React Testing Library recently and, for the most part, I really like it. Still, I get caught out from time-to-time, and this article has a lot of great …</p> </body> </html>
- Murray Champernowne
