cy.wait() for explicit waiting in Cypress - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to wait explicitly for 2 seconds before continuing the test.

Cypress

cy.[1](2000);

Drag options to blanks, or click blank then click option'

Apause

Bwait

Cdelay

Dsleep

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'pause' or 'sleep' instead of 'wait'.

Not specifying the time in milliseconds.

The cy.wait() command pauses the test for the specified milliseconds. Here, 2000 means 2 seconds.

2fill in blank

medium

Complete the code to wait explicitly for 500 milliseconds before clicking the button.

Cypress

cy.[1](500);
cy.get('#submit').click();

Drag options to blanks, or click blank then click option'

Adelay

Bsleep

Cpause

Dwait

Attempts:

3 left

💡 Hint

Common Mistakes

Using non-Cypress commands like 'sleep' or 'delay'.

Forgetting to specify the wait time in milliseconds.

cy.wait(500) pauses the test for half a second before the next command runs.

3fill in blank

hard

Fix the error in the code to wait explicitly for 1 second before checking the text.

Cypress

cy.wait([1]);
cy.get('.message').should('contain', 'Success');

Drag options to blanks, or click blank then click option'

A1000

B'1000ms'

C'1s'

D1

Attempts:

3 left

💡 Hint

Common Mistakes

Passing a string with units like '1000ms' or '1s'.

Passing a number without units but too small like 1.

The cy.wait() command expects a number in milliseconds, so 1000 is correct.

4fill in blank

hard

Fill both blanks to wait explicitly for 3 seconds and then check if the button is visible.

Cypress

cy.[1]([2]);
cy.get('button#start').should('be.visible');

Drag options to blanks, or click blank then click option'

Await

Bpause

C3000

D5000

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'pause' instead of 'wait'.

Using 5000 instead of 3000 for the wait time.

cy.wait(3000) pauses the test for 3 seconds before checking the button visibility.

5fill in blank

hard

Fill all three blanks to wait explicitly for 4 seconds, then get the input field and type 'Hello'.

Cypress

cy.[1]([2]);
cy.get('[3]').type('Hello');

Drag options to blanks, or click blank then click option'

Await

B4000

C#name-input

D.input-field

Attempts:

3 left

💡 Hint

Common Mistakes

Using a class selector instead of the id selector for the input.

Using incorrect wait time or command.

The code waits 4 seconds, then selects the input with id name-input and types 'Hello'.

Practice

1. What is the main purpose of using cy.wait() in Cypress tests?

easy

A. To pause the test for a specific time or until a request finishes

B. To skip a test step temporarily

C. To restart the test from the beginning

D. To automatically retry failed assertions

Solution

1. Step 1: Understand the function of cy.wait()

   cy.wait() is used to pause the test execution either for a fixed time or until a network request completes.

2. Step 2: Compare with other options

   Skipping steps, restarting tests, or retrying assertions are not functions of cy.wait().

3. Final Answer:

   To pause the test for a specific time or until a request finishes -> Option A

4. Quick Check:

   Pause test = cy.wait() [OK]

Hint: Remember: cy.wait() pauses test execution explicitly [OK]

Common Mistakes:

• Thinking cy.wait() skips test steps
• Confusing cy.wait() with test retries
• Assuming cy.wait() restarts tests

2. Which of the following is the correct syntax to wait explicitly for 3 seconds in Cypress?

easy

A. cy.wait(3s)

B. cy.wait('3000')

C. cy.wait(3)

D. cy.wait(3000)

Solution

1. Step 1: Check the correct argument type for cy.wait()

   The argument must be a number representing milliseconds, so 3000 means 3 seconds.

2. Step 2: Validate each option

   cy.wait(3000) uses a number 3000 correctly. cy.wait('3000') uses a string which is invalid. cy.wait(3) uses 3 which means 3 milliseconds, not 3 seconds. cy.wait(3s) uses an invalid unit '3s'.

3. Final Answer:

   cy.wait(3000) -> Option D

4. Quick Check:

   Milliseconds number = cy.wait(3000) [OK]

Hint: Use milliseconds as number, no quotes or units [OK]

Common Mistakes:

• Passing time as string instead of number
• Using seconds instead of milliseconds
• Adding units like 's' inside wait argument

3. Consider this Cypress code snippet:

cy.intercept('GET', '/api/data').as('getData')
cy.visit('/dashboard')
cy.wait('@getData')
cy.get('#result').should('be.visible')

What will cy.wait('@getData') do here?

medium

A. Pause test until the GET request to '/api/data' finishes

B. Pause test for 1 second regardless of request

C. Immediately continue without waiting

D. Cause a syntax error because of wrong alias

Solution

1. Step 1: Understand alias usage with cy.wait()

   The alias '@getData' refers to the intercepted GET request to '/api/data'. Using cy.wait('@getData') waits for that request to complete.

2. Step 2: Check other options

   It does not wait a fixed time (not 1 second), nor does it continue immediately. The alias is correctly defined, so no syntax error.

3. Final Answer:

   Pause test until the GET request to '/api/data' finishes -> Option A

4. Quick Check:

   Wait for request alias = cy.wait('@getData') [OK]

Hint: Wait for alias pauses until that request finishes [OK]

Common Mistakes:

• Confusing alias wait with fixed time wait
• Assuming immediate continuation
• Mistaking alias syntax causing errors

4. You wrote this Cypress code:

cy.wait(5000)
cy.get('.submit-btn').click()

But the test fails because the button is not clickable after 5 seconds. What is the likely problem?

medium

A. The selector '.submit-btn' is invalid syntax

B. The wait time 5000 is too long and causes timeout

C. Using fixed wait instead of waiting for the button to be ready

D. cy.wait() cannot be used before cy.get()

Solution

1. Step 1: Analyze the use of fixed wait

   Waiting a fixed 5 seconds does not guarantee the button is ready or clickable. The button might appear later or be disabled.

2. Step 2: Consider better waiting strategy

   Better to wait for the button to exist or be enabled using assertions or wait for network requests instead of fixed time.

3. Final Answer:

   Using fixed wait instead of waiting for the button to be ready -> Option C

4. Quick Check:

   Fixed wait ≠ reliable readiness [OK]

Hint: Wait for element readiness, not fixed time [OK]

Common Mistakes:

• Assuming fixed wait always works
• Blaming selector syntax without checking
• Thinking cy.wait() must come after cy.get()

5. You want to wait for two different API calls to finish before checking the page content. Which code correctly waits for both requests using cy.wait()?

hard

A. cy.wait('@apiCall1', '@apiCall2')

B. cy.wait('@apiCall1'); cy.wait('@apiCall2')

C. cy.wait(['@apiCall1', '@apiCall2'])

D. cy.wait('@apiCall1') && cy.wait('@apiCall2')

Solution

1. Step 1: Understand how to wait for multiple aliases

   Cypress requires chaining cy.wait() calls sequentially for different aliases to ensure both requests complete.

2. Step 2: Evaluate each option

   cy.wait('@apiCall1'); cy.wait('@apiCall2') correctly chains the waits using semicolon separation, which queues them in Cypress. cy.wait('@apiCall1', '@apiCall2') passes multiple arguments incorrectly. cy.wait('@apiCall1') && cy.wait('@apiCall2') uses logical AND which does not chain Cypress commands properly. cy.wait(['@apiCall1', '@apiCall2']) uses an unsupported array argument.

3. Final Answer:

   cy.wait('@apiCall1'); cy.wait('@apiCall2') -> Option B

4. Quick Check:

   Chained waits = cy.wait('@apiCall1'); cy.wait('@apiCall2') [OK]

Hint: Chain cy.wait() calls for multiple aliases [OK]

Common Mistakes:

• Passing multiple aliases as separate arguments
• Using && instead of proper chaining
• Using unsupported array of aliases