cy.wait() for explicit waiting in Cypress - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the output of this Cypress test snippet?

Consider the following Cypress test code. What will be the value of counter after the test runs?

Cypress

let counter = 0;

cy.wait(1000).then(() => {
  counter += 1;
});

cy.wait(500).then(() => {
  counter += 2;
});

A counter will be 2

B counter will be 1

C counter will be 3

D counter will be 0

💡 Hint

Remember that Cypress commands are queued and run in order.

The cy.wait() commands run sequentially. The first cy.wait(1000) waits 1 second and then increments counter by 1. The second cy.wait(500) waits 0.5 seconds and then increments counter by 2. Both increments happen in order, so the final value is 3.

❓ assertion

intermediate

Which assertion correctly waits for 2 seconds before checking the element?

You want to wait explicitly for 2 seconds before asserting that a button with id #submit is visible. Which option correctly does this in Cypress?

A cy.wait(2000); cy.get('#submit').should('be.visible');

B cy.wait('#submit', 2000).should('be.visible');

C cy.get('#submit').wait(2000).should('be.visible');

D cy.get('#submit').should('be.visible').wait(2000);

💡 Hint

Think about the order of commands and what cy.wait() accepts as arguments.

Option A waits for 2 seconds first, then gets the element and asserts visibility. Options A and C misuse wait() as it is not a chainable command on elements. Option A uses invalid syntax.

🔧 Debug

advanced

Why does this Cypress test fail intermittently?

This test sometimes fails because the element is not found. What is the likely cause?

Cypress

cy.get('#loadButton').click();
cy.get('#result').should('contain', 'Success');

A The selector '#result' is incorrect and does not exist in the DOM.

B The test does not wait for the result to appear after clicking the button.

C The click command is not chained properly causing a syntax error.

D Cypress does not support assertions on text content.

💡 Hint

Think about asynchronous behavior after clicking a button.

After clicking the button, the result may take time to appear. Without an explicit or implicit wait, Cypress tries to find '#result' immediately, causing intermittent failures.

🧠 Conceptual

advanced

What is the main difference between cy.wait() with a number and cy.wait() with an alias?

Choose the correct explanation of how cy.wait() behaves differently when passed a number versus an alias.

A <code>cy.wait(1000)</code> waits for an element; <code>cy.wait('@alias')</code> waits for a timer.

B <code>cy.wait(1000)</code> waits for a network request; <code>cy.wait('@alias')</code> pauses for 1 second.

C <code>cy.wait(1000)</code> retries the command until success; <code>cy.wait('@alias')</code> fails immediately if request not found.

D <code>cy.wait(1000)</code> pauses for 1 second; <code>cy.wait('@alias')</code> waits for a network request to complete.

💡 Hint

Think about what cy.wait() does with numbers and with network aliases.

cy.wait(1000) is an explicit wait that pauses the test for 1 second. cy.wait('@alias') waits for a specific network request to finish before continuing.

❓ framework

expert

How to avoid flaky tests caused by cy.wait() in Cypress?

Which practice helps reduce flaky tests related to using cy.wait() for explicit waiting?

A Replace fixed <code>cy.wait()</code> times with waiting for specific elements or network calls.

B Increase all <code>cy.wait()</code> times to very high values to ensure stability.

C Remove all <code>cy.wait()</code> commands and rely only on <code>cy.get()</code>.

D Use <code>cy.wait()</code> only inside <code>beforeEach()</code> hooks.

💡 Hint

Think about what causes flakiness and how Cypress commands can wait smartly.

Fixed waits can cause tests to be slow or flaky if timing changes. Waiting for elements or network requests is more reliable and faster.