Testing React Hooks With Enzyme and React Testing Library
Apr 14, 2025 am 09:23 AMBuilding robust React applications with hooks requires rigorous testing. This tutorial demonstrates how to effectively test React hooks using Enzyme and React Testing Library, leveraging a to-do application example. We'll cover key testing scenarios and best practices to ensure bug-free code.
This guide assumes familiarity with Jest and React testing fundamentals. If you're new to Enzyme, consider reviewing its integration with Jest in React applications before proceeding.
Testing Scenarios
Our to-do component will be tested against these scenarios:
- Component Rendering: Verify the component successfully renders.
- Initial To-Do Display: Confirm the initial to-do items are displayed correctly.
- Adding a New To-Do: Test the functionality of adding a new to-do item.
- Deleting a To-Do: Verify the ability to remove a to-do item.
Here's the to-do component code:
import React, { useState, useRef } from "react"; const Todo = () => { const [todos, setTodos] = useState([ { id: 1, item: "Fix bugs" }, { id: 2, item: "Take out the trash" } ]); const todoRef = useRef(); const removeTodo = id => { setTodos(todos.filter(todo => todo.id !== id)); }; const addTodo = data => { let id = todos.length 1; setTodos([ ...todos, { id, item: data } ]); }; const handleNewTodo = e => { e.preventDefault(); const item = todoRef.current; addTodo(item.value); item.value = ""; }; return ( <div classname="container"> {/* Corrected classname to className */} <div classname="row"> {/* Corrected classname to className */} <div classname="col-md-6"> {/* Corrected classname to className */} <h2>Add Todo</h2> </div> </div> <div classname="row"> {/* Corrected classname to className */} <div classname="col-md-6"> {/* Corrected classname to className */} <form onsubmit="{handleNewTodo}"> {/* Added form tag */} <input type="text" ref="{todoRef}" data-testid="input"> {/* Added data-testid */} <button type="submit" data-testid="add-button">Add Task</button> {/* Added data-testid */} </form> </div> </div> <div classname="row todo-list"> {/* Corrected classname to className */} <div classname="col-md-6"> {/* Corrected classname to className */} <h3>Lists</h3> {!todos.length ? ( <div classname="no-task">No task!</div> ) : ( <ul data-testid="todos"> {/* Added data-testid */} {todos.map(todo => { return ( <li key="{todo.id}"> {/* Corrected key value */} <div> {todo.item} <button data-testid="delete-button" onclick="{()"> removeTodo(todo.id)}>X</button> {/* Added data-testid and onClick */} </div> </li> ); })} </ul> )} </div> </div> </div> ); }; export default Todo;
Note: classname
attributes have been corrected to className
in the above code. Also, data-testid
attributes have been added for easier testing with React Testing Library.
Testing with Enzyme
-
Installation:
npm install --save-dev enzyme enzyme-adapter-react-16
- Enzyme Configuration (setupTests.js):
import Enzyme from "enzyme"; import Adapter from "enzyme-adapter-react-16"; Enzyme.configure({ adapter: new Adapter() });
- Tests (Todo.test.js):
import React from "react"; import { shallow, mount } from "enzyme"; import Todo from "../Todo"; describe("Todo", () => { it("renders", () => { shallow(<todo></todo>); }); it("displays initial to-dos", () => { const wrapper = mount(<todo></todo>); expect(wrapper.find("li")).toHaveLength(2); }); it("adds a new item", () => { const wrapper = mount(<todo></todo>); wrapper.find("input").instance().value = "Fix failing test"; wrapper.find('[type="submit"]').simulate("submit"); // Simulate submit, not click expect(wrapper.find("li")).toHaveLength(3); expect(wrapper.find("li").last().text()).toContain("Fix failing test"); // Improved assertion }); it("removes an item", () => { const wrapper = mount(<todo></todo>); wrapper.find('[data-testid="delete-button"]').first().simulate("click"); expect(wrapper.find("li")).toHaveLength(1); }); });
Testing with React Testing Library
-
Installation:
npm install --save-dev @testing-library/jest-dom @testing-library/react
- Tests (Todo.test.js):
import React from "react"; import { render, fireEvent, screen } from "@testing-library/react"; import Todo from "../Todo"; import "@testing-library/jest-dom"; describe("Todo", () => { it("displays initial to-dos", () => { render(<todo></todo>); expect(screen.getByTestId("todos").children.length).toBe(2); }); it("adds a new to-do", () => { render(<todo></todo>); fireEvent.change(screen.getByTestId("input"), { target: { value: "New Task" } }); fireEvent.click(screen.getByTestId("add-button")); expect(screen.getByTestId("todos").children.length).toBe(3); }); it("deletes a to-do", () => { render(<todo></todo>); fireEvent.click(screen.getAllByTestId("delete-button")[0]); expect(screen.getByTestId("todos").children.length).toBe(1); }); });
Remember to adjust file paths as needed for your project structure. This improved version provides more robust and maintainable tests. The use of data-testid
makes the tests more resilient to changes in the component's structure.
The above is the detailed content of Testing React Hooks With Enzyme and React Testing Library. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

CSS blocks page rendering because browsers view inline and external CSS as key resources by default, especially with imported stylesheets, header large amounts of inline CSS, and unoptimized media query styles. 1. Extract critical CSS and embed it into HTML; 2. Delay loading non-critical CSS through JavaScript; 3. Use media attributes to optimize loading such as print styles; 4. Compress and merge CSS to reduce requests. It is recommended to use tools to extract key CSS, combine rel="preload" asynchronous loading, and use media delayed loading reasonably to avoid excessive splitting and complex script control.

ThebestapproachforCSSdependsontheproject'sspecificneeds.Forlargerprojects,externalCSSisbetterduetomaintainabilityandreusability;forsmallerprojectsorsingle-pageapplications,internalCSSmightbemoresuitable.It'scrucialtobalanceprojectsize,performanceneed

No,CSSdoesnothavetobeinlowercase.However,usinglowercaseisrecommendedfor:1)Consistencyandreadability,2)Avoidingerrorsinrelatedtechnologies,3)Potentialperformancebenefits,and4)Improvedcollaborationwithinteams.

CSSismostlycase-insensitive,butURLsandfontfamilynamesarecase-sensitive.1)Propertiesandvalueslikecolor:red;arenotcase-sensitive.2)URLsmustmatchtheserver'scase,e.g.,/images/Logo.png.3)Fontfamilynameslike'OpenSans'mustbeexact.

Autoprefixer is a tool that automatically adds vendor prefixes to CSS attributes based on the target browser scope. 1. It solves the problem of manually maintaining prefixes with errors; 2. Work through the PostCSS plug-in form, parse CSS, analyze attributes that need to be prefixed, and generate code according to configuration; 3. The usage steps include installing plug-ins, setting browserslist, and enabling them in the build process; 4. Notes include not manually adding prefixes, keeping configuration updates, prefixes not all attributes, and it is recommended to use them with the preprocessor.

CSScounterscanautomaticallynumbersectionsandlists.1)Usecounter-resettoinitialize,counter-incrementtoincrease,andcounter()orcounters()todisplayvalues.2)CombinewithJavaScriptfordynamiccontenttoensureaccurateupdates.

In CSS, selector and attribute names are case-sensitive, while values, named colors, URLs, and custom attributes are case-sensitive. 1. The selector and attribute names are case-insensitive, such as background-color and background-Color are the same. 2. The hexadecimal color in the value is case-sensitive, but the named color is case-sensitive, such as red and Red is invalid. 3. URLs are case sensitive and may cause file loading problems. 4. Custom properties (variables) are case sensitive, and you need to pay attention to the consistency of case when using them.

CSSselectorsandpropertynamesarecase-insensitive,whilevaluescanbecase-sensitivedependingoncontext.1)Selectorslike'div'and'DIV'areequivalent.2)Propertiessuchas'background-color'and'BACKGROUND-COLOR'aretreatedthesame.3)Valueslikecolornamesarecase-insens
