Timeout configuration in Cypress - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the test result with default timeout?

Consider this Cypress test code snippet:

describe('Timeout test', () => {
  it('waits for element with default timeout', () => {
    cy.visit('https://example.cypress.io')
    cy.get('.non-existent-element').should('be.visible')
  })
})

What will happen when this test runs?

Cypress

describe('Timeout test', () => {
  it('waits for element with default timeout', () => {
    cy.visit('https://example.cypress.io')
    cy.get('.non-existent-element').should('be.visible')
  })
})

A Test fails after about 4 seconds with a timeout error because the element does not appear.

B Test passes immediately because Cypress ignores missing elements by default.

C Test runs forever because there is no timeout set for cy.get().

D Test fails immediately with a syntax error due to missing timeout option.

💡 Hint

Think about Cypress default command timeout behavior when an element is not found.

By default, Cypress waits up to 4 seconds for an element to appear before failing the test with a timeout error.

❓ assertion

intermediate

Which assertion correctly waits up to 10 seconds?

You want to wait up to 10 seconds for a button with id 'submit' to become visible. Which Cypress command and assertion combination achieves this?

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

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

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

D cy.get('#submit').should('be.visible').timeout(10000)

💡 Hint

Timeout option goes inside cy.get() command, not inside should().

The timeout option must be passed as an argument to cy.get() to extend the wait time for the element to appear.

🔧 Debug

advanced

Why does this test fail immediately despite timeout?

Examine this Cypress test:

cy.get('.loading', { timeout: 15000 })
  .should('not.exist')

The element '.loading' appears for 10 seconds then disappears. The test fails immediately. Why?

Cypress

cy.get('.loading', { timeout: 15000 }).should('not.exist')

A The selector '.loading' is invalid, causing immediate failure.

B The timeout value 15000 is too high and causes a syntax error.

C Timeout option is ignored because should('not.exist') does not support waiting.

D cy.get() waits for the element to appear, but since it exists, should('not.exist') fails immediately.

💡 Hint

Think about what cy.get() waits for and what the assertion expects.

cy.get() waits for the element to appear up to 15 seconds. Since the element exists, the assertion should('not.exist') fails immediately because the element is present.

❓ framework

advanced

How to globally increase default command timeout in Cypress?

You want all Cypress commands to wait up to 20 seconds by default instead of 4 seconds. Which configuration change achieves this?

A Set Cypress.config('defaultCommandTimeout', 20000) inside each test file.

B Add "defaultCommandTimeout": 20000 in cypress.config.js under the e2e object.

C Use cy.setTimeout(20000) at the start of every test.

D Add timeout: 20000 to every cy.get() command manually.

💡 Hint

Global settings go in the config file, not inside test code.

The correct way is to set defaultCommandTimeout in cypress.config.js to change the default timeout globally for all commands.

🧠 Conceptual

expert

Why is setting very high timeouts globally risky?

What is a main risk of setting a very high defaultCommandTimeout (e.g., 2 minutes) globally in Cypress tests?

A Tests may take much longer to fail, slowing feedback and hiding real issues.

B Cypress will ignore all timeouts and run tests instantly.

C It causes syntax errors in test files due to invalid config values.

D It disables retries and causes tests to fail immediately.

💡 Hint

Think about test speed and feedback when waiting too long for failures.

Setting very high timeouts delays failure detection, making tests slower and feedback less immediate, which can hide real problems.