Run Cypress tests in parallel without Dashboard: Tutorial

Cypress is a powerful end-to-end testing fabric, but its built-in Dashboard service isn ’ t the only way to run tests in parallel. You can also run Cypress test in latitude, without using the Dashboard.

In this tutorial, you ’ ll hear how to speed up your examination suite by running Cypress tests in parallel, without using the Dashboard, habituate your own CI frame-up and custom logic for test distribution.

What is Cypress Parallelization?

Tests construct using Cypress run very tight and in any real time projection the tests grow from 100s to 1000s. If you run the examination in sequential manner (1 at a clip), no matter how tight the exam execution in Cypress is, it is still move to conduct a good amount of time.

Cypress provides a feature to run examination in Parallel in CI runs using the Cypress Cloud. To use this feature, users should enable Cypress Cloud Integration with our Project and set the flag –parallel in the cypress execution dictation.

The Cypress parallel in built feature need Multiple agent configure in CI run and Cypress balances the loading based on the agents and number of spec file.

Why is it significant to run Cypress Tests in Parallel

To speed up the tests you ask to run our tests in Parallel. Parallelization refers to executing multiple test at any given clip.

Taking model of three tests

1. Test1 takes 5 minutes
2. Test2 takes 10 minutes
3. Test3 takes 5 minutes

When accomplish these tests in Sequential mode it will take 20 minutes. But if you run these three tests in parallel it will average to 10 minutes (It saved 10 minutes!).

Why run Cypress Tests in Parallel without Dashboard?

Running Cypress tests in parallel, without using the Cypress Dashboard, allows teams to accelerate test execution while avoiding external dependencies, subscription cost, and data exposure.

Key Benefits:

• Faster Test Execution: Split test specs across multiple machine or container to reduce total test run time.
• No Vendor Lock-in: Avoid habituation on the Cypress Dashboard or paid plans.
• Cost-Effective Scaling: Leverage your own base or CI runners for parallelization.
• Improved CI Integration: Easily integrate with GitHub Actions, GitLab CI, Jenkins, or others.
• Data Privacy & amp; Compliance: Keep tryout information and logarithm within your organization ’ s environment.
• Custom Analytics: Use open-source or custom tools to track results without dashboard limitation.

How to run Cypress Tests in Parallel without Dashboard

Before trying to run tests in Parallel without Dashboard, countenance run the three tests which can be institutehere

And if you execute below bidding in command line, three tests will be run againstBrowser Stack ’ s Demo coating

npx cypress run -- spec `` cypress/e2e/dropdown-examples/ * .js ''

It is taking 29 Seconds for executing three tests in Sequential mode

SUSA automates exploratory testing with persona-driven behavior, catching bugs that scripted automation misses.

Now to run tests in analogue without Cypress Dashboard, We are going to use two plugins in this clause

1. cypress-parallel
2. cypress-split

Method 1: Using cypress-parallel

You need to install the plugincypress-parallel.

To install this plugin run the below dictation from root of your project

npm i cypress-parallel

Once the plugin is installed, all you need to do is execute below bid

npx cypress-parallel -s cypress: run -t 3 -d `` cypress/e2e/dropdown-examples/ * .js ''

In the above command, using cypress-parallel plugin to fulfill cypress tests. This command contains three constituent

1. -s & lt; npm script & gt; & # 8211; -s cypress: run(cypress: run is the npm script which exists in our package.json file)
2. -t& lt; bit of threads & gt;
3. -d & lt; spec register path & gt;

Executing the above command will create aparallel-weights.jsonfile and thespecfiles are divided based on this file and run in parallel free-base on the thread number provided

You need to insure that the thread bit ply should be based on the agent & # 8217; s Hardware capacity.

Method 2: Using cypress-split

You can use this plugin to run the cypress exam collimate in CI builds.

Installation instruction can be foundhere

With this plugin you can run specific tryout across multiple containers or you can run with multiple agents

Below Github action will run the specific glasses in Parallel on the 2 containers

Below Github action will run all the exam in Parallel in across multiple agent

The work example of Github actions can be foundhere

Once the Github action is execute as part of CI build, it will produce a summary report like below

Github link for the above summary account can be foundhere

Benefits of Cypress Parallelization without Cypress Cloud

By using the two plugins as discourse above, you can run tryout in Parallel without purchase give plans in Cypress Cloud.

You can likewise configure whether to run these exam in parallel across multiple agents or within a single agent with multiple containers.

Limitations of Cypress Parallel Execution without Cypress Cloud

Cypress cloud whirl helpful Analytics, such as

• Runs Status:Users can filter the Run status by Branch, Tag, No of Days, Group by Daily, Weekly, Monthly and Quarterly

• Run Duration:Provides analytics on the Average run duration, Agents used and Time saved while running in Parallel manner

• Test Suite Size:Provides analytics on the test rooms added over a period of clip

• Top Failures:Provides analytics about top betray test cases over period of time

• Slowest Tests:Provides analytics on the tests that taking more time and do execution slower over a period of time

• Most Common Errors:Provides analytics on the failing tryout by aggroup based on the error thrown

• Flaky Tests:Provides analytics on the flaky tests establish on the retry over a period of time

Talk to an Expert

Conclusion

This article spotlight what is Parallel execution, How to achieve the Parallel Cypress tests execution by expend plugins without using fascia and likewise the limitations of not Using Cypress Cloud for Parallel execution.

Post Test Execution Analytics is critical to realise the run duration, tests performance and errors and this feature is available in Cypress Cloud which will benefit the projects tremendously.

Whenever running Cypress test, it is recommended to test on so that the can be guide into history for best truth of tryout results. Tools like assistance QAs by providing access to 3000+ device browser combination for a comprehensive automated testing.

Related Guides