Questions
3 of 7
1What is Cypress?
2What are the advantages and disadvantages of using Cypress?
3What browsers does Cypress support?
4Explain the architecture of Cypress.
5How Cypress Differs from Traditional Testing Tools
6What is a Fixture in Cypress?
7What is the difference between cy.fixture() and cy.readFile()?
CypressCypress
Basics
Test Writing and Syntax
Error Handling & Debugging
Locators and Interactions
Assertions
Cypress Commands
Network Requests
Test Organization & Reusability
Configuration
CI/CD Integration
Authentication Handling
Screenshots & Videos
03 / 07

What browsers does Cypress support?

Chromium-based Browsers and Firefox are supported
  1. 1

    Google Chrome

  2. 2

    Microsoft Edge (Chromium version)

  3. 3

    Brave

  4. 4

    Electron (bundled with Cypress by default)

  5. 5

    Firefox (Stable, Developer Edition, Nightly)

Partial/Experimental Support
  1. 1

    WebKit / Safari – Not officially supported: Safari is not currently supported because Cypress relies on the Chrome DevTools Protocol (CDP), which WebKit doesn’t use.

  2. 2

    Internet Explorer – Not supported

Difficulty: 4/10
Topics: browser support, cross-browser testing, Cypress limitations

Scenario Questions

0-2 years experience
  1. 1

    If you need to run a Cypress test on Chrome and Firefox, how would you configure the test runner?

  2. 2

    What happens when you try to execute a Cypress test on Safari today, and why?

2-5 years experience
  1. 1

    You added a test that passes locally on Chrome but fails on Edge in CI. Walk me through how you'd debug the browser compatibility issue.

  2. 2

    Explain the trade‑offs of using Cypress's built‑in Electron versus real browsers for a cross‑browser test suite.

5-8 years experience
  1. 1

    Our product must support Chrome, Firefox, Edge, and Safari on desktop and mobile. How would you design a Cypress testing strategy given its current browser support limitations?

  2. 2

    If Cypress releases experimental support for a new browser, what factors would you evaluate before adopting it in a large, flaky‑prone test suite?

8+ years experience
  1. 1

    We are planning a migration from Selenium to Cypress across multiple teams, but we still need to support legacy browsers like Safari 10. How would you architect the migration while handling Cypress's browser support gaps?

  2. 2

    At an organization‑wide level, how would you set policies for browser coverage in Cypress tests to balance test reliability, maintenance cost, and coverage of user‑facing browsers?

Follow-up Questions

  • ❓How would you verify that a test behaves the same across the supported browsers?
  • ❓What CI configuration changes are needed to run Cypress on multiple browsers?
  • ❓Can you describe a situation where Cypress's browser support might block a testing requirement?