Testing Vue Elements With Cypress

No Comments

Cypress is an automatic check runner for browser-based purposes and pages. I’ve used it for years to write down end-to-end assessments for internet tasks, and was joyful to see not too long ago that particular person element testing had come to Cypress. I work on a big enterprise Vue utility, and we already use Cypress for end-to-end assessments. Most of our unit and element assessments are written with Jest and Vue Take a look at Utils.

As soon as element testing arrived in Cypress, my staff was all in favor of upgrading and making an attempt it out. You may be taught lots about how element testing works immediately from the Cypress docs, so I’m going skip over among the setup steps and deal with what it’s wish to work with element assessments — what do they seem like, how are we utilizing them, and a few Vue-specific gotchas and helpers we discovered.

Disclosure! On the time I wrote the primary draft of this text, I used to be the front-end staff lead at a big fleet administration firm the place we used Cypress for testing. For the reason that time of writing, I’ve began working at Cypress, the place I get to contribute to the open supply check runner.

All of the examples talked about listed below are legitimate on the time of writing utilizing Cypress 8. It’s a brand new characteristic that’s nonetheless in alpha, and I wouldn’t be shocked if a few of these particulars change in future updates.

If you have already got a background in testing and element assessments, you’ll be able to skip proper to our staff’s experiences.

What a element check file appears like

For a simplified instance, I’ve created a mission that accommodates a “Privateness Coverage” element. It has a title, physique, and an acknowledgment button.

When the button is clicked, an occasion is emitted to let the mother or father element know that this has been acknowledged. Right here it’s deployed on Netlify.

Now right here’s the final form of a element check in Cypress that makes use of among the characteristic’s we’re going to speak about:

import { mount } from ‘@cypress/vue’; // import the vue-test-utils mount operate
import PrivacyPolicyNotice from ‘./PrivacyPolicyNotice.vue’; // import the element to check

describe(‘PrivacyPolicyNotice’, () => {

it(‘renders the title’, () => {
// mount the element by itself within the browser 🏗

// assert some textual content is current within the appropriate heading degree 🕵️
cy.accommodates(‘h1’, ‘Privateness Coverage’).ought to(‘be.seen’);

it(’emits a “affirm” occasion as soon as when affirm button is clicked’, () => {
// mount the element by itself within the browser 🏗

// this time let’s chain some instructions collectively
cy.accommodates(‘button’, ‘/^OK/’) // discover a button ingredient beginning with textual content ‘OK’ 🕵️
.click on() // click on the button 🤞
.vue() // use a customized command to go get the vue-test-utils wrapper 🧐
.then((wrapper) => {
// confirm the element emitted a affirm occasion after the press 🤯
// `emitted` is a helper from vue-test-utils to simplify accessing
// occasions which have been emitted


This check makes some assertions concerning the person interface, and a few concerning the developer interface (shoutout to Alex Reviere for expressing this division in the best way that clicked for me). For the UI, we’re focusing on particular components with their anticipated textual content content material. For builders, we’re testing what occasions are emitted. We’re additionally implicitly testing that the element is a accurately shaped Vue element; in any other case it could not mount efficiently and all the opposite steps would fail. And by asserting particular sorts of components for particular functions, we’re testing the accessibility of the element — if that accessible button ever turns into a non-focusable div, we’ll learn about it.

Right here’s how our check appears after I swap out the button for a div. This helps us preserve the anticipated keyboard conduct and assistive know-how hints that come without cost with a button ingredient by letting us know if we by accident swap it out:

Slightly groundwork

Now that we’ve seen what a element check appears like, let’s again up slightly bit and speak about how this suits in to our total testing technique. There are numerous definitions for these items, so actual fast, for me, in our codebase:

Unit assessments affirm single features behave as anticipated when utilized by a developer. Element assessments mount single UI elements in isolation and ensure they behave as anticipated when utilized by an end-user and a developer.Finish-to-end assessments go to the applying and carry out actions and ensure the app as complete behaves accurately when utilized by an end-user solely.

Lastly, integration testing is a bit more of a squishy time period for me and may occur at any degree — a unit that imports different features, a element that imports different elements, or certainly, an “end-to-end” check that mocks API responses and doesn’t attain the database, may all be thought-about integration assessments. They check multiple a part of an utility working collectively, however not the complete factor. I’m undecided about the true usefulness of that as a class, because it appears very broad, however totally different individuals and organizations use these phrases in different methods, so I wished to the touch on it.

For an extended overview of the totally different sorts of testing and the way they relate to front-end work, you’ll be able to try “Entrance-Finish Testing is For Everybody” by Evgeny Klimenchenko.

Element assessments

Within the definitions above, the totally different testing layers are outlined by who will probably be utilizing a bit of code and what the contract is with that particular person. In order a developer, a operate that codecs the time ought to all the time return the right consequence after I present it a sound Date object, and may throw clear errors if I present it one thing totally different as effectively. These are issues we are able to check by calling the operate by itself and verifying it responds accurately to numerous situations, unbiased of any UI. The “developer interface” (or API) of a operate is all about code speaking to different code.

Now, let’s zoom in on element assessments. The “contract” of a element is de facto two contracts:

To the developer utilizing a element, the element is behaving accurately if the anticipated occasions are emitted based mostly on person enter or different exercise. It’s additionally truthful to incorporate issues like prop sorts and validation guidelines in our thought of “appropriate developer-facing conduct,” although these issues can be examined at a unit degree. What I really need from a element check as a developer is to understand it mounts, and sends the alerts it’s speculated to based mostly on interactions.To the person interacting with a element, it’s behaving accurately if the UI displays the state of the element always. This consists of extra than simply the visible facet. The HTML generated by the element is the inspiration for its accessibility tree, and the accessibility tree supplies the API for instruments like display screen readers to announce the content material accurately, so for me the element shouldn’t be “behaving accurately” if it doesn’t render the right HTML for the contents.

At this level it’s clear that element testing requires two sorts of assertions — generally we verify Vue-specific issues, like “what number of occasions obtained emitted of a sure sort?”, and generally we verify user-facing issues, like “did a visual success message really find yourself on the display screen although?”

It additionally appears like element degree assessments are a strong documentation instrument. The assessments ought to assert all of the vital options of a element — the outlined behaviors which can be relied on — and ignore particulars that aren’t vital. This implies we are able to look to the assessments to know (or bear in mind, six months or a yr from now!) what a element’s anticipated conduct is. And, all going effectively, we are able to change any characteristic that’s not explicitly asserted by the check with out having to rewrite the check. Design modifications, animation modifications, bettering the DOM, all must be doable, and if a check does fail, it is going to be for a purpose you care about, not as a result of a component obtained moved from one a part of the display screen to a different.

This final half takes some care when designing assessments, and most particularly, when selecting selectors for components to work together with, so we’ll return to this matter later.

How Vue element assessments work with and with out Cypress

At a excessive degree, a mix of Jest and the Vue Take a look at Utils library has turns into roughly the usual strategy to working element assessments that I’ve seen on the market.

Vue Take a look at Utils provides us helpers to mount a element, give it its choices, and mock out varied issues a element may rely on to run correctly. It additionally supplies a wrapper object across the mounted element to make it slightly simpler to make assertions about what’s happening with the element.

Jest is a superb check runner and can get up the mounted element utilizing jsdom to simulate a browser atmosphere.

Cypress’ element check runner itself makes use of Vue Take a look at Utils to mount Vue elements, so the primary distinction between the 2 approaches is context. Cypress already runs end-to-end assessments in a browser, and element assessments work the identical means. This implies we are able to see our assessments run, pause them mid-test, work together with the app or examine issues that occurred earlier within the run, and know that browser APIs that our utility is determined by are real browser conduct relatively than the jsdom mocked variations of those self same options.

As soon as the element is mounted, all the same old Cypress issues that we have now been doing in end-to-end assessments apply, and some ache factors round choosing components go away. Primarily, Cypress goes to deal with simulating all of the person interactions, and making assertions concerning the utility’s response to these interactions. This covers the user-facing a part of the element’s contract utterly, however what concerning the developer-facing stuff, like occasions, props, and every little thing else? That is the place Vue Take a look at Utils comes again in. Inside Cypress, we are able to entry the wrapper that Vue Take a look at Utils creates across the mounted element, and make assertions about it.

What I like about that is that we find yourself with Cypress and Vue Take a look at Utils each getting used for what they’re actually good at. We will check the element’s conduct as a person with no framework-specific code in any respect, and solely dig into Vue Take a look at Utils for mounting the element and checking particular framework conduct after we select to. We’ll by no means should await a Vue-specific $nextTick after performing some Vue-specific factor to replace the state of a element. That was all the time the trickiest factor to clarify to new builders on the staff with out Vue expertise — when and why they would wish to await issues when writing a check for a Vue element.

Our expertise of element testing

The benefits of element testing sounded nice to us, however after all, in a big mission only a few issues may be seamless out of the field, and as we obtained began with our assessments, we bumped into some points. We run a big enterprise SPA constructed utilizing Vue 2 and the Vuetify element library. Most of our work closely makes use of Vuetify’s built-in elements and types. So, whereas the “check elements by themselves” strategy sounds good, an enormous lesson discovered was that we would have liked to arrange some context for our elements to be mounted in, and we would have liked to get Vuetify and a few international types taking place as effectively, or nothing was going to work.

Cypress has a Discord the place individuals can ask for assist, and after I obtained caught I requested questions there. Of us from the group —in addition to Cypress staff members — kindly directed me to instance repos, code snippets, and concepts for fixing our issues. Right here’s a listing of the little issues we would have liked to know with a view to get our elements to mount accurately, errors we encountered, and no matter else stands out as fascinating or useful:

Importing and utilizing VuetifyIncluding some attributes that Vuetify is determined by to the __cy_root ingredientUtilizing .spec recordsdata positioned alongside aspect element recordsdata, not in a separate check folderCoping with a customized command import battle between element assessments and end-to-end assessmentsAccessing the Vue wrapper simply in a Cypress context

Importing Vuetify

Via lurking within the Cypress Discord, I’d seen this instance element check Vuetify repo by Bart Ledoux, in order that was my start line. That repo organizes the code into a reasonably frequent sample that features a plugins folder, the place a plugin exports an occasion of Veutify. That is imported by the applying itself, however it can be imported by our check setup, and used when mounting the element being examined. Within the repo a command is added to Cypress that can exchange the default mount operate with one which mounts a element with Vuetify.

Right here is all of the code wanted to make that occur, assuming we did every little thing in instructions.js and didn’t import something from the plugins folder. We’re doing this with a customized command which signifies that as an alternative of calling the Vue Take a look at Utils mount operate immediately in our assessments, we’ll really name our personal cy.mount command:

// the Cypress mount operate, which wraps the vue-test-utils mount operate
import { mount } from “@cypress/vue”;
import Vue from ‘vue’;
import Vuetify from ‘vuetify/lib/framework’;


// add a brand new command with the title “mount” to run the Vue Take a look at Utils
// mount and add Vuetify
Cypress.Instructions.add(“mount”, (MountedComponent, choices) => {
return mount(MountedComponent, {
vuetify: new Vuetify({});, // the brand new Vuetify occasion
…choices, // To override/add Vue choices for particular assessments

Now we’ll all the time have Vuetify together with our elements when mounted, and we are able to nonetheless go in all the opposite choices we have to for that element itself. However we don’t have to manually add Veutify every time.

Including attributes required by Vuetify

The one drawback with the brand new mount command above is that, to work accurately, Vuetify elements anticipate to be rendered in a sure DOM context. Apps utilizing Vuetify wrap every little thing in a <v-app> element that represents the basis ingredient of the applying. There are a few methods to deal with this however the easiest is so as to add some setup to our command itself earlier than it mounts a element.

Cypress.Instructions.add(“mount”, (MountedComponent, choices) => {
// get the ingredient that our mounted element will probably be injected into
const root = doc.getElementById(“__cy_root”);

// add the v-application class that enables Vuetify types to work
if (!root.classList.accommodates(“v-application”)) {

// add the data-attribute — Vuetify selector used for popup components to connect to the DOM
root.setAttribute(‘data-app’, ‘true’);

return mount(MountedComponent, {
vuetify: new Vuetify({}),

This takes benefit of the truth that Cypress itself has to create some root ingredient to really mount our element to. That root ingredient is the mother or father of our element, and it has the ID __cy_root. This provides us a spot to simply add the right courses and attributes that Vuetify expects to seek out. Now elements that use Vuetify elements will look and behave accurately.

One different factor we observed after some testing is that the required class of v-application has a show property of flex. This is sensible in a full app context utilizing Vuetify’s container system, however had some undesirable visible uncomfortable side effects for us when mounting single elements — so we added yet another line to override that model earlier than mounting the element:

root.setAttribute(‘model’, ‘show: block’);

This cleared up the occasional structure points after which we have been really performed tweaking the encompassing context for mounting elements.

Getting spec recordsdata the place we would like them

A whole lot of the examples on the market present a cypress.json config file like this one for element testing:

“fixturesFolder”: false,
“componentFolder”: “src/elements”,
“testFiles”: “**/*.spec.js”

That’s really fairly near what we would like for the reason that testFiles property accepts a glob sample. This one says, Look in any folder for recordsdata ending in .spec.js. In our case, and doubtless many others, the mission’s node_modules folder contained some irrelevant spec.js recordsdata that we excluded by prefixing !(node_modules) like this:

“testFiles”: “!(node_modules)**/*.spec.js”

Earlier than selecting this resolution, when experimenting, we had set this to a particular folder the place element assessments would dwell, not a glob sample that would match them wherever. Our assessments dwell proper alongside our elements, so that would have been high quality, however we even have two unbiased elements folders as we bundle up and publish a small a part of our app for use in different tasks on the firm. Having made that change early, I admit I positive did overlook it had been a glob to start out with and was beginning to get astray earlier than popping into the Discord, the place I obtained a reminder and figured it out. Having a spot to rapidly verify if one thing is the proper strategy was useful many instances.

Command file battle

Following the sample outlined above to get Vuetify working with our element assessments produced an issue. We had piled all these things collectively in the identical instructions.js file that we used for normal end-to-end assessments. So whereas we obtained a few element assessments working, our end-to-end assessments didn’t even begin. There was an early error from one of many imports that was solely wanted for element testing.

I used to be really useful a few options however on the day, I selected to only extract the mounting command and its dependencies into its personal file, and imported it solely the place wanted within the element assessments themselves. Since this was the one supply of any drawback working each units of assessments, it was a clear method to take that out of the the end-to-end context, and it really works simply high quality as a standalone operate. If we have now different points, or subsequent time we’re doing cleanup, we’d most likely comply with the primary advice given, to have two separate command recordsdata and share the frequent items between them.

Accessing the Vue Take a look at Utils wrapper

Within the context of a element check, the Vue Take a look at Utils wrapper is on the market underneath Cypress.vueWrapper. When accessing this to make assertions, it helps to make use of cy.wrap to make the consequence chain-able like different instructions accessed by way of cy. Jessica Sachs provides a brief command in her instance repo to do that. So, as soon as once more inside instructions,js, I added the next:

Cypress.Instructions.add(‘vue’, () => {
return cy.wrap(Cypress.vueWrapper);

This can be utilized in a check, like this:

.accommodates(‘button’, ‘Do the factor as soon as’)
.click on()
.ought to(‘be.disabled’)
.then((wrapper) => {
// the Vue Take a look at Utils `wrapper` has an API particularly setup for testing:
// https://vue-test-utils.vuejs.org/api/wrapper/#properties

This begins to learn very naturally to me and clearly splits up after we are working with the UI in comparison with after we are inspecting particulars revealed by way of the Vue Take a look at Utils wrapper. It additionally emphasizes that, like plenty of Cypress, to get essentially the most out of it, it’s necessary to know the instruments it leverages, not simply Cypress itself. Cypress wraps Mocha, Chai, and varied different libraries. On this case, it’s helpful to know that Vue Take a look at Utils is a third-party open supply resolution with its personal whole set of documentation, and that contained in the then callback above, we’re in Vue Take a look at Utils Land — not Cypress Land — in order that we go to the proper place for assist and documentation.


Since this has been a current exploration, we have now not added the Cypress element assessments to our CI/CD pipelines but. Failures is not going to block a pull request, and we haven’t checked out including the reporting for these assessments. I don’t anticipate any surprises there, however it’s value mentioning that we haven’t accomplished integrating these into our complete workflow. I can’t converse to it particularly.

It’s additionally comparatively early days for the element check runner and there are a number of hiccups. At first, it appeared like each second check run would present a linter error and should be manually refreshed. I didn’t resolve that, after which it mounted itself (or was mounted by a more moderen Cypress launch). I’d anticipate a brand new instrument to have potential points like this.

One different stumbling block about element testing basically is that, relying on how your element works, it may be tough to mount it with out a number of work mocking different components of your system. If the element interacts with a number of Vuex modules or makes use of API calls to fetch its personal knowledge, you should simulate all of that once you mount the element. The place end-to-end assessments are virtually absurdly straightforward to stand up and working on any mission that runs within the browser, element assessments on present elements are much more delicate to your element design.

That is true of something that mounts elements in isolation, like Storybook and Jest, which we’ve additionally used. It’s usually once you try and mount elements in isolation that you simply notice simply what number of dependencies your elements even have, and it might probably look like a number of effort is required simply to supply the proper context for mounting them. This nudges us in direction of higher element design in the long term, with elements which can be simpler to check and whereas touching fewer components of the codebase.

Because of this, I’d counsel for those who haven’t already obtained element assessments, and so aren’t positive what you should mock with a view to mount your element, select your first element assessments rigorously, to restrict the variety of components you need to get proper earlier than you’ll be able to see the element within the check runner. Decide a small, presentational element that renders content material offered by way of props or slots, to see it a element check in motion earlier than entering into the weeds on dependencies.


The element check runner has labored out effectively for our staff. We have already got intensive end-to-end assessments in Cypress, so the staff is aware of spin up new assessments and write person interactions. And we have now been utilizing Vue Take a look at Utils for particular person element testing as effectively. So there was not really an excessive amount of new to be taught right here. The preliminary setup points might have been irritating, however there are many pleasant individuals on the market who may also help work by way of points, so I’m glad I used the “asking for assist” superpower.

I might say there are two major advantages that we’ve discovered. One is the constant strategy to the check code itself between ranges of testing. This helps as a result of there’s now not a psychological shift to consider delicate variations between Jest and Cypress interactions, browser DOM vs jsdom and comparable points.

The opposite is having the ability to develop elements in isolation and getting visible suggestions as we go. By organising all of the variations of a element for improvement functions, we get the define of the UI check prepared, and perhaps a number of assertions too. It appears like we get extra worth out of the testing course of up entrance, so it’s much less like a bolted-on process on the finish of a ticket.

This course of shouldn’t be fairly test-driven improvement for us, although we are able to drift into that, however it’s usually “demo-driven” in that we need to showcase the states of a brand new piece of UI, and Cypress is a reasonably great way to do this, utilizing cy.pause() to freeze a working check after particular interactions and discuss concerning the state of the element. Creating with this in thoughts, realizing that we are going to use the assessments to stroll by way of the elements options in a demo, helps manage the assessments in a significant means and encourages us to cowl all of the eventualities we are able to consider at improvement time, relatively than after.


The psychological mannequin for what precisely Cypress as complete does was tough for me to after I first discovered about it, as a result of it wraps so many different open supply instruments within the testing ecosystem. You may stand up and working rapidly with Cypress with out having a deep information of what different instruments are being leveraged underneath the hood.

This meant that when issues went unsuitable, I bear in mind not being positive which layer I ought to take into consideration — was one thing not working due to a Mocha factor? A Chai difficulty? A foul jQuery selector in my check code? Incorrect use of a Sinon spy? At a sure level, I wanted to step again and find out about these particular person puzzle items and what precise roles they have been taking part in in my assessments.

That is nonetheless the case with element testing, and now there’s an additional layer: framework-specific libraries to mount and check elements. In some methods, that is extra overhead and extra to be taught. Then again, Cypress integrates these instruments in a coherent means and manages their setup so we are able to keep away from a complete unrelated testing setup only for element assessments. For us, we already wished to mount elements independently for testing with Jest, and to be used in Storybook, so we discovered a number of the required mocking concepts forward of time, and tended to favor well-separated elements with easy props/occasions based mostly interfaces for that purpose.

On stability, we like working with the check runner, and I really feel like I’m seeing extra assessments (and extra readable check code!) displaying up in pull requests that I assessment, so to me that’s an indication that we’ve moved in a great course.

The put up Testing Vue Elements With Cypress appeared first on CSS-Tips. You may help CSS-Tips by being an MVP Supporter.

    About Marketing Solution Australia

    We are a digital marketing company with a focus on helping our customers achieve great results across several key areas.

    Request a free quote

    We offer professional SEO services that help websites increase their organic search score drastically in order to compete for the highest rankings even when it comes to highly competitive keywords.

    Subscribe to our newsletter!

    More from our blog

    See all posts

    Leave a Comment