What are the advantages and disadvantages of using Cypress?

Cypress is a modern, open-source end-to-end testing framework built specifically for web applications. It allows developers and QA engineers to write and run tests directly in the browser, providing fast, reliable, and easy-to-understand testing workflows.

Advantages of Cypress:

1
Cypress runs inside the browser, alongside your application. Tests are fast and consistent—no flakiness from waiting or timing issues.
2
No need to add manual waits or sleeps. Cypress automatically waits for elements to appear and for commands to finish.
3
Tests re-run automatically when you save changes.
4
Time travel lets you hover over commands in the UI to see what happened at each step.
5
Developer-friendly error messages. Integration with Chrome DevTools makes it easy to debug failures.
6
No need for additional tools like WebDriver. Works out of the box with a simple npm install cypress.
7
Built-in support to intercept, stub, and spy on API calls using cy.intercept().
8
Automatically captures screenshots on failure. Can record full test runs as videos for CI debugging.
9
Tons of plugins and extensions to enhance capabilities. Constant updates and good documentation.

Disadvantages of Cypress:

1
Primarily supports Chromium-based browsers (Chrome, Edge) and Firefox. No support for Safari or Internet Explorer.
2
Tests run in a single browser tab. Cypress doesn’t support multi-tab or multi-window testing.
3
Cross-origin (CORS) tests can be tricky and limited, though recent updates (Cypress v12+) have improved this.
4
Doesn’t emulate mobile devices as well as tools like Selenium + Appium. Mobile viewports can be simulated, but no real device testing.
5
Requires workarounds or plugins to test file handling features.
6
You must write your tests in JavaScript or TypeScript—no support for Java, Python, etc.

Difficulty: 5/10

Topics: test reliability, parallel execution, tooling integration

Scenario Questions

0-2 years experience

1
If you need to test a simple login form that redirects after submission, how would you set up a Cypress test, and what advantage does Cypress give you over a traditional Selenium script in this case?
2
What happens if a Cypress test tries to interact with an element that hasn't finished rendering? How does Cypress handle waiting, and why is that beneficial?

2-5 years experience

1
You notice that a test suite running in Cypress is flaky on CI but passes locally. Walk me through how you'd debug the issue and what disadvantages of Cypress might be causing it.
2
When adding end‑to‑end tests for a feature that makes API calls to a third‑party service, why might you choose to stub those calls in Cypress, and what trade‑offs does that introduce?

5-8 years experience

1
Our product team wants to run Cypress tests in parallel across multiple containers to reduce feedback time, but we have a large monorepo with many shared stateful services. What system‑level challenges might arise, and how would you mitigate them?
2
Explain how Cypress’s architecture (running in the same browser loop) impacts test performance and reliability at scale, and discuss any disadvantages compared to out‑of‑process runners.

8+ years experience

1
We are planning a migration from Selenium/WebDriver to Cypress across several micro‑frontend teams. What architectural considerations, cross‑team coordination, and long‑term maintenance impacts should we evaluate?
2
If the organization wants to keep a unified test strategy that includes unit, integration, and E2E tests, how would you position Cypress within that strategy, and what are the potential drawbacks of over‑relying on Cypress for all test layers?

Follow-up Questions

❓Can you give an example where Cypress’s automatic waiting actually caused a test to hide a real issue?
❓How would you decide when to use Cypress versus a lighter unit test framework?
❓What metrics would you track to determine if Cypress tests are becoming a bottleneck?