Timeout configuration in Cypress - Build an Automation Script

Verify page loads within custom timeout

Preconditions (2)

Step 1: Open the test website URL with a custom page load timeout of 10000 milliseconds

Step 2: Wait for the main content element with id 'main-content' to be visible

Step 3: Verify that the main content is visible within the timeout

✅ Expected Result: The main content element is visible within 10 seconds, and the test passes without timeout errors

Automation Requirements - Cypress

Assertions Needed:

Assert that the element with id 'main-content' is visible within the custom timeout

Best Practices:

Use Cypress commands with timeout option

Avoid hardcoded waits like cy.wait() for timing

Use meaningful selectors (id, data-cy attributes)

Use Cypress default timeout configuration override only when necessary

Automated Solution

Cypress

describe('Timeout configuration test', () => {
  it('should load main content within custom timeout', () => {
    cy.visit('https://example.com', { timeout: 10000 });
    cy.get('#main-content', { timeout: 10000 }).should('be.visible');
  });
});

The test uses cy.visit with a timeout option set to 10000 milliseconds to allow the page to load up to 10 seconds.

Then it uses cy.get with the same timeout to wait for the element with id main-content to become visible.

This ensures the test waits explicitly for the element without using fixed delays, making it reliable and efficient.

Common Mistakes - 3 Pitfalls

Using cy.wait(10000) to wait for page load

Not setting timeout on cy.get() leading to flaky tests

Using overly complex or brittle selectors instead of simple ids

Bonus Challenge

Now add data-driven testing with 3 different URLs and verify main content loads within timeout for each

Show Hint

Practice

1. What does the { timeout: 10000 } option do in a Cypress command?

easy

A. It disables the timeout for that command.

B. It makes Cypress skip the command after 10 seconds.

C. It repeats the command every 10 seconds.

D. It sets Cypress to wait up to 10 seconds before failing the command.

Solution

1. Step 1: Understand the timeout option in Cypress

   The { timeout: ms } option tells Cypress how long to wait for a command to succeed before failing.

2. Step 2: Interpret the value 10000

   10000 milliseconds equals 10 seconds, so Cypress waits up to 10 seconds.

3. Final Answer:

   It sets Cypress to wait up to 10 seconds before failing the command. -> Option D

4. Quick Check:

   Timeout option = wait time before failure [OK]

Hint: Timeout sets max wait time before failure [OK]

Common Mistakes:

• Thinking timeout disables the command
• Assuming timeout repeats the command
• Confusing timeout with delay or skip

2. Which of the following is the correct syntax to set a 5-second timeout for a cy.get() command?

easy

A. cy.get('.btn', { timeout: 5000 })

B. cy.get('.btn').timeout(5000)

C. cy.get('.btn', timeout=5000)

D. cy.get('.btn').setTimeout(5000)

Solution

1. Step 1: Recall Cypress command options syntax

   Cypress commands accept options as an object inside curly braces after the selector.

2. Step 2: Identify correct object syntax

   The correct syntax uses { timeout: 5000 } as the second argument to cy.get().

3. Final Answer:

   cy.get('.btn', { timeout: 5000 }) -> Option A

4. Quick Check:

   Options object uses curly braces and key-value pairs [OK]

Hint: Use curly braces for options object in commands [OK]

Common Mistakes:

• Using equals sign instead of colon in options
• Calling timeout as a method on command
• Passing timeout outside options object

3. What will happen if the following Cypress code runs and the element .submit-btn appears after 7 seconds?

cy.get('.submit-btn', { timeout: 5000 }).click()

medium

A. The test will pass because the element appears eventually.

B. The test will fail because the timeout is shorter than the wait time.

C. The test will wait indefinitely for the element.

D. The test will skip the click and continue.

Solution

1. Step 1: Analyze the timeout value

   The timeout is set to 5000 milliseconds (5 seconds), so Cypress waits up to 5 seconds for the element.

2. Step 2: Compare element appearance time

   The element appears after 7 seconds, which is longer than the 5-second timeout.

3. Final Answer:

   The test will fail because the timeout is shorter than the wait time. -> Option B

4. Quick Check:

   Timeout less than wait time causes failure [OK]

Hint: Timeout must be >= element load time to pass [OK]

Common Mistakes:

• Assuming test waits longer than timeout
• Thinking test passes if element appears later
• Believing timeout disables failure

4. Identify the error in this Cypress code snippet:

cy.get('.nav-link', { timeout: '3000' }).click()

medium

A. Timeout value should be a number, not a string.

B. The selector '.nav-link' is invalid.

C. The click() command cannot follow get().

D. Timeout option is not supported in cy.get().

Solution

1. Step 1: Check the timeout option type

   The timeout value must be a number representing milliseconds, not a string.

2. Step 2: Validate other parts

   The selector is valid, click() can follow get(), and timeout is supported in cy.get().

3. Final Answer:

   Timeout value should be a number, not a string. -> Option A

4. Quick Check:

   Timeout must be numeric type [OK]

Hint: Timeout must be a number, not quoted string [OK]

Common Mistakes:

• Passing timeout as a string
• Misunderstanding selector validity
• Thinking click() is invalid after get()

5. You want to wait up to 8 seconds for a button with class .save-btn to appear, but only 3 seconds for a loading spinner .spinner to disappear. Which code correctly sets these timeouts in Cypress?

hard

A. cy.get('.save-btn').click({ timeout: 8000 }); cy.get('.spinner').should('not.exist', { timeout: 3000 });

B. cy.get('.save-btn', { timeout: 3000 }).click(); cy.get('.spinner', { timeout: 8000 }).should('not.exist');

C. cy.get('.save-btn', { timeout: 8000 }).click(); cy.get('.spinner', { timeout: 3000 }).should('not.exist');

D. cy.get('.save-btn').click(); cy.get('.spinner').should('not.exist'); cy.wait(8000);

Solution

1. Step 1: Set timeout for button appearance

   Use { timeout: 8000 } in cy.get() to wait up to 8 seconds for .save-btn.

2. Step 2: Set timeout for spinner disappearance

   Use { timeout: 3000 } in should('not.exist') to wait up to 3 seconds for .spinner to disappear.

3. Final Answer:

   cy.get('.save-btn', { timeout: 8000 }).click(); cy.get('.spinner', { timeout: 3000 }).should('not.exist'); -> Option C

4. Quick Check:

   Set timeout in get() and should() options correctly [OK]

Hint: Set timeout per command in options object [OK]

Common Mistakes:

• Passing timeout inside click() or should() incorrectly
• Swapping timeout values for elements
• Using fixed wait instead of timeout option