Free tools Windows power users keep installed
One-click scans. No signup required.
Cypress 10.7.0, released August 30, 2022, introduced experimental Cypress Studio for end-to-end tests, alpha Svelte component testing, Dashboard connection guidance, and Cypress.require() support inside cy.origin() callbacks. It is a historical release, not a current upgrade target for every project: first check your installed major version, then follow Cypress’s migration guide one major version at a time.
What’s new in Cypress 10.7?
Cypress’s 10.7.0 changelog dates the release to August 30, 2022. Its highlights span test authoring, component testing, Dashboard onboarding, and cross-origin test code.
Experimental Cypress Studio for end-to-end tests
Studio was reintroduced as an experimental feature that records interactions to generate end-to-end tests. To enable it in a 10.7 project, set e2e.experimentalStudio to true in the Cypress configuration. Studio was not available for component tests in this release. Because it was experimental, treat it as early access rather than a stable capability guaranteed across later releases. Cypress explains feature maturity in its release-stage documentation.
Alpha Svelte component testing
Cypress 10.7 added Svelte component testing support as an alpha feature. Cypress warned that alpha features can change incompatibly in future releases. Check the documentation for the version you actually install before building a long-lived workflow around this support.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Dashboard onboarding changes
The Specs list gained hover actions on the Latest Runs and Average Duration columns intended to help connect a project to Cypress Dashboard. The release also added informational banners explaining how to connect a project and record a first test run. These were onboarding aids, not changes to the test runner’s core execution model.
Cypress.require() inside cy.origin()
Cypress 10.7 added Cypress.require() to load dependencies inside a cy.origin() callback, which executes in a separate context. Its availability changed across later releases: Cypress says it was removed in 10.11 in favor of CommonJS require() or ES module import(), then added again in 12.6. Consult the Cypress.require() version history and the cy.origin() API for the version in your project; do not assume the 10.7 behavior applies unchanged today.
How should you choose an upgrade target?
Start by identifying the version in the project and deciding the next major migration step—not by aiming at 10.7 because it is the subject of this article. Cypress’s currently served migration guide covers later majors and recommends moving one major version at a time. A project on Cypress 9 should first follow the 9-to-10 guide; a project on a later major should follow the guide for its own next major.
- Identify the installed version. Check the Cypress version used by the project and its lockfile or package manifest so you know which migration guide applies.
- Choose the next major only. Read that major’s official migration instructions before changing dependencies. Repeat the process for each subsequent major rather than skipping intervening migration steps.
- Inventory project-specific configuration. Note whether the project uses end-to-end tests, component tests, custom plugins, framework-specific dev-server settings, or experimental features.
- Apply the guide for the exact step. Review configuration, defaults, removed options, and APIs; migration details differ by testing type and framework.
- Verify the migrated project. Run Cypress’s supported verification checks and the project’s test suite, then address failures before proceeding to another major.
What changes when migrating from Cypress 9 to Cypress 10?
The 9-to-10 migration is not just a package-version change. Cypress 10 removed support for cypress.json and changed how configuration and plugin events are organized. The official migration guide is the authority for the complete set of changes; use it alongside these key areas.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Replace cypress.json with a config file
Create cypress.config.js or cypress.config.ts and move the project’s configuration into it. For example, an end-to-end base URL belongs inside the e2e configuration object. Do not copy settings mechanically: confirm their current names and placement in the guide for the target version.
Move plugin event handling into setupNodeEvents
Logic commonly held in cypress/plugins/index.js must move into the setupNodeEvents function in the configuration. Review the guide’s examples and preserve the events and tasks your project actually uses.
Review testing-type and spec settings
For example, Cypress 10 replaced componentFolder with testing-type specPattern, and component dev-server configuration belongs inside component. The correct settings depend on whether and how the project uses component testing.
Check support files, removed options, and APIs
Review the migration guide for changes to spec and support file defaults, removed configuration options, and APIs. Then verify Cypress’s configuration and run the project’s tests. Passing a migration step on one project cannot be assumed for another project with different plugins, frameworks, or test types.
When are Studio and Svelte support appropriate?
In the context of 10.7, both features carried an explicit maturity caveat. Studio was experimental and limited to end-to-end tests; Svelte component testing was alpha. They may be worth evaluating when their respective workflows address a project need, but avoid making them foundational without checking the release-stage status and current documentation for the version you run.
Or skip the browser setup
If you need a clean screenshot of a test page or other URL without configuring a browser capture workflow, ScreenshotNeo provides a one-request screenshot API and an MCP server for AI agents. For example, using cURL:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp
See the ScreenshotNeo API documentation for request options. Cookie banners, popups, and chat widgets are removed before the shot; bot checks, blank pages, and failed loads are never billed. Its MCP server lets AI agents take screenshots. The Free plan includes 1,000 screenshots per month with no card, and paid plans start at $5 for 3,000.
Sign up free for 1,000 screenshots a month, with no card required.
Frequently Asked Questions
Does Cypress 10.7 work with every current Cypress project?
No single compatibility claim follows from the 10.7 release notes. Use the migration guide for the next major step from your installed version, and check that version’s documentation for the APIs and features your project uses.
Can Cypress Studio record component tests in 10.7?
No. The experimental Studio feature in 10.7 was available for end-to-end tests only.
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.
