What’s New in Cypress 10: Key Features

Cypress 10 marks a major milestone in the phylogeny of mod. With a revamped architecture and a host of powerful new features, it simplifies testing workflows and improves reliability across web applications.

This article research the virtually impactful feature in Cypress 10 and how to migrate from the old version of the Cypress Project to Cypress 10

Understanding Cypress 10

Released in 2022, Cypress 10 marked a significant turn point for the. It introduced a unified testing experience by combining component testing and under a single interface, get it easier for squad to handle different test types within the same project.

The update likewise replaced the traditional configuration file with a more flexiblecypress.config.js, modernized the UI with a streamlined launchpad, and acquaint built-in test retries for improved trial constancy.

These changes put the foundation for a more scalable and user-friendly testing environment, enhancements that continue to mold how Cypress is used today.

New features in Cypress 10

Cypress 10 introduced several new characteristic designed to simplify test automation for QA pro. Below are the key enhancements and change in this edition:

1. New Improved User Interface (UI)

Cypress 10 features a redesigned, more intuitive User Interface that makes selecting and running trial across different browser easier. It includes separate UIs for and End-to-End (E2E) Testing, providing a clearer and more focused testing experience.

2. Component Testing in Cypress 10 (Beta)

Cypress 10 present Component Testing, enabling fast and effective examination of item-by-item UI components within a existent browser environment. This characteristic allows developers to debug components directly employ Chrome DevTools and promptly address issues.

By supporting both portion and end-to-end examination within the same fabric, Cypress 10 eradicate the need for freestanding tools, create it a preferred choice for developer and testers alike.

Cypress 10 offered a dedicate User Interface for executing Component Tests, delivering an interactional and prosecute testing experience. Developers can supply and essay components from modern model like React, Angular, and Vue in isolation.

Additionally, Cypress 10 includes a setup summons that simplifies configuring your project for Component Testing.

3. E2E Testing in Cypress

In Cypress 10, End-to-End (E2E) examination is primarily handled by QA and test engineers to validate integrated workflows across components. E2E testing is now clearly separated from Component Testing, providing a more organized testing structure.

Previously, end-to-end tests were placed in the integration folder, but with Cypress 10, this folder has been supplant by thee2efolder to reverberate its intention good.

4. File and Folder Structure Changes

Here are a few noteworthy modification in the file and pamphlet structure with Cypress 10:

• The integration brochure is rename the E2E booklet. That meanscypress/integration is now cypress/e2e
• Spec file propagation have vary fromtestfile.spec.js/ts to testfile.cy.js/ts
• cypress/support/index.jsand are renamed tocypress/support/e2e.js
• The pluginsFileoption is withdraw. This option is now part of newsetupNodeEvents () and devServer ()configuration options in your config file
• The testFilesoption is removed. This option is supercede with the newspecPattern option.
• The ignoreTestFilesoption is removed. This option is now replaced with theexcludeSpecPattern option
• The baseUrl and experimentalSessionAndOriginoptions are no longer uncommitted as top-level configuration options and now, it can only be delimit within the e2e shape
• cypress.jsonfile is no longer supported, you need to replace it with one of these file namescypress.config.js, cypress.config.ts, cypress.config.cjs or cypress.config.mjs

Cypress Configuration File will now have the following three constituent:

• Global contour:Option applicable for both e2e and element
• E2E subdivision:Options that are applicable only for e2e tests
• Component section:Options that are applicable for only component tests

5. Additional flag support for opening Cypress window

Since Cypress has two different parts, component and e2e, if you open the Cypress window with the commandnpx cypress open, you need to choose manually to land on the specific type of testing.

Cypress 10 introduces two distinguishable masthead, one each for Component Testing and End-to-End (E2E) Testing, as outlined below:

• To open the Cypress E2E Testing window directly

  npx cypress open -- e2e

• To open the Cypress component testing window directly.

  npx cypress open -- component

6. No Example Tests in Fresh Cypress Installations

Previously, Cypress installations included legion example examination cases by default. With Cypress 10, these examples have be removed, requiring users to make or download tests through the Cypress E2E Project setup interface.

For autonomous testing across multiple user personas, check out SUSATest — it explores your app like 10 different real users.

7. Browser Selection Option Added to Test Runner Window

Previously, browser selection was but useable at the Cypress Project window. With Cypress 10, you can choose the browser either from the Project window or directly within the Test Runner window.

Cypress CLI Changes and characteristic in Cypress 10

• Cypress E2E test can be now run with command

npx cypress run -- e2e

• Cypress Component test can be run with command

npx cypress run –component

• The end-to-end tests by default, without any option, are run using the Cypress CLI command

npx cypress run

How to Migrate from the Old version of Cypress Test Automation Project to Cypress 10

Cypress 10 introduced several breaking modification along with new features and bug fixes. Updating to Cypress 10 without migrate your existing projection will cause tests to fail. Therefore, after upgrading, it ’ s necessary to migrate your project to be compatible with Cypress 10.

Step 1: Update Cypress habituation in your undertaking

You can update the Cypress dependency to the Cypress 10 version using the command below:

npm install cypress @ latest

Step 2: Launch the Cypress window

Once the update is complete, launch the cypress window with the command

npx cypress exposed

Note Sometimes you might confront an error, try entering the below command and repeat Step 2.

npx cypress install -- force a

Step 3: The new Cypress 10 window Opens, see the video (optional), and pawl on Continue to Cypress10.

Step 4: Migration Helper window opens up

Once you click on Continue to Cypress10 the migration helper opens up.

Step 5: Rename existing Specs

The migration window suggests a specification files folder from integrating to e2e

Next, the appellative conventions fromxyz.js to xyz.cy.js file

Click on Rename These Specs for me

Step 6: Rename the Cypress Support file

As mentioned earliercypress/support/index.jshas change tocypress/support/e2e.js, so you need to change them accordingly.

Click on Rename support file for me

Step 7: Update Configuration File

The cypress.jsonis no longer supported in Cypress 10, So you need to transmigrate the new Cypress configuration file.

Click on Migrate theConfiguration File For me

Step 8: Configure End-to-End Tests

Once you complete the above Tests you will be landed on the welcome page.Click on the E2E Testing tileto Configure End to end Tests

Step  9: Review newly Added files

Cypress windows Open up with the Title & # 8220; Configuration Files & # 8221;, Now review all the files and click onContinue

Step 10: Choose the browser

Cypress Lists all the installed browsers on your Machine Click on the Browser of your choice and Click on Start E2E Testing

Step 11: Cypress Specs window

Cypress Specs window open up, Choose the Spec from the uncommitted listing. Cypress Test runner starts executing tests

As Cypress continues to evolve with knock-down features, integrating your test mechanisation with reliable cloud-based program can boost enhance your quiz workflow.

offers seamless g on real devices and browsers, enabling faster and more comprehensive test coverage for Cypress tests without the demand for complex local apparatus. Combining Cypress with BrowserStack helps teams accelerate release cycles while sustain high-quality standards.

Talk to an Expert

Conclusion

Cypress 10 brought significant melioration that streamline both component and end-to-end testing, making test automation more efficient and accessible for developers and QA team. With its redesigned UI, clear separation of test types, raise configuration, and knock-down debugging potentiality, Cypress 10 laid the groundwork for a more coordinated and flexible testing experience.

While upgrading requires some migration attempt, the benefits in productivity and test reliableness are easily worth it. Leveraging tools like Cypress alongside platforms such as BrowserStack can farther optimize your testing strategy and help render quality coating quicker.

BrowserStack ’ s provide access to 3500+ real device and browsers to execute, cross-browser testing, and.

It easily integrates with framework like Cypress,,, etc., and all the major CICD tools like,,,, etc. This seamless integration enables teams to automate trial across multiple environments expeditiously, ensuring faster releases with high confidence in application quality.

Related Guides