Releases: trivago/cluecumber
Releases · trivago/cluecumber
2.1.0 - customization and redesign
2.0.1 - Bugfix release
Fixed
- Error when
customParametersFile
property was not set (#171) - Wrong log format for
customCssFile
property
Added
- Better error messages for missing files
2.0.0 - Architecture changes and property loading
Added
- Ability to set custom parameters via a properties file through the
customParametersFile
property (#167, contributed by gazler22)
Fixed
- Custom parameters are now displayed in the order of definition (#157)
- Better logging and error handling
Changed
- Major internal architecture change to ease future extension
1.11.0 - Speed / compatibility release
Fixed
- Much higher report generation speed
- Warnings in Java > 8
- Various small code style issues
Changed
- Updated all dependencies
Removed
- Cloner dependency
- JSoup dependency
1.10.2 Nexus version fix
updated version
1.10.1 - UTC time conversion, small bug fixes
Fixed
- Incorrect wrapping for urls in custom parameters
- UTC timezone conversion for timestamps
Changed
- more resilient mime type handling
1.10.0 - Support timestamps, various bug fixes
Fixed
- Steps that are only skipped should not have a link to a scenario from the minimum/maximum time in
All Steps
- Feature name on
Scenario Details
page was incorrectly linked
Added
- Additional parallel run time on
All Scenarios
andScenario Sequence
pages - Support of Cucumber 4.3.0's new scenario start timestamps
- Start time and date, end time and date and duration is displayed on each scenario in
All Scenarios
,Scenario Sequence
andScenario Detail
pages (Cucumber >= 4.3.0)
Changed
Scenario Sequence
is now not based on start time if it exists in the json file- Minor design changes
1.9.0 - strict scenario mode
Added
- Minimum and maximum step times on
All Steps
page links to the enclosing scenario (#152) - New
failScenariosOnPendingOrUndefinedSteps
configuration property for marking scenarios as failed when they contain
steps with statuspending
orundefined
(default value isfalse
) (#74)
Changed
- Minimum and maximum step times are now only calculated for non-skipped steps
1.8.1 - Step status fix
Fixed
All Steps
shows scenario states instead of step states (#147)