Cypress 10.7.0, released August 30, 2022, added experimental Cypress Studio for end-to-end tests, alpha Svelte component testing, Dashboard interface changes, and Cypress.require() support inside cy.origin() callbacks. It is a historical release, not a recommended upgrade target for every project: identify your installed version and follow Cypress’s migration guide one major version at a time.
What’s new in Cypress 10.7?
Cypress’s 10.7.0 changelog lists four release highlights. The changes vary in maturity: Studio was experimental and Svelte component testing was alpha, so neither should be mistaken for a stable feature guarantee across later Cypress versions.
As an Amazon Associate I earn from qualifying purchases.
Experimental Cypress Studio for end-to-end tests
Studio was reintroduced as an experimental feature that records browser interactions to help generate tests. It was limited to end-to-end testing in this release and had to be enabled with the e2e.experimentalStudio flag. Consult the documentation for the Cypress version you actually run before relying on the setting or its behavior.
Alpha Svelte component testing
Cypress 10.7 introduced Svelte component testing support as an alpha. Cypress warns that alpha features can change, including through breaking changes in later releases. Treat it as an evaluation option rather than assuming it is suitable unchanged for a production test setup.
Dashboard-oriented Specs list changes
The Specs list gained hover actions on its Latest Runs and Average Duration columns to help users connect a project to Cypress Dashboard. Informational banners also explained how to connect a project and record a first test run.
Cypress.require() inside cy.origin()
Cypress.require() was added in 10.7 to load dependencies inside a cy.origin() callback, which executes in a separate context. Its availability changed over time: Cypress removed the API in 10.11 in favor of CommonJS require() or ES module import(), then added it again in 12.6. Check the Cypress.require API history and the cy.origin() documentation for your installed version before changing code.
How should you choose an upgrade target?
Do not jump to 10.7 just because its release notes are the subject of this guide. First check the Cypress version currently installed, then identify the next major migration step supported by Cypress. The current migration guide contains guidance for later majors and recommends moving one major version at a time. A project on Cypress 9 should follow the Cypress 10.0 migration guide; a project already on a later major should follow the guide for its next major transition.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
- Record the installed version and the intended next major version.
- Check whether the project uses end-to-end testing, component testing, or both; defaults and framework-specific settings can differ.
- Inventory configuration, plugin event handlers, dependencies, support files, and tests that use experimental or alpha features.
- Read the migration guide for that exact transition, including any intervening major guides, rather than applying Cypress 10 changes indiscriminately.
The 10.7 release notes describe what shipped then; they are not a current compatibility matrix and do not establish whether a specific app will upgrade successfully.
How do you migrate from Cypress 9 to Cypress 10?
The following changes apply to the Cypress 9-to-10 step described by Cypress. Use the official migration guide as the authoritative checklist for your project’s testing type and configuration.
1. Replace cypress.json with a config file
Cypress 10 removed support for cypress.json and requires a JavaScript or TypeScript config file, typically cypress.config.js or cypress.config.ts. Move settings into the new configuration structure and verify each option against the migration guide; do not simply rename the file.
2. Move plugin event handling into setupNodeEvents
Logic commonly held in cypress/plugins/index.js belongs in the configuration’s setupNodeEvents function. Review each plugin and event handler for the new structure and confirm that it still runs in the intended testing type.
Windows 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 reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware match3. Update configuration placement and names
- Place
baseUrlinside thee2econfiguration object. componentFolderwas replaced by testing-typespecPattern.- Put component dev-server configuration inside
component. - Review defaults, removed options, and APIs against the migration guide rather than carrying forward settings by assumption.
4. Verify the migrated project
Use the Cypress verification checks and run the project’s relevant test suite after updating the configuration and dependencies. A successful configuration edit alone does not prove that the application, test runner, plugins, or component framework work together. Cypress’s guide includes verification and test steps; results depend on the individual project.
Screenshot a test page without setting up a browser
For a screenshot needed in a test workflow, ScreenshotNeo is a website screenshot API and MCP server from Yorker Media. Its API can return an image or PDF from one GET request, and its 63 options include CSS-selector element capture, viewport and device settings, custom CSS and JavaScript, waits, cookies, and headers. It also accepts parameter names used by other screenshot APIs, which can make switching easier. See ScreenshotNeo and its API documentation.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpReplace the target URL and supply your API key. ScreenshotNeo accepts the URL in a GET request and returns a screenshot; the response format can be PNG, JPEG, WebP, or PDF according to the requested output.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Common upgrade problems to check
- Cypress still expects
cypress.json: Cypress 10 removed support for that file. Create the JavaScript or TypeScript config and move settings into the supported structure. - Plugin events no longer run: move the former plugin-file logic into
setupNodeEventsand confirm it is configured under the relevant testing type. - Base URL or component configuration is ignored: check that
baseUrlis undere2e, component dev-server options are undercomponent, and specs usespecPatternrather than the removedcomponentFoldersetting. Cypress.require()fails: verify the installed Cypress version. It was removed in 10.11 and restored in 12.6, so the right dependency-loading syntax depends on the version.- Studio or Svelte component testing behaves differently: Studio was experimental and Svelte support alpha in 10.7. Check the release-stage and migration documentation for the version you are using, and avoid assuming early-access behavior is unchanged.
Or skip the browser setup
ScreenshotNeo can capture a page with one request. Before capture, it accepts cookie or consent banners as a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets; each cleanup step can be turned off. Bot checks and CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing, and response headers report the page verdict and billing status. Its MCP server offers take_screenshot, get_page_info, and capture_pdf to Claude, Cursor, and other MCP clients. The Free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 shots.
Recommended Free Tools
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 docs, or sign up free for 1,000 screenshots a month with no card.
Frequently Asked Questions
Can Cypress 10.7 test Svelte components?
Yes. Svelte component testing support was introduced as an alpha in Cypress 10.7; alpha functionality may change or break in later releases.
Does Cypress 10.7 support Cypress.require() inside cy.origin()?
Yes. Cypress.require() was added in 10.7, removed in 10.11, and restored in 12.6. Check the API history for the version you have installed.
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.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitches
