You're reading from End-to-End Web Testing with Cypress Explore techniques for automated frontend web testing with Cypress and JavaScript

Product type Paperback

Published in Jan 2021

Publisher Packt

ISBN-13 9781839213854

Length 240 pages

Edition 1st Edition

Languages

JavaScript

Tools

Cypress

Concepts

Test Driven Development

Author (1):

Waweru Mwaura

View More author details

Table of Contents (17) Chapters

Preface

1. Section 1: Cypress as an End-to-End Testing Solution for Frontend Applications

2. Chapter 1: Installing and Setting Up Cypress FREE CHAPTER

3. Chapter 2: Differences between Selenium WebDriver and Cypress

4. Chapter 3: Working with Cypress Command-Line Tools

5. Chapter 4: Writing Your First Test

6. Chapter 5: Debugging Cypress Tests

7. Section 2: Automated Tests with the TDD Approach

8. Chapter 6: Writing Cypress Tests Using the TDD approach

9. Chapter 7: Understanding Element Interaction in Cypress

10. Chapter 8: Understanding Variables and Aliases in Cypress

11. Chapter 9: Advanced Uses of Cypress Test Runner

12. Section 3: Automated Testing for Your Web Application

13. Chapter 10: Exercise – Navigation and Network Requests

14. Chapter 11: Exercise – Stubbing and Spying XHR Requests

15. Chapter 12: Visual Testing in Cypress

16. Other Books You May Enjoy

Creating test files

All tests within Cypress must be within a test file for them to run. For a test to be considered useful, it must validate all the conditions that we have defined in the test and return a response stating whether the conditions have been met. Cypress tests are no exception to the process of writing tests, and all the tests that are written in a test file must have a set of conditions to be validated.

In this section, we will go through the process of writing a test file, starting from where a test file should be located in Cypress, different extensions that Cypress supports, and the file structures that test files written in Cypress should follow.

Testfiles location

Cypress creates test files by default when it is initialized in the cypress/integration/examples directory. However, these can be deleted as they are intended to show the proper format of utilizing different Cypress test types and assertions. Cypress allows you to be flexible when it comes to...