如何用React Testing Library与Jest测试父组件向子组件传递Props?
React 组件 Props 传递校验测试方案
针对需要验证父组件向子组件正确传参的需求,最适合新手落地的实现方式是基于 React Testing Library(React 官方推荐的测试工具集)的 Mock 校验法,不需要深入了解复杂的组件渲染逻辑,核心逻辑是把所有非目标组件做隔离 Mock,直接捕获子组件收到的入参做对比。
实现步骤
1. 前置依赖准备
常规 React 项目(基于 Vite、Create React App、Next.js 初始化的项目)默认已经集成了 React Testing Library 和 Jest 测试框架,不需要额外安装复杂依赖。
2. 测试文件初始化与依赖Mock
在和 QueryPanelRouters 组件同目录下新建 QueryPanelRouters.test.jsx 测试文件,先把所有组件依赖替换成可捕获入参的 Mock 组件,避免真实子组件的内部逻辑干扰测试:
import { render } from '@testing-library/react' import QueryPanelRouters from './QueryPanelRouters' // Mock所有外部依赖的子组件,返回空节点,同时把接收到的props存在mock函数上方便校验 jest.mock('LookingGlass/common/components', () => ({ SubsectionTitle: jest.fn(() => <div data-testid="mock-subsection-title" />) })) jest.mock('LookingGlass/app/components/SelectorIPVersion', () => ({ __esModule: true, default: jest.fn(() => <div data-testid="mock-selector-ip" />) })) jest.mock('LookingGlass/app/components/SelectorNetwork', () => ({ __esModule: true, default: jest.fn(() => <div data-testid="mock-selector-network" />) })) jest.mock('LookingGlass/app/components/SelectorRouter', () => ({ __esModule: true, default: jest.fn(() => <div data-testid="mock-selector-router" />) })) // Mock静态常量 jest.mock('LookingGlass/constants', () => ({ QueryPanelRouters: { title: '路由器查询面板' } })) // 引入mock后的组件,方便后续拿到mock函数的入参 import { SubsectionTitle } from 'LookingGlass/common/components' import SelectorIPVersion from 'LookingGlass/app/components/SelectorIPVersion' import SelectorNetwork from 'LookingGlass/app/components/SelectorNetwork' import SelectorRouter from 'LookingGlass/app/components/SelectorRouter'
3. 编写测试用例覆盖所有传参分支
每个用例的核心逻辑非常简单:构造目标组件的入参 → 渲染组件 → 读取 Mock 子组件捕获到的入参 → 和预期值做断言对比:
describe('QueryPanelRouters Props 传递校验', () => { // 每个测试跑完把mock函数的入参清空,避免测试间的污染 beforeEach(() => { jest.clearAllMocks() }) test('正确向 SubsectionTitle 传递标题文本', () => { const mockProps = { env: { routers: [] }, query: { ipVersion: 4, network: 'test-net', router: 'r1' } } render(<QueryPanelRouters {...mockProps} />) expect(SubsectionTitle).toHaveBeenCalledWith( expect.objectContaining({ text: '路由器查询面板' }), expect.anything() ) }) test('正确向 SelectorIPVersion 传递计算后的props', () => { const mockQuery = { ipVersion: 6 } const mockProps = { env: { routers: [] }, query: mockQuery, isLoading: true } render(<QueryPanelRouters {...mockProps} />) const receivedProps = SelectorIPVersion.mock.calls[0][0] expect(receivedProps.checkedVersion).toBe(6) expect(receivedProps.disabled).toBe(true) expect(typeof receivedProps.onChange).toBe('function') }) test('正确向 SelectorNetwork 传递计算后的props', () => { const mockQuery = { network: 'network-01' } const mockProps = { env: { routers: [] }, query: mockQuery, isLoading: false } render(<QueryPanelRouters {...mockProps} />) const receivedProps = SelectorNetwork.mock.calls[0][0] expect(receivedProps.selectedNetwork).toBe('network-01') expect(receivedProps.disabled).toBe(false) expect(typeof receivedProps.onChange).toBe('function') }) test('正确向 SelectorRouter 传递过滤后的路由器列表', () => { const mockEnv = { routers: [ { id: 'r1', network: 'net-A' }, { id: 'r2', network: 'net-B' } ] } const mockQuery = { network: 'net-A', router: 'r1' } const mockProps = { env: mockEnv, query: mockQuery, isLoading: false } render(<QueryPanelRouters {...mockProps} />) const receivedProps = SelectorRouter.mock.calls[0][0] expect(receivedProps.routers).toEqual([{ id: 'r1', network: 'net-A' }]) expect(receivedProps.selectedRouter).toBe('r1') expect(receivedProps.disabled).toBe(false) }) test('env.routers不存在时,给SelectorRouter传空数组', () => { const mockProps = { env: {}, query: { network: 'net-A', router: 'r1' } } render(<QueryPanelRouters {...mockProps} />) const receivedProps = SelectorRouter.mock.calls[0][0] expect(receivedProps.routers).toEqual([]) }) })
4. 补充回调函数逻辑校验
对于传递下去的 onChange 类回调函数,不需要模拟点击交互,直接拿函数引用手动触发,验证回调触发后是否正确修改了传入的 query 对象即可:
test('SelectorIPVersion的onChange触发后会正确修改query对象', () => { const mockQuery = { ipVersion: 4 } const mockProps = { env: {}, query: mockQuery } render(<QueryPanelRouters {...mockProps} />) // 拿到传下去的onChange方法 const ipChangeHandler = SelectorIPVersion.mock.calls[0][0].onChange // 手动触发方法,传一个新版本值 ipChangeHandler(6) // 校验原query对象被正确修改 expect(mockQuery.ipVersion).toBe(6) })
新手避坑提示
- 不要在测试中渲染真实的子组件UI,只需要把组件替换成返回空节点的Mock就能拿到传入的props,测试稳定性会高很多,不会因为子组件的UI改动导致测试失败
- 每个测试用例执行前,调用
jest.clearAllMocks()清空Mock函数的历史调用记录,避免不同用例之间的参数污染 - 不要通过查找DOM节点反推传参是否正确,直接读取Mock函数的入参校验,就算父组件的DOM结构调整,只要传参逻辑正确,测试就不会报错
内容的提问来源于stack exchange,提问作者Jaimini Chothwani
相关产品推荐
相关产品推荐

