The answer
Behavior. Simulate user events like clicks and typing with userEvent, then assert the result, like a count changed or a message appeared. This tests real behavior, not implementation details, and survives refactors.
How to Write Your First React Component Test
What should my next React tests cover?
More FAQs in How to Write Your First React Component Test
Create a .test.js file, import render and screen from RTL and your component, use Jest's test function, render the component, query an element by role and name, and assert it is in the document. Run with npm test.
Use RTL's screen queries, preferably by role and accessible name, like screen.getByRole('heading', { name: /hello/i }). These are the same queries screen readers use, so they focus on what the user experiences.
It mounts your component in a simulated DOM provided by jsdom, so you can query and interact with the rendered output. After render, you use screen queries to find elements.
Still have questions?
Browse all our FAQs or reach out to our support team
Want to upskill yourself?
Your learning library
Small steps. Big possibilities.
Find your next course. Build something great.