- Upgraded to cucumber-js v1.3.3 (#26)
- Backgrounds no longer a failure (closes #20)
- Upgraded to latest version of Cucumber, v1.0.0 (closes #16)
- Executes scenarios in parallel rather than just executing features in parallel (closes #14)
- Additional tests for retries
- Removed retry count from feature and scenario ids and added it to the feature names
- Formatters could not emit error events
- Retries should not fail when an element in the report does not have an id
- Retry failed features (closes #11)
- Removed the -c command line argument (closes #7)
- Included the tests in the npm package
- Restructured the tests
- The tests are less reliant on tags
- Additional tests for tags
- BeforeFeatures and AfterFeatures events should not fire for every feature (closes #8)
- Updated dependencies
- Use Travis CI for builds (closes #3)
- Setting environment variables on a profile (closes #6)
- Allow cucumber-js 0.4.x to be used (closes #2)
- Error with progress formatter when a step has no result (closes #4)
- Can now specify a customized version of cucumber-js to load. Can specify a relative path or custom module name
- Implemented a work around for cucumber-js lacking a dry run mode. The workaround uses an environment variable called PARALLEL_CUCUMBER_DRY_RUN
- Improved the output of the progress formatter. Nested JSON in error messages is now converted to YAML, which makes it much easier to read the error messages
- Added additional tests for the --profiles.NAME.tags command line arguments
- Fixed a bug where passing only one -r/--require command line argument did not work. Specifying more than one of those arguments was working
Initial release