Learn how you can improve the quality of your site and capture bugs before they reach production with the help of Cypress.

Frontend End-to-End Testing with Cypress.png

Cypress.tar.gz

Cypress

CypressGUI

Cypress, an end-to-end testing framework, has become a popular choice among front-end developers to test their applications with a fast, easy-to-use, and reliable testing tool. It allows you to test your applications with a fast, easy-to-use, and reliable testing tool. It can help you improve your site by capturing bugs before they reach production.

In this course, you'll start off with the basics of Cypress, learn why Cypress is a great choice, how it works, and how you can create robust test cases with its help. In this course, you'll start off with the basics of Cypress, learn why it is a great choice, how it works, and how we can create robust test cases. We will also ensure that our site is usable by the widest possible audience by integrating Axe by Deque, an accessibility engine.

By the end of this course, you'll have a solid foundation to enhance the quality of your front-end application and learn more advanced concepts to take your E2E testing to the next level.

Frontend End-to-End Testing with Cypress

Another powerful built-in command for debugging test cases is the `cy.pause` command. Unlike `cy.debug`, this does not set a `debugger` in the code. Rather, it stops the Cypress command from running whatever it is attached to. Why is it useful? It allows us to interact with the application and step through each command one-by-one, followed by the `pause` command.

---

## Pausing commands

To use `cy.pause`, we can chain it off from other Cypress commands or call it on its own. We can also chain other commands from it:

```javascript
cy.get('@cookiePolicyBanner').pause(); // Pause after the `get` command is executed
cy.pause().get('@cookiePolicyBanner'); // Pause before the `get` command is executed 
```

If we run the above commands, we can see that additional buttons will appear inside of the status bar:

Another powerful built-in command for debugging test cases is the `cy.pause` command. Unlike `cy.debug`, this does not set a `debugger` in the code. Rather, it stops the Cypress command from running whatever it is attached to. Why is it useful? It allows us to interact with the application and step through each command one-by-one, followed by the `pause` command.

---

# Pausing commands

To use `cy.pause`, we can chain it off from other Cypress commands or call it on its own. We can also chain other commands from it:

```javascript
cy.get('@cookiePolicyBanner').pause(); // Pause after the `get` command is executed
cy.pause().get('@cookiePolicyBanner'); // Pause before the `get` command is executed 
```

If we run the above commands, we can see that additional buttons will appear inside of the status bar:

Learn about different ways to debug flakes in Cypress.

What is Cypress?

Why Cypress?

How Cypress Works

The Features of Cypress

The Structure of Cypress

Writing Your Very First Test Case

Integrating Axe

Running Your Test Cases

Debugging Cypress

What's Next?

Appendix

Debugging Flaky Tests

Pausing commands