Home › Blog › Cypress Interview Questions (2026): 32 Questions With Answers, Updated for Cypress 16

Cypress Interview Questions (2026): 32 Questions With Answers, Updated for Cypress 16

Cypress interviews test whether you understand how Cypress runs your tests: the command queue, retry-ability, network control with cy.intercept, login caching with cy.session, test isolation, cross-origin rules, component testing and CI parallelization. As of November 17, 2026 the current release is Cypress 16.3.0 (November 10, 2026), and Cypress 16.0, released September 1, 2026, brought breaking changes interviewers now ask about.

Cypress interviews test whether you understand how Cypress runs your tests: the command queue, retry-ability, network control with cy.intercept, login caching with cy.session, test isolation, cross-origin rules, component testing and CI parallelization. As of November 17, 2026 the current release is Cypress 16.3.0 (November 10, 2026), and Cypress 16.0, released September 1, 2026, brought breaking changes interviewers now ask about. Below are 32 questions by level with concise answers, five troubleshooting scenarios and how interviews test the tool.

Cypress in November 2026: facts to know

FactDetail (Cypress changelog and docs)
Current version16.3.0, released November 10, 2026
Node.jsCypress 16 requires Node.js 22.x, 24.x or 26 and later
BrowsersChrome-family browsers (Chrome, Chromium, Edge), Electron and Firefox; WebKit behind experimentalWebKitSupport
LanguageJavaScript and TypeScript; test code runs inside the browser
Cypress 16 changesCypress.env() removed in favour of Cypress.expose() and cy.env(); cy.exec() and cy.end() removed; native network interception in Chrome-family browsers; cy.type() keystroke delay now 0
Earlier milestones12.0 (December 2022): cy.session and cy.origin generally available, test isolation on by default, cy.server() and cy.route() removed. 13.0 (August 2023): Test Replay, video off by default

Fundamentals

  1. How is Cypress's architecture different from Selenium's? Cypress runs test code inside the browser, in the same run loop as the app, with a Node.js process alongside for tasks, files and network handling. There is no WebDriver layer, so tests get direct access to the DOM, window and network. The trade-offs are JavaScript only and one browser at a time; compare our Selenium interview questions.
  2. Are Cypress commands promises? No. Commands are queued and run later, one after another. cy.get('button') returns a chainable, not an element, so you can't assign its result or await it; use .then(), aliases or assertions to work with values.
  3. What is retry-ability? Queries such as cy.get(), .find() and .contains() re-run with their assertions until they pass or defaultCommandTimeout (4 seconds) runs out. Actions such as .click() are not retried. Cypress 16 made cookie and storage commands retry-able queries too.
  4. Implicit or explicit assertions? Implicit: cy.get('.toast').should('contain', 'Saved'). Explicit: expect() inside .should(callback), which retries, or inside .then(), which does not.
  5. How should you select elements? With dedicated attributes such as data-cy or data-test, or cy.contains() for user-visible text. Avoid classes and DOM structure that change with styling.
  6. What are fixtures? Static test data in the fixtures folder: cy.fixture('user.json'), or a stubbed response with cy.intercept('GET', '/api/user', { fixture: 'user.json' }).
  7. How do aliases and cy.wait work? .as('save') names an intercept, element or value; cy.wait('@save') waits for that request and yields it for assertions on the request and response.
  8. What does test isolation do? On by default since Cypress 12: before each test, Cypress clears the page, cookies, local storage and session storage, so tests cannot depend on each other. Set testIsolation: false on a suite only with a strong reason.
  9. Where does configuration live? In cypress.config.js or .ts, using defineConfig({ e2e: { baseUrl, setupNodeEvents } }), with separate e2e and component sections. The old cypress.json file was replaced in Cypress 10.
  10. How do you write custom commands? Cypress.Commands.add('login', (email, pw) => { ... }) for repeated flows. Cypress.Commands.overwrite changes an existing command, and overwriteQuery changes a query.
  11. What is the difference between cypress open and cypress run? open starts the interactive runner with time-travel snapshots of each command, for writing and debugging. run executes headlessly for CI, with screenshots on failure and reporter output.

Intermediate

  1. How do you use cy.intercept? To spy on, stub or modify the app's requests: cy.intercept('POST', '/api/orders', { statusCode: 201, body: { id: 1 } }).as('create'). Use req.reply() or req.continue(res => ...) for dynamic handling, and register the intercept before the action that fires the request.
  2. What does cy.session do? It caches and restores cookies, local storage and session storage for a login: cy.session(email, () => login(email), { validate }). Pass cacheAcrossSpecs: true to reuse it across spec files. It is how you keep test isolation without logging in through the UI every time.
  3. cy.request or cy.intercept? cy.request() sends an HTTP request from Cypress itself, outside the app, for seeding data or API checks. cy.intercept() watches or stubs requests the app makes.
  4. What is cy.task for? Running code in the Node.js process registered in setupNodeEvents: database seeding, file access, anything outside the browser. Cypress 16 removed cy.exec(), so shell work moves into tasks.
  5. How do environment values work in Cypress 16? Cypress.env() is gone. Use Cypress.expose() for non-sensitive values the browser may read and cy.env() for sensitive values that stay in the Node process; the env key in per-test config overrides is no longer supported.
  6. How do you test across origins? Each test is bound to one superdomain, so wrap steps on another origin in cy.origin('https://login.example.com', () => { ... }). Since Cypress 14, navigating between subdomains also needs cy.origin().
  7. How do you work with iframes? For same-origin iframes, get the body and wrap it: cy.get('iframe').its('0.contentDocument.body').should('not.be.empty').then(cy.wrap). There is still no built-in command to switch into an iframe.
  8. Can Cypress handle new tabs? Cypress controls one browser at a time. For a target=_blank link, assert the href or remove the target attribute; for real multi-tab flows the docs point to the @cypress/puppeteer plugin.
  9. How do you test hover and keyboard behaviour? There is no cy.hover(): most actions simulate events in JavaScript, so use .trigger('mouseover') and assert the effect. cy.press(), added in 14.3, sends a native Tab key press.
  10. What is component testing in Cypress? Mounting one React, Vue, Angular or Svelte component in a real browser with cy.mount(), using your dev server config. It is faster than end-to-end tests for UI states and edge cases.
  11. How do retries work? retries: { runMode: 2, openMode: 0 } retries failures in CI only. Cypress Cloud flags flaky tests, and Test Replay shows the DOM, network and console of a failed CI run.

Experienced and senior

  1. How do you parallelize a Cypress suite? cypress run --record --parallel with Cypress Cloud balances spec files across CI machines. Without Cloud, split specs across jobs yourself and keep spec files similar in length.
  2. Why avoid cy.wait(5000)? A fixed wait is slow and still flaky. Wait on an aliased request or assert the state you need, and let retry-ability do the waiting.
  3. Why does Cypress discourage conditional testing? The DOM can change between the check and the action, so if logic on page state produces random results. Make the state deterministic with seeded data or stubs instead.
  4. How do you avoid detached DOM errors? Since Cypress 12, queries re-query when the element re-renders. You can still hit the error by holding an element inside .then() and acting on it after a re-render, so keep chains of queries rather than storing elements.
  5. How do you test SSO or OAuth logins? Don't drive a third-party login page; Cypress is not built for scripting third-party sites. Get a token through cy.request() to your auth endpoint or a test-only route, and wrap it in cy.session().
  6. How would you structure a large Cypress project? Custom commands or small page helpers, data-cy attributes agreed with developers, API seeding with cy.request and cy.task, cy.session logins, per-environment config, tags with the @cypress/grep plugin, and a small end-to-end layer over component and API tests.
  7. What do you check when upgrading to Cypress 16? Node.js 22 or later; replace Cypress.env(); move cy.exec() to cy.task(); drop .end(); re-run intercept tests, because native interception no longer reports req.httpVersion or compression headers; and check tests that relied on the old 10 ms typing delay. The migration guide lists each change.
  8. When would you choose Cypress over Playwright? When the team writes JavaScript, values the interactive runner and time-travel debugging, and tests one app in Chrome-family browsers and Firefox. For WebKit, multiple tabs or other languages, see our Playwright interview questions.
  9. What is Cypress not designed for? Its trade-offs page lists indexing the web, spidering links, performance testing and scripting third-party sites. For load testing, use a tool built for it; see our JMeter interview questions.
  10. How do you test WebSocket features? Cypress lets WebSocket connections work but does not intercept their frames. Assert on what the user sees, stub the client messaging layer, or drive a second client from Node with cy.task.

Five troubleshooting scenarios

How interviews test Cypress

Companies don't publish question banks, but QA automation candidates commonly report a live task (automate a flow on a demo app with stubbed network calls), a review of a flaky spec, and a framework and CI discussion. Because Cypress tests are JavaScript, expect closures, promises and async behaviour; our JavaScript interview questions cover them. Strategy questions, such as what belongs in end-to-end tests at all, are in our QA engineer interview questions.

Where CoPilot Interview fits

CoPilot Interview is an AI interview assistant whose free AI mock interview builds Cypress and QA automation questions from your résumé and the job description, reads them aloud and scores each spoken answer out of 10. The browser demo at /try has 145 practice questions in 10 tracks, scored out of 10, with no signup. The free plan gives 15 minutes a day of live help in sessions of up to 15 minutes, with AI mock interviews included; Standard costs $24.99 a month and Pro $39.99. For role-specific prep, see our guide to practicing QA engineer interviews with AI. Live coding tasks, take-homes and online assessments usually forbid outside help, so prepare for those; in any live interview, follow your employer's rules.

Disclosure: CoPilot Interview is our product, so weigh what we say about it accordingly.

Frequently asked questions

Is Cypress still worth learning in 2026?

If the jobs you want list it, yes. Cypress shipped 16.0 in September 2026 and 16.3.0 in November, and the concepts it teaches, such as retry-ability, network stubbing and isolation, transfer to other tools.

Can Cypress test Safari?

Not Safari itself. Cypress supports Chrome-family browsers, Electron and Firefox, and runs WebKit, Safari's engine, behind the experimentalWebKitSupport flag.

Does Cypress support languages other than JavaScript?

No. Tests run in the browser, so Cypress supports JavaScript and TypeScript only.

Can Cypress do API testing?

Yes, with cy.request and assertions on status, headers and body. For broader API test design, see our <a href="/blog/api-testing-interview-questions">API testing interview questions</a>.

What is the latest Cypress version?

As of November 17, 2026, Cypress 16.3.0, released November 10, 2026. It requires Node.js 22, 24 or 26 and later.

Practice this interview before the real one

The AI mock interview builds questions from your resume and the job description, reads them aloud and scores each spoken answer out of 10. Included on the free plan.

Start a mock interview