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

Special debugging commands

If jumping through commands is not your thing, or you are finding it difficult to understand how travelling back in time shows you the order of execution in a test, Cypress has got your back. Cypress includes commands that are helpful for debugging and even gives you the options that you would have when using normal code debuggers. The two commands that we will be exploring in this section are as follows:

cy.debug()
cy.pause()

Using these Cypress debug commands, we can understand how to debug Cypress from the tests themselves. These two special debugging commands will allow us to directly control the debug process as we execute our tests. Having the ability to stop execution within the tests themselves gives us the advantage of only having to debug the specific sections that are throwing errors in Cypress.