Component test basics

What this means

A component test renders one component or a small tree, then checks the result. Testing libraries encourage queries that resemble how users find things: text, labels, roles.

In beginner terms, this topic answers one practical question: "What should I write, and why does React care about it?" Do not try to memorize the syntax first. First understand the idea, then connect the syntax to that idea.

Why it matters

This gives confidence that the component works outside the full app. It is especially useful for forms, buttons, and conditional UI.

When you build real React screens, this idea helps you decide where data should live, what the user should see, and what should happen after an interaction. That is why this lesson is part of the main path instead of being an optional detail.

Step by step

1. Notice the UI problem this topic solves. 2. Look at the smallest possible example. 3. Change one value and predict what should appear. 4. Run the example and compare the result with your prediction. 5. Use the practice task before moving on.

Small example

render(<Counter />);
await user.click(screen.getByRole("button", { name: "Add" }));

Common mistake

Do not rely only on class names for behavior tests. Text, labels, and roles usually describe user intent better.

Practice task

Write the steps for testing a login form with email, password, and submit.

Remember this

Component tests should interact like a user.