These are my top tips for anyone using the React Testing Library package for their unit tests. I hope they help you avoid major pain points.

Atomic Object is a software consultancy specializing in custom software development and product design. Readers can learn about software development methodologies, user-centered design principles, and agile practices. With case studies, blog posts, and technical insights, Atomic Object provides  guidance and expertise for building innovative and user-friendly software products.

Atomic Spin

Unit testing ensures code functions as expected. Test-driven development (TDD) at Atomic Object involves writing tests based on code requirements first. This post offers tips for using React Testing Library efficiently, such as choosing the right query method (getBy, findBy, queryBy), avoiding multiple assertions in a waitFor, and using screen instead of destructuring functions from render. Also, using an ESLint plugin can help avoid common pitfalls.

Tips for Using React Testing Library to Write Unit Tests

Don’t have multiple assertions in a waitFor.

Don’t export functions from render and use screen instead.