Skip to content

Files

Latest commit

 

History

History
101 lines (80 loc) · 2.99 KB

run-your-cypress-tests-in-parallel.md

File metadata and controls

101 lines (80 loc) · 2.99 KB
id title hide_title sidebar_label description keywords url site_name slug
run-your-cypress-tests-in-parallel
Run Your Cypress Tests In Parallel On LambdaTest Platform
true
Parallel Testing
Run multiple Cypress tests on the LambdaTest cloud simultaneously across 40+ browser versions. This documentation will help you in running Cypress tests in parallel.
Cypress Automation
Cypress Testing Guide
Cypress Test Automation
Cypress Automation Testing
Running Cypress Tests
Cypress Testing Online
Run Cypress
Cypress Run Specific Test
Cypress Testing Environment
How to Run Cypress Tests
LambdaTest
run-your-cypress-tests-in-parallel/

Run Your Cypress Tests In Parallel


If you want to run your tests parallelly on the LambdaTest platform, you can do that using either of the following two ways:

1. Run your Cypress tests Parallelly using the CLI


To perform Cypress testing parallelly using the CLI, you need to use the "--parallels" option while running your tests.

Syntax:

--parallels <number of parallel sessions>

For example, if you want to run your Cypress tests on 5 parallel sessions, you can use the below command:

lambdatest-cypress run --parallels 5

2. Run your Cypress tests Parallelly using the lambdatest-configuration.json file


To run your Cypress testing parallelly, you can also use the lambdatest-configuration.json file, using the 'parallels' key.

Syntax:

{
  "run_settings": {
    ...
    "parallels": <number of parallel sessions>,
    ...
  }
}

For example, if you want to run your Cypress tests on 5 parallel sessions, use the below settings:

{
  "run_settings": {
    ...
    "parallels": 5,
    ...
  }
}

:::info NOTE

The number of parallel test running on the LambdaTest platform at a time, is based on the concurrency plan of your LambdaTest account. In case the number of parallel tests is more than the concurrency plan, the remaining tests will get queued and run after the existing tests are complete. For example, suppose you have a concurrency plan of 5 parallel sessions and want to run 50 tests parallelly. In this case, only 5 parallel tests will be executed at a time, and the rest 45 will be queued. As the test finishes running, the queued tests will be moved to the running state based on availability.

:::