Free tools Windows power users keep installed
One-click scans. No signup required.
Cypress deprecated its bundled Electron browser as a test target in Cypress 16.0.0. Electron still runs during the deprecation period, but Cypress warns when a test targets it. Cypress says Electron will be removed in a future major version; it has not announced which version or a removal date. To prepare, install the browser you intend to test, select it in Cypress, update CI, and verify the Electron warning is gone.
What the deprecation means
The deprecation applies to using Cypress’s bundled Electron browser to run tests. It does not mean Electron has already been removed: Cypress still lists it as an accepted CLI browser during the deprecation period. Existing Electron-targeted runs continue to work and emit a warning in cypress run output and in the Cypress app.
As an Amazon Associate I earn from qualifying purchases.
After Electron is removed, explicitly selecting it with --browser electron, setting defaultBrowser: 'electron', or relying on an implicit Electron fallback will fail. Cypress’s migration guide describes removal only as occurring in a future major version; no specific release or date is published in the cited guidance.
Why Cypress is moving tests away from Electron
Cypress gives two reasons. Electron embeds a Chromium version tied to the Electron release bundled with Cypress, so its Chromium can trail stable Chrome and miss newer web-platform features and fixes. Also, embedded Chromium does not necessarily behave like the Chrome browser a site’s users run. Testing in an installed browser can better match the browser and update cadence the team wants to cover.
#1 Best Overall
This is not a promise that a suite will behave identically after changing browsers. Browser engines and versions can expose differences in application behavior and tests. Choose the target based on the users and compatibility requirements the suite is meant to represent.
Which browser should replace Electron?
Cypress documents Chrome-family browsers (Chrome, Chromium, Chrome for Testing, and Edge), Firefox, and experimental WebKit. For Chrome, Firefox, and Edge, Cypress’s documented support window is the latest three major versions. The Cypress browser guidance says it cannot launch Firefox versions older than 140 because those versions implement WebDriver BiDi incompletely; Firefox 135 was the floor for Cypress 15.0.0 through 15.18.1. Check the current Cypress browser-launching guide when pinning a browser or choosing a CI image.
Rank #2
- HTML CSS Design and Build Web Sites
- Comes with secure packaging
- It can be a gift option
| Choice | When it fits | Important qualification |
|---|---|---|
| Chrome | Use when Chrome is the browser your users rely on or the target your suite is intended to exercise. | Cypress supports the latest three major versions. Evergreen Chrome can update; Cypress documents Chrome for Testing/Chromium downloads for teams that need a specific version. |
| Chromium or Chrome for Testing | Use when you want a Chrome-family target, including a version you can pin for more controlled runs. | Confirm the selected version is compatible with your Cypress release and available in local and CI environments. |
| Edge | Use when Edge is a target browser for your users or product. | Cypress supports the latest three major versions. |
| Firefox | Use when Firefox coverage is part of the suite’s purpose. | Cypress supports the latest three major versions and currently cannot launch versions below 140, according to its browser guidance. |
| WebKit | Use when you specifically need to explore WebKit behavior. | Cypress identifies WebKit as experimental; do not treat it as equivalent to the documented Chrome, Firefox, and Edge support policy. |
Migrate a local Cypress project from Electron
- Install the intended browser. Install Chrome or another browser Cypress supports on each developer machine that runs the suite. Cypress also points to CI options such as Docker images, its GitHub Action, and CircleCI Orb in its migration guide.
- Find Electron selections. Search project configuration and package scripts for
--browser electronanddefaultBrowser: 'electron'. Also check any wrapper scripts or CI commands that may be choosing a browser indirectly. - Choose a default or pass the browser explicitly. Set a default such as
defaultBrowser: 'chrome'in Cypress configuration, or supply the browser in the run command:npx cypress run --browser chrome. The CLI accepts installed browser names such aschrome,chromium,edge, andfirefox; Cypress attempts to detect installed browsers automatically. See the Cypress CLI reference. - Run the suite and inspect its behavior. Run the relevant tests locally, check failures for browser-specific assumptions, and confirm the Electron deprecation warning no longer appears.
For example, a project configuration can set defaultBrowser: 'chrome' in its Cypress configuration object. The exact surrounding file and export format depend on the project’s existing configuration; change only the browser setting rather than replacing the rest of the configuration.
Update CI and control browser versions
Changing a local command is not enough if CI still chooses Electron or does not have the new browser installed. Update the CI job’s browser installation or image and its Cypress command, then run the same test job used for releases. Cypress’s migration guidance points to Docker images, the GitHub Action, and CircleCI Orb as CI routes; use the workflow appropriate to your provider and verify its installed browser rather than assuming local autodetection applies in CI.
Rank #3
- For an evergreen browser: accept that browser updates can change test behavior, and investigate failures as potential browser-version changes as well as application regressions.
- For more deterministic runs: Cypress documents downloading a specific Chrome for Testing or Chromium version. Pin and maintain the chosen version in the CI environment, and keep it within Cypress’s supported browser window.
- For Firefox: do not pin a version below 140 for current browser launching according to Cypress’s guidance.
- For multiple browser coverage: run separate jobs or commands for each installed target. A passing run in one engine does not establish behavior in another.
Troubleshooting migration problems
The Electron deprecation warning still appears
A command, configuration default, wrapper, or CI job is still selecting Electron. Search for both --browser electron and defaultBrowser: 'electron', inspect the actual command printed by CI, and make sure the intended browser is selected in every path that runs Cypress.
Cypress cannot find or launch Chrome
The browser may not be installed in the environment running Cypress, or may not be available under the name supplied. Install it in that environment, check Cypress’s detected browser list, and use a browser name accepted by the CLI. Local installation does not install the browser in a CI container.
Rank #4
- Brand: Wiley
- Set of 2 Volumes
- A handy two-book set that uniquely combines related technologies Highly visual format and accessible language makes these books highly effective learning tools Perfect for beginning web designers and front-end developers
Firefox fails to launch
Check its version against Cypress’s current browser guidance. Cypress says versions below Firefox 140 cannot be launched because their WebDriver BiDi implementation is incomplete; use a supported installed version and review the compatibility page before pinning.
Tests pass in Electron but fail in Chrome or another browser
Do not assume the failure is only a Cypress configuration problem. The move is specifically intended to exercise a browser closer to the real target, and behavior can differ across engines or versions. Inspect the application behavior, test assumptions, browser APIs, timing, and any version change; then decide whether the product or the test needs adjustment.
A CI run selects Electron despite a local default
Check the CI command-line arguments and environment setup. An explicit --browser electron selection can override the intended choice, and a CI environment may not share the local browser installation or configuration path. Update and validate the CI job itself.
Or skip the browser setup
If you also need clean website screenshots for documentation, QA records, or agent workflows, ScreenshotNeo is a separate website screenshot API and MCP server—not a replacement for running Cypress tests. One GET request can return an image or PDF. For a screenshot of Stripe:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpSee the ScreenshotNeo API documentation for request options. It accepts cookie/consent banners and removes 60+ known consent platforms, newsletter popups, and chat widgets before capture; each of those steps can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed, and response headers identify the page verdict and billing status. Its MCP server provides take_screenshot, get_page_info, and capture_pdf tools for AI agents and other MCP clients. The free plan includes 1,000 shots per month with no card; paid plans start at $5 for 3,000 shots. Sign up for ScreenshotNeo’s free plan.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallFrequently Asked Questions
Does Cypress 16 remove Electron?
No. Cypress 16.0.0 deprecated Electron as a test browser; it continues to run with a warning during the deprecation period.
Has Cypress announced the Electron removal date?
No. The official migration guidance says removal will happen in a future major version but does not name the version or date.
Can I keep using Electron for now?
Yes, runs still work during the deprecation period, but selecting Electron produces a warning and the selection must be migrated before removal.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →
