Skip to main content
Cypress App

Cypress Component Testing

info
What you'll learn​
  • What makes Cypress Component Testing different from other component testing tools
  • How to set up Component Testing for React, Angular, Vue, or Svelte
  • How to write your first component test
  • How to run your component test

Cypress Component Testing mounts your components directly in a real browser — not a simulated DOM — so you test them exactly as they will behave for your users. Every component renders visually during the test run, and you can use browser DevTools to inspect, interact, and debug just as you would during development.

Why Cypress for Component Testing?​

Teams that adopt Cypress for component testing typically come looking for faster feedback on their UI components. They stay because Cypress brings together capabilities that would otherwise require assembling several separate tools:

  • See your component in action. Components render visually inside the Cypress App as each test runs. You can interact with them manually, inspect elements with DevTools, and use Time Travel to step back through exactly what happened at each point in the test — no guessing, no console.log archaeology.
  • Write less test boilerplate. Automatic waiting means your assertions run only after your component has rendered and updated. There is no need for waitFor, act(), or manual timeouts. You describe what should be true; Cypress waits until it is.
  • Use powerful testing primitives — built in. Spies and stubs to verify event handlers and isolate dependencies. Network interception to test how your component handles any server response without a running backend. Clock control to test time-sensitive logic instantly, without sleeping.
  • One project, one quality signal. Component tests live in the same Cypress project as your end-to-end tests. When connected to Cypress Cloud, results, flake patterns, and coverage data flow into a single view — so your team has clear evidence of quality at every layer before a release ships.

Catching a component bug in isolation is far cheaper than catching the same bug in an end-to-end test or, worse, in production. Teams that test components with Cypress close that feedback loop earlier, reduce the cost of fixing defects, and ship with more confidence.

Configuring Component Testing​

Assuming you've successfully installed Cypress and opened Cypress, now it's time to set up component testing.

The Cypress App will guide you through configuring your project.

Supported Frameworks​

Cypress currently has official mounting libraries for React, Angular, Vue, and Svelte and support for the following development servers and frameworks:

FrameworkUI LibraryBundler
React with ViteReact 18-19Vite 5-8
React with WebpackReact 18-19Webpack 5
Next.js 14-16React 18-19Webpack 5
Vue with ViteVue 3Vite 5-8
Vue with WebpackVue 3Webpack 5
AngularAngular 18-21Webpack 5
Svelte with Vite AlphaSvelte 5Vite 5-8
Svelte with Webpack AlphaSvelte 5Webpack 5

The following integrations are built and maintained by Cypress community members.

FrameworkUI LibraryBundler
Qwik CommunityQwikVite
Lit CommunityLitVite

Select Testing Type​

Whenever you run Cypress for the first time, the app will prompt you to set up either E2E Testing or Component Testing. Click on "Component Testing" to start the configuration wizard.

info

For more information on how to choose a testing type, we recommend this Testing Types Guide

Choose Component Testing

Choose Component Testing

Project Setup​

The Project Setup screen will automatically detect your framework and bundler. In this example we will use React and Vite. Click "Next Step" to continue.

React and Vite are automatically detected

React and Vite are automatically detected

Install Dependencies​

The next screen checks that all the required dependencies are installed. All the items should have green checkboxes on them, indicating everything is good, so click "Continue".

All necessary dependencies are installed

All necessary dependencies are installed

Config Files​

Next, Cypress generates all the necessary configuration files and gives you a list of all the changes it made to your project. Click "Continue".

The most important generated setting is component.devServer in cypress.config, which tells Cypress which UI framework and bundler to use. For most projects, the scaffolded values are all you need. See Dev Server and Bundler for how this works and how to customize it.

The Cypress launchpad will scaffold all of these files for you

The Cypress launchpad will scaffold all of these files for you

Choose A Browser​

After setting up component testing, you will be at the browser selection screen.

Pick the browser of your choice and click the "Start Component Testing" button to open the Cypress App.

Choose your browser

Choose your browser

Writing Your First Test​

At this point, your project is configured to use Cypress Component Testing. However, when the app appears, it won't find any specs because we haven't created any yet. Now we need write our first Component Test.

Cypress App UI with Create your first spec page with buttons for Create from component or Create new spec

Frameworks​

Cypress currently has official mounting libraries for React, Angular, Vue, and Svelte. In addition to our official framework support there are many community plugins such as Qwik and Lit.

Your First Component Test​

Though every framework is different and has its own unique nuances, in general, writing tests is very similar. Let's look at how a basic test is written for a StepperComponent.

Let's assume the Stepper Component consists of two buttons, one used to decrement the counter and one to increment it as well as a span tag that sits in the middle of the buttons to show the current value of the counter.

info

To see examples of the Stepper Component and its tests in each Framework, visit our Component Testing Quick Start Apps Repo

import React from 'react'
import Stepper from './Stepper'

describe('<Stepper />', () => {
  it('mounts', () => {
    // see: https://on.cypress.io/mounting-react
    cy.mount(<Stepper />)
  })
})

Test Explanation​

Let's break down the spec. First, we import the Stepper component. Then, we organize our tests using the functions describe and it, which allows us to group tests into sections by using method blocks. These are global functions provided by Cypress, which means you don't have to import them directly to use them. The top-level describe block will be the container for all our tests in a file, and each it represents an individual test. The describe function takes two parameters, the first of which is the name of the test suite, and the second is a function that will execute the tests.

We defined a test using the it function inside describe. The first parameter to it is a brief description of the spec, and the second parameter is a function that contains the test code. In our example above, we only have one test, but soon we'll see how we can add multiple it blocks inside of a describe for a series of tests.

info

The cy.mount() method will mount our component into the test app so we can begin running tests against it.

Now it's time to see the test in action.

Running the Test​

Switch back to the browser you opened for testing, and you should now see the Stepper Component in the spec list. Click it to see the spec execute.

Our first test verifies the component can mount in its default state without any errors. If there is a runtime error during test execution, the test will fail, and you will see a stack trace pointing to the source of the problem.

A basic test like the one above is an excellent way to start testing a component. Cypress renders your component in a real browser, and you can use all the techniques/tools you would normally during development, such as interacting with the component in the test runner, and using the browser dev tools to inspect and debug both your tests and the component's code.

Feel free to play around with the Stepper component by interacting with the increment and decrement buttons.

Now that the component is mounted, our next step is to test that the behavior of the component is correct.

Selectors & Assertions​

By default, the Stepper's counter is initialized to "0". We can override that value by specifying an initial count. Let's write a couple of tests that will verify both these states.

To do so, we will use a selector to access the span element that contains the counter, and then assert that the text value of the element is what we expect it to be.

There are various ways to select items from the DOM using Cypress. We will use cy.get(), which allows us to pass in a CSS-like selector.

After we "get" the element, we use the should assertion method to verify it has the correct text value.

Add the following test inside the describe block, right below the first test:

it('stepper should default to 0', () => {
  cy.mount(<Stepper />)
  cy.get('span').should('have.text', '0')
})

When you go back to the test runner, you should see the test pass.

In the above test, we select the element by passing in "span" to cy.get(), which will select all span tags in our component. We only have one span currently, so this works. However, if our component evolves and we add another span, then this test could start to fail. We should use a selector that will be less brittle to future changes.

In the Stepper component, the span tag has a data-cy attribute on it:

<span data-cy="counter">{count}</span>

We assign a unique id to the data-cy attribute that we can use for testing purposes. Update the test to use a CSS attribute selector to cy.get():

it('stepper should default to 0', () => {
  cy.mount(<Stepper />)
  cy.get('[data-cy=counter]').should('have.text', '0')
})

The test will still pass as expected, and our selector is now future-proof. For more info on writing good selectors, see our guide Selector Best Practices.

Passing Props to Components​

We should also have a test to ensure the count prop sets the count to something else besides its default value of "0". We can pass in props to the Stepper component like so:

it('supports a "count" prop to set the value', () => {
  cy.mount(<Stepper count={100} />)
  cy.get('[data-cy=counter]').should('have.text', '100')
})

Testing Interactions​

We mounted and selected the element in the above tests but didn't interact with it. We should also test that the value of the counter changes when a user clicks the "increment" and "decrement" buttons.

To do so, we will interact with the component by using the click() command, which clicks a DOM element just like a real user would.

Add the following tests:

it('when the increment button is pressed, the counter is incremented', () => {
  cy.mount(<Stepper />)
  cy.get('[data-cy=increment]').click()
  cy.get('[data-cy=counter]').should('have.text', '1')
})

it('when the decrement button is pressed, the counter is decremented', () => {
  cy.mount(<Stepper />)
  cy.get('[data-cy=decrement]').click()
  cy.get('[data-cy=counter]').should('have.text', '-1')
})

When you view the results of each of the tests, you will see that the counter is now "1" in the increment test, and "-1" in the decrement test. Not only did our tests pass, but we can visually see the results in a browser!

Testing Components with Events​

All the state of the Stepper Component (ie: the count) is handled internally in the component and then consumers are then alerted to changes to the state.

As the developer of the Stepper Component, you want to make sure when the end-user clicks the increment and decrement buttons, that the appropriate event is triggered with the proper values in the consuming component.

Using Spies​

We can use Cypress Spies to validate these events are being called correctly. A spy is a special function that keeps track of how many times it was called and any parameters that it was called with. We can then assign a spy to our event, interact with the component, and then query the spy to validate it was called with the parameters we expect.

Let's set up the spies and bind them to the component:

it('clicking + fires a change event with the incremented value', () => {
  const onChangeSpy = cy.spy().as('onChangeSpy')
  cy.mount(<Stepper onChange={onChangeSpy} />)
  cy.get('[data-cy=increment]').click()
  cy.get('@onChangeSpy').should('have.been.calledWith', 1)
})

First, we create a new spy by calling the cy.spy() method. We pass in a string that gives the spy an alias, which assigns the spy a name by which we can reference it later. In cy.mount(), we initialize the component and pass the spy into it. After that, we click the increment button.

The next line is a bit different. We've seen how we can use the cy.get() method to select elements, but we can also use it to grab any aliases we've set up previously. We use cy.get() to grab the alias to the spy (by prepending an "@" to the alias name). We assert that the method was called with the expected value.

With that, the Stepper component is well tested. Nice job!

What's Next?​

Congratulations, you covered the basics for Component Testing with Cypress!

To learn more about testing with Cypress, check out the Introduction to Cypress guide.

To track which parts of your components are exercised by your tests, set up code coverage for component tests.

tip

Writing component tests with an AI coding tool? The /cypress-author skill applies Cypress best practices automatically. See Cypress AI Skills.

Contents