Introduction to Automation Testing with Cypress for the Modern Web

Back to Blog
Automation Testing with Cypress

Introduction to Automation Testing with Cypress for the Modern Web

About Cypress

Cypress is a front-end automation tool created for the modern web. Cypress is built using new architecture and it runs in the same run-loop as the application under test. This results in Cypress providing better, faster, and more reliable testing for anything that runs in a browser. Cypress works on any front-end framework or website

Cypress’s Features

Some of the key features of Cypress are Time Travel, Debug ability, Automatic wait, Spies, Stubs, and Clocks, Network Traffic Control, Consistent Results, Screenshots, and Videos

What you may like in Cypress:

  • Cypress does not use Selenium as most of the other end-to-end testing tools are using Selenium, that’s why others have almost the same problems
  • Easy and effortless installation and updating. If you’re using Node.js and want to install Cypress in the project it will be just a single line in the console. (npm install cypress)
  • Cypress supports any framework or website quite well. There are thousands of projects built using the latest React, Angular, Vue, Elm, etc. frameworks. Cypress also works equally well on server-rendered pages or applications.
  • Cypress tests are only written in JavaScript. While one can compile down to JavaScript from any other language, ultimately the test code is executed inside the browser itself. There are no languages or driver bindings – there is and will always be just JavaScript.
  • Cypress has no issues with nodes, their versions, and related dependencies.
  • It has an awesome dashboard and preview window. Just look at the screenshot below. It gives you a precise overview of what’s being tested.
  • Screenshot for every step, of the script, which can be quite helpful if there, is any false passing or failing test which is good for debugging also.
  • A broad range of debugging and testing tracking options. The list has integration with dev tools, screenshots, snaps, etc
  • Headless option and ease of integrating with CI. At present, Cypress can be integrated with around 15 CI providers. Cypress runs much faster with end-to-end tools.
  • Network traffic control. i.e. Detection, debugging, verification, waiting for requests
  • Eliminating all sorts of timers. Cypress features a built-in mechanism to handle waiting for DOM elements
  • Easy to use & intuitive syntax (Mocha and Chai are all there)
  • A wide range of selectors plus Cypress ‘built-in’ commands serves all requirement

What you may dislike in Cypress:

  • The structure is different from the other Selenium end-to-end tools, so in the first place need to spend more time understanding.
  • Community: As Cypress is relatively new may find trouble getting answers
  • No native event handling capabilities like files upload etc. & No cross-browsers testing.
  • No Page Object Model supports an altogether different approach
  • It’s only available for only one client (language) i.e. for JavaScript only.

Pros and Cons: Cypress vs. Selenium

Cypress vs. Selenium

Going Ahead With Cypress:

·  Must be good at JavaScript Coding

·   Limitation as cannot parallelize test execution

·   No Cross Browser Testing & No Support for native event handling

·   No out-of-box support for Page Object Model

Setting Up Cypress
  • Pre-requisites

·  Download and install Node.js

·   Download and install VS Code

·   Create a project folder say “eazyagile”

·  Open the folder in VS Code

·  In VS Code terminal run npm init -y

  •   Install Cypress

                 ·  In VS Code terminal run npm install cypress

  • Create Folder Structure for Cypress tests & Write tests

·  In VS Code terminal run npx cypress open (To create folder structure required for cypress tests)

·  Delete the examples folder from the integration

·  Create an authentication folder under integration

·  Create an authentication folder under support

authentication folder under integration

·  Create login.spec.js in the authentication folder under integration

authentication folder under support

·  Create login-form.js & index.js in the authentication folder under support

1

 

  • Tests Execution

                       ·  In VS Code terminal run npm start

Tests Execution

 

  • Runner Window

 

Runner Window

 

  • Execution in Progress

Execution in Progress

 

 

 

Share this post

Back to Blog