React Testing Library integration in NextJS - Step-by-Step Execution

Concept Flow - React Testing Library integration

Write React Component

↓

Write Test with RTL

↓

Render Component in Test

↓

Query Elements

↓

Simulate User Actions

↓

Assert Expected Output

↓

Test Pass or Fail

This flow shows how you write a React component, then write a test using React Testing Library (RTL), render the component in the test, query elements, simulate user actions, and finally check if the output matches expectations.

Execution Sample

NextJS

import { render, screen, fireEvent } from '@testing-library/react';
import Button from './Button';

test('button click changes text', () => {
  render(<Button />);
  fireEvent.click(screen.getByRole('button'));
  expect(screen.getByText('Clicked')).toBeInTheDocument();
});

This test renders a Button component, clicks it, and checks if the text changes to 'Clicked'.

Execution Table

Step	Action	Component State	Screen Query Result	Assertion Result
1	Render <Button />	Text: 'Click me'	Button found by role 'button'	N/A
2	fireEvent.click(button)	Text changes to 'Clicked'	Text 'Clicked' found	N/A
3	expect text 'Clicked' to be in document	Text: 'Clicked'	Text 'Clicked' found	Pass

💡 Test ends after assertion passes confirming UI updated correctly

Variable Tracker

Variable	Start	After Render	After Click	Final
buttonText	'Click me'	'Click me'	'Clicked'	'Clicked'

Key Moments - 2 Insights

Why do we use screen.getByRole instead of document.querySelector?

React Testing Library encourages queries that resemble how users find elements, like getByRole, which improves test reliability and accessibility. See execution_table step 1 where getByRole finds the button.

What happens if fireEvent.click is missing?

Without fireEvent.click, the buttonText state won't change, so the assertion in step 3 would fail because 'Clicked' text won't appear. This is shown in execution_table step 2.

Visual Quiz - 3 Questions

Look at the execution_table, what is the button text after rendering but before clicking?

A Empty string

B 'Clicked'

C 'Click me'

D Undefined

💡 Hint

Check 'Component State' column at Step 1 in execution_table

At which step does the test confirm the UI updated correctly?

A Step 1

B Step 3

C Step 2

D Test never confirms

💡 Hint

Look at 'Assertion Result' column in execution_table

If we replace fireEvent.click with fireEvent.change, what would happen?

A No change in text

B Test fails immediately

C Text changes to 'Clicked'

D Button disappears

💡 Hint

Refer to variable_tracker and execution_table step 2 where click triggers text change

Concept Snapshot

React Testing Library integration:
- Render component with render()
- Query elements with screen.getByRole or similar
- Simulate user events with fireEvent
- Assert UI changes with expect(...).toBeInTheDocument()
- Tests mimic user behavior for reliable results

Full Transcript

This visual guide shows how React Testing Library integrates with Next.js components. First, you write a React component, then a test that renders it using RTL's render function. The test queries elements using screen.getByRole, simulates user actions like clicks with fireEvent, and finally asserts expected UI changes with expect statements. The execution table traces each step: rendering the button with initial text, clicking it to change text, and confirming the new text appears. The variable tracker follows the button's text state through the test. Key moments clarify why RTL queries focus on user roles and what happens if user events are missing. The quiz tests understanding of component state at each step and effects of changing events. This approach ensures tests reflect real user interactions and accessibility best practices.

Practice

1. What is the main purpose of React Testing Library in a Next.js project?

easy

A. To manage global state in React applications

B. To style React components with CSS-in-JS

C. To test React components by simulating user interactions and checking visible output

D. To optimize React components for faster rendering

Solution

1. Step 1: Understand React Testing Library's role

   It focuses on testing components by simulating how users interact with them and what they see.

2. Step 2: Compare options with this role

   Only To test React components by simulating user interactions and checking visible output describes testing user interactions and visible output, which matches React Testing Library's purpose.

3. Final Answer:

   To test React components by simulating user interactions and checking visible output -> Option C

4. Quick Check:

   Testing user behavior = D [OK]

Hint: React Testing Library tests user actions and visible UI [OK]

Common Mistakes:

• Confusing testing library with styling or state management tools
• Thinking it optimizes rendering performance
• Assuming it manages app state

2. Which of the following is the correct way to import the render function from React Testing Library?

easy

A. import { render } from '@testing-library/react';

B. import render from 'react-testing-library';

C. import { render } from 'react-dom';

D. import { render } from 'next/testing';

Solution

1. Step 1: Identify the official package for React Testing Library

   The correct package is '@testing-library/react' for React Testing Library functions.

2. Step 2: Check import syntax

   React Testing Library exports render as a named export, so use curly braces around render.

3. Final Answer:

   import { render } from '@testing-library/react'; -> Option A

4. Quick Check:

   Named import from '@testing-library/react' = B [OK]

Hint: Use named import from '@testing-library/react' for render [OK]

Common Mistakes:

• Using default import instead of named import
• Importing from wrong package like 'react-dom' or 'next/testing'
• Missing curly braces around render

3. Given this test code snippet, what will screen.getByText('Hello World') return?

import { render, screen } from '@testing-library/react';

function Greeting() {
  return <h1>Hello World</h1>;
}

test('renders greeting text', () => {
  render(<Greeting />);
  const element = screen.getByText('Hello World');
  return element;
});

medium

A. An error because screen is not defined

B. The <h1> element containing 'Hello World'

C. null because 'Hello World' is not found

D. An array of all elements with text 'Hello World'

Solution

1. Step 1: Understand what render and screen.getByText do

   render displays the component in a virtual DOM; screen.getByText finds the first element with matching text.

2. Step 2: Check the component output

   Greeting returns <h1>Hello World</h1>, so screen.getByText('Hello World') finds this <h1> element.

3. Final Answer:

   The <h1> element containing 'Hello World' -> Option B

4. Quick Check:

   getByText finds matching element = C [OK]

Hint: getByText returns the matching DOM element, not null or array [OK]

Common Mistakes:

• Thinking getByText returns null if found
• Confusing screen with undefined variable
• Assuming getByText returns multiple elements

4. Identify the error in this test code snippet:

import { render, screen, fireEvent } from '@testing-library/react';

function Button() {
  const [count, setCount] = React.useState(0);
  return <button onClick={() => setCount(count + 1)}>Clicked {count} times</button>;
}

test('increments count on click', () => {
  render(<Button />);
  const button = screen.getByRole('button');
  fireEvent.click(button);
  expect(button.textContent).toBe('Clicked 1 times');
});

medium

A. Expect statement should check button.innerHTML

B. Using fireEvent instead of userEvent

C. Incorrect role used in getByRole

D. Missing import of React from 'react'

Solution

1. Step 1: Check imports for React usage

   The component uses React.useState but React is not imported, causing a runtime error.

2. Step 2: Verify other parts

   fireEvent.click and getByRole('button') are correct usage; expect checks textContent correctly.

3. Final Answer:

   Missing import of React from 'react' -> Option D

4. Quick Check:

   React must be imported to use React.useState = A [OK]

Hint: Always import React when using React APIs like useState [OK]

Common Mistakes:

• Assuming fireEvent is wrong instead of userEvent
• Thinking getByRole('button') is incorrect
• Checking innerHTML instead of textContent

5. You want to test a Next.js component that fetches data on mount and displays it. Which approach correctly integrates React Testing Library with async data fetching?

import { render, screen, waitFor } from '@testing-library/react';
import React from 'react';

function DataDisplay() {
  const [data, setData] = React.useState(null);
  React.useEffect(() => {
    fetch('/api/data').then(res => res.json()).then(setData);
  }, []);
  if (!data) return <div>Loading...</div>;
  return <div>Data: {data.value}</div>;
}

test('shows fetched data', async () => {
  global.fetch = jest.fn(() => Promise.resolve({
    json: () => Promise.resolve({ value: 'Hello' })
  }));
  render(<DataDisplay />);
  await waitFor(() => screen.getByText('Data: Hello'));
  expect(screen.getByText('Data: Hello')).toBeInTheDocument();
});

hard

A. Correctly mocks fetch and waits for async update with waitFor

B. Should use fireEvent to trigger fetch manually

C. Missing cleanup of fetch mock after test

D. Should use getByText without waitFor for async content

Solution

1. Step 1: Check mocking of fetch

   The test mocks global.fetch to return a resolved promise with expected data, which is correct for simulating API calls.

2. Step 2: Verify waiting for async UI update

   Using waitFor to wait until the text 'Data: Hello' appears is the right way to handle async rendering in tests.

3. Final Answer:

   Correctly mocks fetch and waits for async update with waitFor -> Option A

4. Quick Check:

   Mock fetch + waitFor async UI = A [OK]

Hint: Mock fetch and use waitFor to handle async UI updates [OK]

Common Mistakes:

• Trying to trigger fetch with fireEvent instead of mocking
• Not waiting for async content before assertions
• Forgetting to cleanup mocks (not critical here)