Executes Cucumber scenarios in parrallel, reducing the amount of time tests take to execute

Downloads in past


19131.1.06 years ago10 years agoMinified + gzip package size for parallel-cucumber in KB


Build Status Dependencies Code Climate
Executes Cucumber scenarios in parallel, reducing the amount of time tests take to execute.
parallel-cucumber-js uses multiple node.js processes to execute more than one Cucumber feature at a time. This can greatly reduce the time it takes for a test suite to execute. However, a test suite needs to be built with parallization in mind; especially when the Cucumber features are accessing shared resources like a database-backed web service.



parallel-cucumber-js is available as an npm module called parallel-cucumber.
parallel-cucumber-js should be added to your test codebase as a dev dependency. You can do this with:
$ npm install --save-dev parallel-cucumber

Alternatively you can manually add it to your package.json file:
  "devDependencies" : {
    "parallel-cucumber": "latest"

then install with:
$ npm install --dev


parallel-cucumber-js can be ran from a terminal as follows:
$ node_modules/.bin/parallel-cucumber-js

By default parallel-cucumber will look for features files under a directory called ./features

Number of Workers

The number of features that will be executed in parallel can be set by passing the -w argument:
$ node_modules/.bin/parallel-cucumber-js -w 4

Setting the number of workers controls the amount of parallization. The larger the number of workers, the more Cucumber feature will be executed in parallel. By default the number of workers is set to the number of CPU cores in the machine running parallel-cucumber.


parallel-cucumber can execute the same scenario multiple times. This can be useful for things like executing the same tests against both a desktop browser and mobile browser.
$ node_modules/.bin/parallel-cucumber-js --profile.desktop.tags ~@mobile-only ~@desktop-only

parallel-cucumber sets an environment variable called PARALLELCUCUMBERPROFILE which can be used within the Cucumber step defs and support code to determine which profile is currently executing.

Environment variables

Environment variables can be specified for a profile and those environment variables will be set when the Cucumber scenarios are executed for the profile:
$ node_modules/.bin/parallel-cucumber-js --profile.desktop.env.EXAMPLE_NAME example_value --profile.desktop.env.EXAMPLE_NAME_2 example_value_2


Two output formats are supported: json and progress. The progress format is the default. The -f argument is used to configure a different format:
$ node_modules/.bin/parallel-cucumber-js -f json

By default, output is sent to the console but you can also send it to a file:
$ node_modules/.bin/parallel-cucumber-js -f json:./output.json

You can configure multiple formats, with each format configured to output to the console or a file:
$ node_modules/.bin/parallel-cucumber-js -f json:./output.json -f progress


See for an example test codebase that uses parallel-cucumber-js.