workerEnvVars fix

workerEnvVars was not being passed properly to the worker. This would still pick up environment variables based on your current env, but not new ones defined as an argument. This is now corrected so anywhere in you cucumber code (step defintions, hooks, world, etc) you can reference a property via process.env

results.json log is now merged at the feature level

Note This is to be considered a breaking change to the api, as the results file produced has changed its format slightly. It now aligns with how default Cucumber groups logs (Scenarios are grouped and nested with a feature, we currently dupe feature per scenario).

This also injects the value used from a scenario outline into the log data. Cucumberjs v2+ allows for custom formatters to address this, but I don't want to constrain versions so tightly.

v0.12.1

Fixing a bug where failed scenario outlines would cause multicuke to hang

Add --fail-fast

Add a new --fail-fast option that mimics the equivalent option in cucumber-js.

Default to empty string for uri if missing

This corrects an error in the output parsing where if the uri is missing, it would cause an exception on path.join as the argument is undefined. This will default to an empty string to circumvent the exception bringing anything else down and parses the rest of the error data.

Capture stdout when a test fails to execute

Stderr was being captured to print to console when cucumber itself crashed so that we could have insight on failures, but was leaving out useful information on stdout with which point in the test it failed on.That is now also captured and piped to console if that test fails to run. This will not happen when a a test 'fails' in the sense that the expected output is not met, but rather a failure in the running of the test.

Default Cucumber to 1.0.0

Listing this currently as a minor bump as it has the potential to affect existing usecase if you are reliant on the default cucumber packaged with multi-cuke and the major version bump affects your code in some way (Please remember minor version bumps in sub 1.0.0 semver could mean some volatility).

If this version change affects your testing, meaning your cucumber steps definitions have some incompatibility with version 1.0.0, please use the --cucumber <path> flag to specify a path to any installed version of cucumber you choose.

Removed hard limit to maximum workers

Workers were limited to max number of cpus cores. That limit is removed, as cpu cores was already the default and passing a worker count explicitly should not be altered.

Propagate error messaging on cucumber failure to run

This would obfuscate the error when cucumber was unable to run, hiding it behind an error unable to read logs in multicuke. This now passes the stderr log to the parser to surface properly.

Allow multiple paths in devMode

This previously did not handle paths correctly if running with the 'devMode' option. It now does.