Waiting for requests (cy.wait with alias) 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 response.status after the cy.wait('@getUser') command resolves?

Cypress

cy.intercept('GET', '/api/user').as('getUser');
cy.visit('/profile');
cy.wait('@getUser').then(({ response }) => {
  const status = response.status;
  cy.wrap(status).as('statusCode');
});
cy.get('@statusCode').then(statusCode => {
  console.log(statusCode);
});

A 200

B undefined

C 404

D 500

💡 Hint

The intercept simulates a successful GET request to '/api/user'.

The intercept command sets up a stub for the GET request to '/api/user' which by default returns a 200 status. The cy.wait('@getUser') waits for this request and the response status is 200.

❓ assertion

intermediate

Which assertion correctly waits for and verifies the response body property?

You want to wait for the API call aliased as '@fetchData' and assert that the response body has a property success set to true. Which option correctly does this?

A cy.get('@fetchData').should('have.property', 'response.body.success', true);

B cy.wait('@fetchData').should('have.property', 'success', true);

C cy.wait('@fetchData').its('response.body.success').should('eq', true);

D cy.wait('@fetchData').then(({ response }) => expect(response.body.success).to.be.true);

💡 Hint

Use cy.wait with its to access nested properties.

Option C correctly waits for the alias and accesses the nested property using its, then asserts it equals true. Option C is invalid because should does not work directly on the alias object like that. Option C uses cy.get which is for DOM elements, not aliases. Option C correctly accesses response.body by destructuring the argument.

🔧 Debug

advanced

Why does this test fail to wait for the request?

This Cypress test fails intermittently because cy.wait('@postData') times out. What is the most likely reason?

Cypress

cy.intercept('POST', '/api/data').as('postData');
cy.visit('/form');
cy.get('button[type=submit]').click();
cy.wait('@postData');

A The POST request happens before the intercept is set up.

B The button click does not trigger the POST request.

C The alias '@postData' is misspelled in cy.wait.

D cy.wait cannot be used with POST requests.

💡 Hint

Check if the user action triggers the network request.

If the button click does not trigger the POST request, cy.wait('@postData') will time out waiting for a request that never happens. The intercept and alias are correctly set up before the visit, and cy.wait works with POST requests. The alias spelling is correct.

🧠 Conceptual

advanced

What is the main benefit of using cy.wait with an alias in Cypress tests?

Why do testers use cy.wait('@alias') instead of arbitrary cy.wait(time) delays?

A It retries the request automatically if it fails.

B It pauses the test for a fixed time to avoid race conditions.

C It disables all other network requests during the wait.

D It waits exactly for the network request to finish, making tests more reliable and faster.

💡 Hint

Think about waiting for real events vs fixed delays.

Using cy.wait with an alias waits for the actual network request to complete, avoiding flaky tests caused by guessing wait times. Fixed delays can be too short or too long, making tests unreliable or slow. Cypress does not retry requests automatically with cy.wait, nor does it disable other requests.

❓ framework

expert

In a complex test suite, how can you wait for multiple requests with different aliases before proceeding?

You have three API calls aliased as '@getUser', '@getPosts', and '@getComments'. You want to wait for all three to finish before continuing the test. Which code snippet correctly waits for all three requests?

A cy.wait(['@getUser', '@getPosts', '@getComments']);

B cy.wait('@getUser'); cy.wait('@getPosts'); cy.wait('@getComments');

C Promise.all([cy.wait('@getUser'), cy.wait('@getPosts'), cy.wait('@getComments')]);

D cy.wait('@getUser && @getPosts && @getComments');

💡 Hint

Check Cypress docs for waiting on multiple aliases at once.

Option A uses an array of aliases in cy.wait, which waits for all listed requests to complete before continuing. Option A waits sequentially but is less efficient and can cause timing issues. Option A is invalid because cy.wait returns Cypress chainables, not promises usable with Promise.all. Option A is invalid syntax.