Testing client components in NextJS - Mini Project: Build & Apply

Testing Client Components in Next.js

📖 Scenario: You are building a simple Next.js client component that shows a counter with increment and decrement buttons. You want to write tests to check that the buttons update the counter correctly.

🎯 Goal: Build a client component with a counter and two buttons, then write tests to verify the counter increments and decrements as expected.

📋 What You'll Learn

Create a client component with a counter state starting at 0

Add two buttons labeled 'Increment' and 'Decrement'

Write a test to check the initial counter value is 0

Write tests to check clicking 'Increment' increases the counter by 1

Write tests to check clicking 'Decrement' decreases the counter by 1

💡 Why This Matters

🌍 Real World

Testing client components ensures your interactive UI works correctly before users see it. This prevents bugs and improves user experience.

💼 Career

Front-end developers often write tests for React or Next.js components to maintain code quality and catch errors early in development.

1

Create the Counter Client Component

Create a file Counter.jsx with a React client component called Counter. Inside it, use useState to create a state variable count initialized to 0. Render a <div> that displays the text Count: {count}.

NextJS

// Your code here

Hint

Remember to add "use client"; at the top to make it a client component.

2

Add Increment and Decrement Buttons

In Counter.jsx, add two <button> elements inside the <div>. One button should have the text Increment and call setCount(count + 1) on click. The other button should have the text Decrement and call setCount(count - 1) on click.

NextJS

"use client";

import { useState } from "react";

export default function Counter() {
  const [count, setCount] = useState(0);
  return (
    
      Count: {count}
      {/* Add Increment and Decrement buttons here */}
    
  );
}

Hint

Use onClick handlers on buttons to update the count state.

3

Write a Test for Initial Counter Value

Create a test file Counter.test.jsx. Import render and screen from @testing-library/react and import the Counter component. Write a test named "shows initial count as 0" that renders <Counter /> and checks that the text Count: 0 is in the document.

NextJS

// Your test code here

Hint

Use screen.getByText to find the text and expect(...).toBeInTheDocument() to check it exists.

4

Write Tests for Increment and Decrement Buttons

In Counter.test.jsx, add two tests. The first test named "increments count when Increment button clicked" should render <Counter />, click the Increment button using screen.getByText and fireEvent.click, then check the text updates to Count: 1. The second test named "decrements count when Decrement button clicked" should do the same but click the Decrement button and check the text updates to Count: -1.

NextJS

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

// Add tests for Increment and Decrement buttons here

Hint

Use fireEvent.click to simulate button clicks and check the updated text.

Practice

1. What is the main purpose of testing client components in Next.js?

easy

A. To catch UI bugs early by simulating user interactions

B. To improve server response time

C. To optimize database queries

D. To deploy the app faster

Solution

1. Step 1: Understand client component testing goal

   Testing client components focuses on the user interface and user actions to find bugs early.

2. Step 2: Compare options with testing goals

   Only To catch UI bugs early by simulating user interactions matches the goal of catching UI bugs by simulating user interactions.

3. Final Answer:

   To catch UI bugs early by simulating user interactions -> Option A

4. Quick Check:

   Testing client components = catch UI bugs early [OK]

Hint: Focus on UI and user actions for client component tests [OK]

Common Mistakes:

• Confusing client testing with server optimization
• Thinking testing speeds up deployment
• Mixing database concerns with UI testing

2. Which of the following is the correct way to import React Testing Library's render function in a Next.js client component test?

easy

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

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

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

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

Solution

1. Step 1: Identify correct package for render

   React Testing Library's render function is imported from '@testing-library/react'.

2. Step 2: Check import syntax

   import { render } from '@testing-library/react'; uses correct named import syntax and package name.

3. Final Answer:

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

4. Quick Check:

   Render import = '@testing-library/react' [OK]

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

Common Mistakes:

• Using default import instead of named import
• Importing from wrong package like 'next/testing'
• Confusing 'react-dom' with testing library

3. Given this test code for a Next.js client component:

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

test('renders button with label', () => {
  render(<Button label="Click me" />);
  const btn = screen.getByRole('button');
  expect(btn.textContent).toBe('Click me');
});

What will this test check?

medium

A. That the Button component does not render anything

B. That the Button component throws an error

C. That the Button component renders a button element with text 'Click me'

D. That the Button component renders a div with text 'Click me'

Solution

1. Step 1: Analyze render and query

   The test renders Button with label 'Click me' and queries for a button role element.

2. Step 2: Check assertion

   The test expects the button's text content to be exactly 'Click me'.

3. Final Answer:

   That the Button component renders a button element with text 'Click me' -> Option C

4. Quick Check:

   Button renders button with label 'Click me' [OK]

Hint: Look for role queries and text assertions to find tested output [OK]

Common Mistakes:

• Assuming error or no render without evidence
• Confusing element type (button vs div)
• Ignoring the text content check

4. Consider this test code snippet:

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

test('increments count on button click', () => {
  render(<Counter />);
  const btn = screen.getByRole('button');
  btn.click();
  expect(screen.getByText('Count: 1')).toBeInTheDocument();
});

What is the main issue with this test?

medium

A. Using getByRole instead of queryByRole

B. Missing import of React in the test file

C. Expecting wrong text content 'Count: 1'

D. Using btn.click() instead of userEvent.click(btn) to simulate user action

Solution

1. Step 1: Identify how click is simulated

   The test uses btn.click(), which is a DOM method but does not simulate real user events fully.

2. Step 2: Recognize recommended practice

   React Testing Library recommends using userEvent.click(btn) for realistic user interaction simulation.

3. Final Answer:

   Using btn.click() instead of userEvent.click(btn) to simulate user action -> Option D

4. Quick Check:

   Use userEvent.click for user actions [OK]

Hint: Use userEvent.click, not btn.click, for user simulation [OK]

Common Mistakes:

• Forgetting to import userEvent
• Assuming btn.click triggers React events fully
• Confusing getByRole with queryByRole

5. You want to test a Next.js client component that conditionally renders a message only after a button click. Which approach correctly tests this behavior?

hard

A. Render the component and immediately check if the message is in the document

B. Render the component, use userEvent.click on the button, then check if the message appears

C. Use screen.getByText before clicking the button to find the message

D. Test only the button rendering without clicking it

Solution

1. Step 1: Understand conditional rendering on user action

   The message appears only after clicking the button, so the test must simulate that click.

2. Step 2: Verify test steps

   Render component, simulate userEvent.click on button, then check for message presence is correct.

3. Final Answer:

   Render the component, use userEvent.click on the button, then check if the message appears -> Option B

4. Quick Check:

   Simulate click before checking conditional content [OK]

Hint: Click button first, then check for conditional content [OK]

Common Mistakes:

• Checking message before user action
• Not simulating user click properly
• Ignoring conditional rendering logic