Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

cypress-react-unit-test

Package Overview
Dependencies
Maintainers
1
Versions
109
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

cypress-react-unit-test

Unit test React components using Cypress

  • 4.14.1
  • Source
  • npm
  • Socket score

Version published
Weekly downloads
1.5K
decreased by-10.33%
Maintainers
1
Weekly downloads
 
Created
Source

cypress-react-unit-test CircleCI Cypress.io tests renovate-app badge

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

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

Survey

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 🙏

TLDR

  • 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

  • How is this different from Enzyme or RTL? It is similar in functionality BUT runs the component in the real browser with full power of Cypress E2E test runner: live GUI, full API, screen recording, CI support, cross-platform, and visual testing. Ohh, and the code coverage is built-in!
  • If you like using @testing-library/react, you can use @testing-library/cypress for the same findBy, queryBy commands, see one of the examples in the list below
  • Read My Vision for Component Tests in Cypress

Comparison

FeatureJest / Enzyme / RTLCypress + cypress-react-unit-test
Test runs in real browser
Supports shallow mount
Supports full mount
Test speed🏎as fast as the app works in the browser
Test can use additional pluginsmaybeuse any Cypress plugin
Test can interact with componentsynthetic limited APIuse any Cypress command
Test can be debuggedvia terminal and Node debuggeruse browser DevTools
Built-in time traveling debuggerCypress time traveling debugger
Re-run tests on file or test change
Test output on CIterminalterminal, screenshots, videos
Tests can be run in parallel✅ via parallelization
Test against interfaceif using @testing-library/react✅ and can use @testing-library/cypress
Spying and stubbing methodsJest mocksSinon library
Stubbing imports
Stubbing clock
Code coverage

If you are coming from Jest + RTL world, read Test The Interface Not The Implementation.

If you are coming from Enzyme world, check out the enzyme example.

Blog posts

Known problems

See issues labeled v4

Install

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
require('cypress-react-unit-test/support')
  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 (even after ejecting) 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"
}

API

  • mount is the most important function, allows to mount a given React component as a mini web application and interact with it using Cypress commands
  • createMount factory function that creates new mount function with default options
  • unmount removes previously mounted component, mostly useful to test how the component cleans up after itself
  • mountHook mounts a given React Hook in a test component for full testing, see hooks example

Examples

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 of examples showing various testing scenarios.

Basic examples

SpecDescription
aliasRetrieve mounted component by its name or alias
alert-spec.jsComponent tries to use window.alert
counter-set-stateCounter component that uses this.state
counter-use-hooksCounter component that uses useState hook
document-specChecks document dimensions from the component
enzymeSeveral specs showing how to recreate Enzyme's setProps, setState, and setContext methods.
emotion-spec.jsConfirms the component is using @emotion/core and styles are set
error-boundary-spec.jsChecks if an error boundary component works
pure-component-spec.jsTests stateless component
stateless-spec.jsPasses Cypress stub to the component, confirms the component calls it on click
window-spec.jsIn the component test, the spec window and the application's window where the component is running should be the same object
cssShows that component with import './Button.css' works
css modulesShows that component that using css modules styles works
networkConfirms we can use cy.route to stub / spy on component's network calls
no-visitComponent specs cannot call cy.visit
re-renderChecking how the component re-renders when its props change
react-book-by-chris-noringCopied test examples from React Book and adapted for Cypress component tests
react-tutorialTests from official ReactJS tutorial copied and adapted for Cypress component tests
stub-exampleUses cy.stub as component props
stylesAdd extra styles to the component during testing using style, cssFile or stylesheets mount options
toggle-exampleTesting a toggle component using Cypress DOM commands
typescriptA spec written in TypeScript
unmountVerifies the component's behavior when it is unmounted from the DOM
use-lodash-fpImports and tests methods from lodash/fp dependency
styled-componentsTest components that use styled-components

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

Advanced examples

SpecDescription
api-testMix REST api tests that use cy-api with component tests
app-action-exampleApp actions against components
contextConfirms components that use React context feature work
custom-commandWraps mount in a custom command for convenience
forward-refTests a component that uses a forward ref feature
hooksTests several components that use React Hooks like useState, useCallback
lazy-loadedConfirms components that use React.lazy and dynamic imports work
material-ui-exampleLarge components demos from Material UI
mock-fetchTest stubs window.fetch used by component in useEffect hook
mocking-axiosStubbing methods from a 3rd party component like axios
mocking-componentReplaced a child component with dummy component during test
mocking-importsStub a named ES6 import in various situations
react-router-v6Example testing a React Router v6. Both browser and in memory routers
renderlessTesting a component that does not need to render itself into the DOM
set-timeout-exampleControl the clock with cy.tick and test loading components that use setTimeout
test-retriesThis component is compatible with Cypress Test Retries
testing-lib-exampleA spec adopted from @testing-library/react that uses @testing-library/cypress
timersTesting components that set timers, adopted from ReactJS Testing recipes
tutorialA few tests adopted from ReactJS Tutorial, including Tic-Tac-Toe game
use-local-storageUse hooks to load and save items into localStorage
portalComponent test for ReactDOM.createPortal feature
radioactive-stateTesting components that use radioactive-state library
react-bootstrapConfirms react-bootstrap components are working
select React componentUses cypress-react-selector to find DOM elements using React component name and state values
lazy-loadedUses multiple chunks and async components with React.lazy + React.Suspense.
i18nUsesreact-i18next for localizaiton.
framer-motionUses framer motion for javascript-based animation.

Full examples

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

Folder NameDescription
a11yTesting components' accessibility using cypress-axe
react-scriptsA project using react-scripts with component tests in src folder, including the .env files demo.
react-scripts-folderA project using react-scripts with component tests in cypress/component
tailwindTesting styles built using Tailwind CSS
sass-and-tsExample with Webpack, Sass and TypeScript
snapshotsComponent HTML and JSON snapshots using cypress-plugin-snapshots
visual-sudokuVisual 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-percyVisual testing for components using 3rd party service Percy.io
visual-testing-with-happoVisual testing for components using 3rd party service Happo
visual-testing-with-applitoolsVisual testing for components using 3rd party service Applitools.com
using-babelBundling specs and loaded source files using project's existing .babelrc file
webpack-fileLoad existing webpack.config.js file
webpack-optionsUsing 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.

RepoDescription
try-cra-with-unit-testHello world initialized with CRAv3
try-cra-app-typescriptHello world initialized with CRAv3 --typescript
react-todo-with-hooksModern web application using hooks
test-redux-examplesExample apps copies from official Redux repo and tested as components
test-react-hooks-animationsTesting React springs fun blob animation
test-mdx-exampleExample testing MDX components using Cypress
test-apolloComponent testing an application that uses Apollo GraphQL library
test-xstate-reactXState component testing using Cypress
test-react-router-v5A few tests of React Router v5
test-material-uiTesting Material UI components: date pickers, lists, autocomplete
test-d3-react-gaugeTesting React D3 gauges
storybook-code-coverageExample app where we get 100% code coverage easily with a single integration spec and a few component specs, replacing several tools
react-loading-skeletonOne to one Storybook tests for React skeleton components. Uses local .babelrc settings without Webpack config
test-swrComponent test for Zeit SWR hooks for remote data fetching
emoji-searchQuick component test for a fork of emoji-search
test-custom-error-boundaryPlay with a component that implements error boundary
Jscrambler-Webpack-ReactExample project with its own Webpack config file
bahmutov/integration-testsExample based on blog post React Integration Testing: Greater Coverage, Fewer Tests
mobx-react-typescript-boilerplateFork of the official Mobx example, shows clock control
bahmutov/test-react-hook-formTesting forms created using react-hook-form
bahmutov/react-with-rollupTesting a React application bundled with Rollup by using @bahmutov/cy-rollup preprocessor
bahmutov/testing-react-exampleDescribed in blog post Test React Component with cypress-react-unit-test Example
ejected-react-scripts-exampleUsing component testing after ejecting react-scripts
tic-tac-toeComponent and unit tests for Tic-Tac-Toe, read Tic-Tac-Toe Component Tests
react-hooks-file-uploadUpload a file from the component while stubbing the server
react-query-exampleQuick test example for components that use react-query with mock clock control

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

Options

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/styles.md for the full list of options.

const todo = {
  id: '123',
  title: 'Write more tests',
}
mount(<Todo todo={todo} />, {
  stylesheets: [
    'https://cdnjs.cloudflare.com/ajax/libs/bulma/0.7.2/css/bulma.css',
  ],
})
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. I explain how to write visual testing using open source tools in this blog post, video talk, and slides.

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"
}

Find full example in sass-and-ts folder.

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.

Missing code coverage

If you are using your custom Webpack, this plugin might be missing code coverage information because the code was not instrumented. We try to insert the babel-plugin-istanbul plugin automatically, but your bundling might not use Babel, or configure it differently, preventing plugin insertion. Please let us know by opening an issue with full reproducible details.

See related issue #141. You can also debug the plugin's behavior by running it with DEBUG environment variable, see #debugging section.

Next.js projects not supported

Currently, this project cannot find Webpack settings used by Next.js, thus it cannot bundle specs and application code correctly. Keep an eye on #155

Gatsby.js projects not supported

Currently, this project cannot find Webpack settings used by Gatsby.js, thus it cannot bundle specs and application code correctly. Keep an eye on #307

Chat

We have a chat workspace at https://component-testing.slack.com/, you are welcome to join us.

Development

See docs/development.md

Debugging

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

DEBUG=cypress-react-unit-test

Because finding and modifying Webpack settings while running this plugin is done by find-webpack module, you might want to enable its debug messages too.

DEBUG=cypress-react-unit-test,find-webpack

Migration guide

From v3 to v4

The old v3 main 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')

Same feature for unit testing components from other frameworks using Cypress

Keywords

FAQs

Package last updated on 17 Sep 2020

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc