Assertion timeout customization in Cypress - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the test result with customized assertion timeout?

Consider this Cypress test snippet that checks if a button becomes visible within a custom timeout.

cy.get('#submit-btn', { timeout: 10000 }).should('be.visible')

Assuming the button appears after 8 seconds, what will be the test outcome?

Cypress

cy.get('#submit-btn', { timeout: 10000 }).should('be.visible')

A Test fails with a syntax error due to incorrect timeout usage.

B Test fails because the default timeout is 4 seconds, which is exceeded.

C Test passes because the button appears before the 10-second timeout.

D Test passes immediately without waiting for the button.

💡 Hint

Remember that the timeout option overrides the default wait time for the element.

The custom timeout of 10 seconds allows Cypress to wait up to 10 seconds for the button to appear. Since the button appears after 8 seconds, the assertion passes.

❓ assertion

intermediate

Which assertion correctly sets a custom timeout for visibility check?

Choose the correct Cypress assertion that waits up to 5 seconds for an element with id login to be visible.

A cy.get('#login', { timeout: 5000 }).should('be.visible')

B cy.get('#login').should({ timeout: 5000 }, 'be.visible')

C cy.get('#login').should('be.visible', { timeout: 5000 })

D cy.get('#login').should('be.visible').timeout(5000)

💡 Hint

Check where the timeout option is passed in Cypress commands.

The timeout option must be passed as an option to cy.get(), not inside should(). Option A correctly sets the timeout.

🔧 Debug

advanced

Why does this assertion timeout too early despite custom timeout?

Review this Cypress test code:

cy.get('#profile', { timeout: 10000 }).should('contain.text', 'User')

The element #profile appears after 9 seconds with text 'User Profile'. The test fails with a timeout error after 4 seconds. Why?

Cypress

cy.get('#profile', { timeout: 10000 }).should('contain.text', 'User')

A The timeout option on <code>cy.get</code> applies only to element existence, not to assertion retries.

B The default timeout for <code>should</code> assertions is 4 seconds and is not overridden by <code>cy.get</code> timeout.

C The timeout option is ignored because <code>contain.text</code> is not a valid assertion.

D The test fails because the text 'User' does not exactly match 'User Profile'.

💡 Hint

Consider how Cypress handles timeouts for commands versus assertions.

The timeout option on cy.get controls how long Cypress waits for the element to appear. However, the should assertion has its own default retry timeout (usually 4 seconds). Since the element appears but the assertion text check fails initially, the assertion times out after 4 seconds.

❓ framework

advanced

How to globally customize assertion timeout in Cypress?

Which configuration change globally sets the default assertion timeout to 8000 milliseconds in Cypress?

A Add <code>assertionTimeout: 8000</code> in <code>cypress.json</code> root level.

B Add <code>defaultCommandTimeout: 8000</code> in <code>cypress.config.js</code> under <code>e2e</code> section.

C Add <code>defaultAssertionTimeout: 8000</code> in <code>cypress.config.js</code> under <code>e2e</code> section.

D Add <code>timeout: 8000</code> in <code>package.json</code> under <code>scripts</code>.

💡 Hint

Check Cypress official docs for global timeout settings.

The defaultCommandTimeout setting in cypress.config.js controls the default timeout for commands and assertions globally. Option B correctly sets it.

🧠 Conceptual

expert

Why might increasing assertion timeout cause flaky tests?

Increasing assertion timeout can help tests wait longer for conditions. However, what is a common risk of setting very high assertion timeouts in Cypress tests?

A Tests will always fail faster, causing more false negatives.

B Assertions will stop retrying and only check once immediately.

C Cypress will ignore the timeout and use default values anyway.

D Tests may become slower and mask real failures by waiting too long for conditions that never happen.

💡 Hint

Think about test speed and reliability trade-offs.

Setting very high assertion timeouts can slow down tests and hide real problems by waiting too long for conditions that might never be met, leading to flaky or unreliable test suites.