Why Retry-ability of commands in Cypress? - Purpose & Use Cases

The Big Idea

What if your tests could patiently wait and never fail just because the app is a little slow?

The Scenario

Imagine you are testing a website manually. You click a button and wait for a message to appear. Sometimes it takes a moment, so you keep checking again and again, hoping it shows up. This waiting and checking is tiring and easy to miss.

The Problem

Manually waiting and checking is slow and boring. You might check too soon and think the feature is broken, or miss the message if you look away. This causes mistakes and wastes time, making testing frustrating and unreliable.

The Solution

Retry-ability means the test automatically tries again until the expected result appears or a timeout happens. This way, tests wait patiently and only fail if the feature truly does not work, making tests more reliable and faster to write.

Before vs After

✗ Before

cy.get('#submit').click().then(() => {
  expect(Cypress.$('#message').length).to.be.gt(0);
}); // fails if message not immediately present

✓ After

cy.get('#submit').click();
cy.get('#message').should('be.visible'); // retries until visible or timeout

What It Enables

It enables tests to handle real-world delays smoothly, making automated testing trustworthy and less flaky.

Real Life Example

When submitting a form, the confirmation message might take a second to appear. Retry-ability lets the test wait and catch that message without failing too early.

Key Takeaways

Manual checking is slow and error-prone.

Retry-ability automates waiting and rechecking.

This makes tests more reliable and easier to maintain.

Practice

1. What does retry-ability in Cypress help with during test execution?

easy

A. Automatically waiting for elements or conditions before proceeding

B. Skipping tests that take too long to run

C. Running tests in parallel on multiple browsers

D. Generating test data automatically

Solution

1. Step 1: Understand retry-ability concept

   Retry-ability means Cypress waits and retries commands until the element or condition is met or timeout occurs.

2. Step 2: Identify what retry-ability helps with

   This automatic waiting avoids flaky tests caused by timing issues, ensuring tests proceed only when ready.

3. Final Answer:

   Automatically waiting for elements or conditions before proceeding -> Option A

4. Quick Check:

   Retry-ability = Automatic wait [OK]

Hint: Retry-ability means Cypress waits automatically for conditions [OK]

Common Mistakes:

• Confusing retry-ability with parallel test execution
• Thinking retry-ability skips tests
• Assuming retry-ability generates test data

2. Which of the following Cypress command patterns correctly uses retry-ability?

easy

A. cy.wait(5000).get('.btn').click()

B. cy.get('.btn').click()

C. cy.click('.btn')

D. cy.get('.btn').should('be.visible').click()

Solution

1. Step 1: Identify retry-ability usage

   Retry-ability works with commands like get combined with should assertions that retry until condition is true.

2. Step 2: Check each option

   cy.get('.btn').should('be.visible').click() uses get with should('be.visible') which retries until the button is visible before clicking.

3. Final Answer:

   cy.get('.btn').should('be.visible').click() -> Option D

4. Quick Check:

   Use get + should for retry-ability [OK]

Hint: Use get() with should() for retry-ability in Cypress [OK]

Common Mistakes:

• Using cy.click() directly without get()
• Relying on fixed wait times instead of should()
• Missing should() causes no retry

3. Consider this Cypress code snippet:

cy.get('#status').should('contain', 'Success')
cy.get('#submit').click()

What happens if the element with id status initially does not contain 'Success' but updates after 2 seconds?

medium

A. The test fails immediately because 'Success' is not found

B. The test skips the assertion and clicks submit immediately

C. Cypress retries the assertion until 'Success' appears or timeout

D. The test waits 2 seconds automatically before clicking submit

Solution

1. Step 1: Understand retry-ability with should()

   The should('contain', 'Success') assertion retries until the text appears or timeout.

2. Step 2: Analyze behavior when text updates after 2 seconds

   Cypress waits and retries the assertion, so it passes once 'Success' appears, then proceeds to click.

3. Final Answer:

   Cypress retries the assertion until 'Success' appears or timeout -> Option C

4. Quick Check:

   should() retries until condition met [OK]

Hint: should() retries assertions until success or timeout [OK]

Common Mistakes:

• Assuming test fails immediately without retry
• Thinking Cypress waits fixed time automatically
• Believing test skips assertion

4. You wrote this Cypress test:

cy.get('.loading').should('not.exist')
cy.get('.content').click()

But the test fails because .content is not clickable yet. What is the likely cause?

medium

A. The get('.content') command does not wait for element to be clickable

B. The should('not.exist') does not retry properly for .loading

C. You need to add wait() before clicking .content

D. The selector .content is incorrect

Solution

1. Step 1: Understand retry-ability of should('not.exist')

   The should('not.exist') retries until the loading element disappears, so this part works correctly.

2. Step 2: Analyze get('.content').click() behavior

   The get command retries until the element exists but does not wait for it to be clickable or visible before clicking.

3. Final Answer:

   The get('.content') command does not wait for element to be clickable -> Option A

4. Quick Check:

   get() waits for existence, not clickability [OK]

Hint: get() waits for element existence, not clickability [OK]

Common Mistakes:

• Assuming should('not.exist') fails to retry
• Adding unnecessary fixed waits
• Blaming wrong selector without checking

5. You want to test a button that appears only after a loading spinner disappears. Which Cypress command sequence best uses retry-ability to ensure the button is clicked only when ready?

hard

A. cy.get('.spinner').should('not.exist')
cy.get('button#submit').click()

B. cy.get('.spinner').should('not.exist')
cy.get('button#submit').should('be.visible').click()

C. cy.get('button#submit').should('be.visible').click()

D. cy.wait(3000)
cy.get('button#submit').click()

Solution

1. Step 1: Wait for spinner to disappear

   Using should('not.exist') on spinner retries until spinner is gone, ensuring loading finished.

2. Step 2: Wait for button to be visible before clicking

   Using should('be.visible') retries until button is visible and ready for click, avoiding flaky clicks.

3. Final Answer:

   cy.get('.spinner').should('not.exist') cy.get('button#submit').should('be.visible').click() -> Option B

4. Quick Check:

   Chain should() assertions for reliable waits [OK]

Hint: Chain should('not.exist') and should('be.visible') for reliable clicks [OK]

Common Mistakes:

• Clicking button immediately after spinner disappears without visibility check
• Using fixed wait instead of retry-ability
• Skipping spinner wait and causing flaky tests