Skip to content
Unit test React components using Cypress
JavaScript TypeScript CSS HTML
Branch: master
Clone or download


Type Name Latest commit message Commit time
Failed to load latest commit information.
.vscode limit renovate dependencies to just ours Apr 29, 2020
cypress rename file May 19, 2020
docs remove warning that is obsolete May 20, 2020
examples Add babelrc example (#243) May 24, 2020
images clarify styles a little May 15, 2020
lib fix: add delay to let hooks run (#201) May 12, 2020
plugins fix: use default webpack options (#189) May 8, 2020
src feat: support testing React components that use hooks Apr 28, 2020
support feat: support testing React components that use hooks Apr 28, 2020
.gitignore update screenshots using non-interactive mode May 16, 2020
.npmrc Cy 3.1.0, package lock Aug 16, 2018
.prettierrc.json feat: support testing React components that use hooks Apr 28, 2020 Add babelrc example (#243) May 24, 2020
babel.config.js feat: support testing React components that use hooks Apr 28, 2020
circle.yml Add babelrc example (#243) May 24, 2020
cypress.json feat: support testing React components that use hooks Apr 28, 2020
index.html feat: support testing React components that use hooks Apr 28, 2020
package-lock.json Update dependency semantic-release to v17.0.8 May 25, 2020
package.json Update dependency semantic-release to v17.0.8 May 25, 2020
renovate.json fix renovate config May 21, 2020
tsconfig.json feat: support testing React components that use hooks Apr 28, 2020
webpack.config.js feat: support testing React components that use hooks Apr 28, 2020

cypress-react-unit-test CircleCI tests renovate-app badge

A little helper to unit test React components in the open source E2E test runner v4.5.0+

Jump to: Comparison, Install, Examples: basic, advanced, full, external, Style options, Code coverage, Visual testing, Common problems


Hi there! We are trying to collect feedback from Cypress users who need component testing. Answer a few questions in this survey about component testing to help us 🙏


  • What is this? This package allows you to use Cypress test runner to unit test your React components with zero effort. Here is a typical component testing, notice there is not external URL shown, since it is mounting the component directly.

Example component test


Feature Jest / Enzyme / RTL Cypress + cypress-react-unit-test
Test runs in real browser
Uses full mount
Test speed 🏎 as fast as the app works in the browser
Test can use additional plugins maybe use any Cypress plugin
Test can interact with component synthetic limited API use any Cypress command
Test can be debugged via terminal and Node debugger use browser DevTools
Built-in time traveling debugger Cypress time traveling debugger
Re-run tests on file or test change
Test output on CI terminal terminal, screenshots, videos
Tests can be run in parallel via parallelization
Test against interface if using @testing-library/react and can use @testing-library/cypress
Spying and mocking Jest mocks Sinon library
Code coverage

Known problems

See issues labeled v4


Requires Node version 8 or above.

npm install --save-dev cypress cypress-react-unit-test
  1. Include this plugin from your project's cypress/support/index.js
  1. Tell Cypress how your React application is transpiled or bundled (using Webpack), so Cypress can load your components. For example, if you use react-scripts do:
// cypress/plugins/index.js
module.exports = (on, config) => {
  require('cypress-react-unit-test/plugins/react-scripts')(on, config)
  // IMPORTANT to return the config object
  // with the any changed environment variables
  return config

See Recipes for more examples.

  1. ⚠️ Turn the experimental component support on in your cypress.json. You can also specify where component spec files are located. For example, to have them located in src folder use:
  "experimentalComponentTesting": true,
  "componentFolder": "src"


import React from 'react'
import { mount } from 'cypress-react-unit-test'
import { HelloWorld } from './hello-world.jsx'
describe('HelloWorld component', () => {
  it('works', () => {
    mount(<HelloWorld />)
    // now use standard Cypress commands
    cy.contains('Hello World!').should('be.visible')

Look at the examples in cypress/component folder. Here is the list in progress

Basic examples

Spec Description
alert-spec.js Component tries to use window.alert
counter-set-state Counter component that uses this.state
counter-use-hooks Counter component that uses useState hook
emotion-spec.js Confirms the component is using @emotion/core and styles are set
error-boundary-spec.js Checks if an error boundary component works
pure-component-spec.js Tests stateless component
stateless-spec.js Passes Cypress stub to the component, confirms the component calls it on click
window-spec.js In the component test, the spec window and the application's window where the component is running should be the same object
css Shows that component with import './Button.css' works
network Confirms we can use cy.route to stub / spy on component's network calls
react-book-by-chris-noring Copied test examples from React Book and adapted for Cypress component tests
react-tutorial Tests from official ReactJS tutorial copied and adapted for Cypress component tests
stub-example Uses cy.stub as component props
styles Add extra styles to the component during testing using style, cssFile or stylesheets mount options
toggle-example Testing a toggle component using Cypress DOM commands
typescript A spec written in TypeScript
unmount Verifies the component's behavior when it is unmounted from the DOM
use-lodash-fp Imports and tests methods from lodash/fp dependency
document-spec Checks document dimensions from the component
styled-components Test components that use styled-components

plus a few smaller sanity specs in cypress/component/basic folder.

Advanced examples

Spec Description
app-action-example App actions against components
context Confirms components that use React context feature work
custom-command Wraps mount in a custom command for convenience
forward-ref Tests a component that uses a forward ref feature
hooks Tests several components that use React Hooks like useState, useCallback
lazy-loaded Confirms components that use React.lazy and dynamic imports work
material-ui-example Large components demos from Material UI
mock-fetch Test stubs window.fetch used by component in useEffect hook
mocking-component Replaced a child component with dummy component during test
mocking-imports Stub a named ES6 import using plugin-transform-modules-commonjs with loose: true when transpiled
react-router-v6 Example testing a React Router v6
renderless Testing a component that does not need to render itself into the DOM
set-timeout-example Control the clock with cy.tick and test loading components that use setTimeout
testing-lib-example A spec adopted from @testing-library/react that uses @testing-library/cypress
timers Testing components that set timers, adopted from ReactJS Testing recipes
tutorial A few tests adopted from ReactJS Tutorial, including Tic-Tac-Toe game
portal Component test for ReactDOM.createPortal feature
react-bootstrap Confirms react-bootstrap components are working
select React component Uses cypress-react-selector to find DOM elements using React component name and state values

Full examples

We have several subfolders in examples folder that have complete projects with just their dependencies installed in the root folder.

Folder Name Description
react-scripts A project using react-scripts with component tests in src folder
react-scripts-folder A project using react-scripts with component tests in cypress/component
tailwind Testing styles built using Tailwind CSS
visual-sudoku Visual testing for components using open source plugin cypress-image-snapshot. For larger example with an hour long list of explanation videos, see bahmutov/sudoku.
visual-testing-with-percy Visual testing for components using 3rd party service
visual-testing-with-happo Visual testing for components using 3rd party service Happo
using-babel Bundling specs and loaded source files using project's existing .babelrc file
webpack-options Using the default Webpack options from @cypress/webpack-preprocessor to transpile JSX specs

External examples

This way of component testing has been verified in a number of forked 3rd party projects.

Repo Description
try-cra-with-unit-test Hello world initialized with CRAv3
try-cra-app-typescript Hello world initialized with CRAv3 --typescript
react-todo-with-hooks Modern web application using hooks
test-redux-examples Example apps copies from official Redux repo and tested as components
test-react-hooks-animations Testing React springs fun blob animation
test-mdx-example Example testing MDX components using Cypress
test-apollo Component testing an application that uses Apollo GraphQL library
test-xstate-react XState component testing using Cypress
test-react-router-v5 A few tests of React Router v5
test-material-ui Testing Material UI components: date pickers, lists, autocomplete
test-d3-react-gauge Testing React D3 gauges
storybook-code-coverage Example app where we get 100% code coverage easily with a single integration spec and a few component specs, replacing several tools
react-loading-skeleton One to one Storybook tests for React skeleton components. Uses local .babelrc settings without Webpack config
test-swr Component test for Zeit SWR hooks for remote data fetching
emoji-search Quick component test for a fork of emoji-search
test-custom-error-boundary Play with a component that implements error boundary
Jscrambler-Webpack-React Example project with its own Webpack config file
bahmutov/integration-tests Example based on blog post React Integration Testing: Greater Coverage, Fewer Tests
mobx-react-typescript-boilerplate Fork of the official Mobx example, shows clock control
bahmutov/test-react-hook-form Testing forms created using react-hook-form
bahmutov/react-with-rollup Testing a React application bundled with Rollup by using @bahmutov/cy-rollup preprocessor

To find more examples, see GitHub topic cypress-react-unit-test-example


In most cases, the component already imports its own styles, thus it looks "right" during the test. If you need another CSS, the simplest way is to import it from the spec file:

// src/Footer.spec.js
import './styles/main.css'
import Footer from './Footer'
it('looks right', () => {
  // styles are applied
  mount(<Footer />)

Extra styles

You can pass additional styles, css files and external stylesheets to load, see docs/ for the full list of options.

const todo = {
  id: '123',
  title: 'Write more tests',
mount(<Todo todo={todo} />, {
  stylesheets: [
Additional configuration If your React and React DOM libraries are installed in non-standard paths (think monorepo scenario), you can tell this plugin where to find them. In `cypress.json` specify paths like this:
  "env": {
    "cypress-react-unit-test": {
      "react": "node_modules/react/umd/react.development.js",
      "react-dom": "node_modules/react-dom/umd/react-dom.development.js"

Code coverage

If you are using plugins/cra-v3 it instruments the code on the fly using babel-plugin-istanbul and generates report using dependency cypress-io/code-coverage (included). If you want to disable code coverage instrumentation and reporting, use --env coverage=false or CYPRESS_coverage=false or set in your cypress.json file

  "env": {
    "coverage": false

Visual testing

You can use any Cypress Visual Testing plugin to perform visual testing from the component tests. This repo has several example projects, see visual-sudoku, visual-testing-with-percy, visual-testing-with-happo, and visual-testing-with-applitools.

For a larger Do-It-Yourself example with an hour long list of explanation videos, see bahmutov/sudoku repository. There you can also find an example of testing responsive design, as shown in this video.

Common problems

Node Sass

When using Node Sass styles, tell Cypress to use the system NodeJS rather than its bundled version. In cypress.json set option:

  "nodeVersion": "system"
Slow bundling

When you bundle spec file, you are now bundling React, Read DOM and other libraries, which is might be slow. For now, you can disable inline source maps by adding to your Webpack config settings (if available) the following:

const webpackOptions = {
  devtool: false,

Keep your eye on issue #156 for more information.


See docs/


You can see verbose logs from this plugin by running with environment variable


Migration guide

From v3 to v4

The old v3 master branch is available as branch v3

  • the cy.mount is now simply import { mount } from 'cypress-react-unit-test'
  • the support file is simply require('cypress-react-unit-test/support')

Related tools

Same feature for unit testing components from other frameworks using Cypress

You can’t perform that action at this time.