Working with cypress in Node.js

June 26, 2021

Testing is a vital part of software development. It is the main focus when following the Test-Driven Development principle. It ensures the behavior of our applications is as what we expect it to be. End-to-end testing, or e2e in short, is a testing approach used to check for user interactions with the application. We can use cypress to carry out these e2e tests.


Cypress is an end-to-end testing framework that helps developers test their web applications easily and provides an interface for them to easily analyze their test progress and results. This article aims to help readers understand how cypress works and how to write end-to-end tests.

In order for you to follow through the tutorial, you will need:

  1. A basic understanding of Node.js and have it installed on your machine.
  2. Knowledge in Javascript language and HTML.
  3. A basic understanding of testing.

With that, let’s get started.

Step 1: The setup

Create a new folder and give it any name of your choice. I will name mine cypress-testing. Navigate to the directory in your terminal and run the following to initialize an empty node project:

npm init -y

Next up, let’s install cypress in our project. Run the following command:

npm i cypress --save-dev

We save it as a dev dependency since we will run the tests locally and the dependency is not needed in a production environment. The command might take a while to complete. This is because it also downloads the Cypress binary.

This is a better approach than installing the cypress desktop application since it is better in CI/CD operations. You can read more about it here.

Once the binary is downloaded, you can run the following command to view the simple GUI that comes with it:

node_modules/.bin/cypress open

You can remove the example folder since we will write our own tests from scratch.

Next up, we will configure cypress to work with our local server. Add a script to start our cypress binary in our package.json file:

  "scripts": {
    "test": "cypress open"

Then we set the base URL of our server. This will tell cypress where the project is rendered. In the cypress.json file, add the following record:

  "baseUrl": "http://localhost:5000"

Port 5000 is the default port for the serve package which we shall use to render the application.

Step 2: The HTML form

We shall write tests for an HTML form. For this, we need a simple form with some fields and a submit button. Add the following code in an index.html file in the root directory of the project:

<!DOCTYPE html>
<html lang="en">
    <meta charset="UTF-8" />
    <title>Cypress Testing</title>
        <label for="name">Name</label>
        <input type="text" id="name" required />
        <label for="email">Email</label>
        <input type="email" id="email" required />
        <button type="submit">SEND</button>
    const form = document.forms[0];
    form.addEventListener("submit", (event) => {

This is a basic form with 2 fields and a submit button. We add a script below to prevent the form from submitting once we are done.

Now that we have the basics done, we can now get into the real testing and see what cypress can do.

To view the page, run npx serve to render the index file. The command also copies the URL in your clipboard so you can directly paste it into your browser.

Step 3: Writing tests

In your cypress/integration folder, create a new file named forms.spec.js. This is the naming convention followed in testing with cypress.

To write tests, we use the describe keyword.

describe("Forms test", () => {
  // tests go here

Fun fact: the same keyword is used in the mocha testing framework.

All the tests involving our forms will go in here. It receives the name of the collection/suite of the tests and a callback that holds all the actual tests. To test a single action, we use the it keyword.

First, let’s test whether we can get to the form. Go ahead and add the following inside the describe function:

it("can get to the form", () => {

cy stands for cypress and this allows us to access the various actions that cypress offers. .visit instructs cypress to navigate to the specified route while .get is used to select the elements in the page.

Run the test command we created a while ago. The binary should appear with a list of all the integrations test in your application. In our case, we should have only one test displayed.


Click the Run (n) integration spec button. This will open a new tab in your default browser and run the test. The result should be similar to the one below.


Awesome stuff right? 😎

Another great thing about cypress is that the test GUI actively listens to the changes in the spec files. Once you add tests and save the file, the changes should reflect in the binary and browser.

The cypress GUI is interactive and you can explore by checking which elements are tested individually by clicking on the test name.

Let’s test the form inputs. We can use the .type method to mimic a user typing action in a field and ensure the value returned by the input is still the same.

For that, add the following test, still under the forms test suite:

it("can fill the form", () => {
  cy.get('input[id="name"]').type("linus").should("have.value", "linus");

The test passes, obviously! You can try out different values and check for differences. If you notice, we used the id attribute to get the input. We can also use the name attribute.

We use the .should method with the have.value assertion to confirm the value. You can read more about assertions in this section of the docs.

To test submission, you can use the .submit function like so:

it("can submit the form", () => {

The result of submitting the form is logged in the console so you can check the chrome dev tools for the value.


Those are just a few tests you can carry out using cypress. There are methods like .on and .its. You can go ahead and change the values as you learn more about testing. There are network request tests with cypress which can help mock the functionality after submitting your form.

Cypress makes testing easy for developers and ensures you follow a clean TDD approach when creating your applications. You can find the source code for this tutorial on GitHub.

Have fun coding!

Peer Review Contributions by: Daniel Katungi