Book Image

End-to-End Web Testing with Cypress

By : Waweru Mwaura
1 (1)
Book Image

End-to-End Web Testing with Cypress

1 (1)
By: Waweru Mwaura

Overview of this book

Cypress is a modern test automation framework for web-based frontend apps. Learning Cypress will help you overcome the shortcomings of conventional testing solutions such as dependency graph problems, the steep learning curve in setting up end-to-end testing packages, and difficulties in writing explicit time waits for your tests. In End-to-End Web Testing with Cypress, you’ll learn how to use different Cypress tools, including time travel, snapshots, errors, and console output, to write fail-safe and non-flaky tests. You’ll discover techniques for performing test-driven development (TDD) with Cypress and write cross-browser tests for your web applications. As you advance, you’ll implement tests for a sample application and work with a variety of tools and features within the Cypress ecosystem. Finally, this Cypress book will help you grasp advanced testing concepts such as visual testing and networking. By the end of this book, you’ll have the skills you need to be able to set up Cypress for any web app and understand how to use it to its full potential.
Table of Contents (17 chapters)
1
Section 1: Cypress as an End-to-End Testing Solution for Frontend Applications
7
Section 2: Automated Tests with the TDD Approach
12
Section 3: Automated Testing for Your Web Application

Running Cypress commands

Effective utilization of the Cypress framework requires you to have an understanding of Cypress and how different functionalities can be run using the command line. Cypress commands allow the users of the Cypress framework to automate processes, and also to provide specific instructions to the framework and to the tests during initialization and runtime.

In most instances, running Cypress tests through the command line is quicker than running them using the browser. This is because running tests through the command line reduces the number of resources required to run a specific test. The reason for this is that tests that run in the command line are normally headless, which means less resources are allocated to run the tests, which is not the same for test execution in headed mode.

Important note

Headed mode is when tests can be visually seen running on a browser, while in headless mode, the test execution process does not open a visible browser. Instead...