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

One of the core features of Cypress is its ability to retry commands several times to reduce the likelihood of flakes. As discussed previously in the "[Consistent Results](https://www.educative.io/courses/frontend-testing-cypress/consistent-results)" lesson, Cypress takes several measures to battle the most common causes of flakes, such as:

- Half-loaded application state.
- Elements that are not available, covered, or disabled.
- Flakes caused by animations.

---

## Retrying commands and assertions

To battle all of this, Cypress retries both commands and assertions alike. The commands are Cypress calls that execute either a user behavior or get an element:

One of the core features of Cypress is its ability to retry commands several times to reduce the likelihood of flakes. As discussed previously in the "[Consistent Results](https://www.educative.io/courses/frontend-testing-cypress/consistent-results)" lesson, Cypress takes several measures to battle the most common causes of flakes, such as:

- Half-loaded application state.
- Elements that are not available, covered, or disabled.
- Flakes caused by animations.

---

# Retrying commands and assertions

To battle all of this, Cypress retries both commands and assertions alike. The commands are Cypress calls that execute either a user behavior or get an element:

Learn how Cypress retries commands and assertions to avoid flakes. In addition, learn how we can use retry-ability to our advantage.

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

Retry-ability

Retrying commands and assertions