All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog and this project adheres to Semantic Versioning.
Back to Readme.
1.12.0 - 2024-05-08
generated-features.properties
only included the last generated feature, not all
- Updated dependencies
- Infrastructure changes (GitHub workflow, Maven wrapper, etc.)
1.11.0 - 2023-12-04
- New way to only generate features without runners by specifying
<desiredNumberOfRunners>0</desiredNumberOfRunners>
.
- Default value of
<desiredNumberOfRunners>
was changed from0
to-1
:-1
means that the number generated runners should be equal to the number generated scenarios.0
means that no runners should be generated at all.
- Java 11 requirement
- Updated dependencies
1.10.0 - 2023-06-27
- Ability added to specify a folder containing rerun text files [183]
- Additional
generated-features.properties
file in the generated feature directory that stores all generated feature names and their reference to the respective source feature [184] - Feature source options can now be freely combined
- Cucable version is now mentioned in the generated runners and features
- Various dependency updates
1.9.0 - 2020-11-26
- Better error messages when features cannot be parsed (#173)
Background
steps are now preserved asBackground
in generated scenarios (#160)
1.8.0 - 2020-08-15
- Correct handling of feature tags in combination with multiple tagged example tables (#168)
- Invalid runner class name for features beginning with numbers (#156)
1.7.2 - 2020-04-03
- Cucable does not fail on empty Cucumber feature list file.
1.7.1 - 2020-04-03
- Runner and feature file names generated from Cucumber feature text files are now postfixed with
_rerun_IT
1.7.0 - 2020-03-30
- Support for Cucumber feature text files (#154)
- Various dependency and documentation updates
1.6.0 - 2019-12-10
- Cucable is now more resilient when trying to deal with unparsable features - these are skipped instead of stopping the overall execution.
- Utf-8 encoding error on linux (#150)
- Scenarios had too many tags when there were also feature tags (#145)
1.5.3 - 2019-09-09
- Scenario name support (#127, contributed by @josepj)
1.5.2 - 2019-07-11
- Updated dependencies
- Replaced
cobertura
withjacoco
1.5.1 - 2019-03-14
- Potentially wrong handling of scenarios without tags when a tag expression is provided in
<includeScenarioTags>
( #107)
1.5.0 - 2019-03-11
- Untrue error on missing example table columns (#100)
- Errors before scenario parsing are not reported as parse errors anymore
- Cucumber tag expression support (#104)
- Removed parameters
excludeScenarioTags
,includeScenarioTagsConnector
andexcludeScenarioTagsConnector
in favor of Cucumber tag expressions inincludeScenarioTags
includeScenarioTags
now expects a Cucumber tag expression
1.4.0 - 2019-02-13
-
Support for
and
andor
mode forincludeScenarioTags
andexcludeScenarioTags
viaincludeScenarioTagsConnector
andexcludeScenarioTagsConnector
parameters (default: 'or') (#88):<includeScenarioTagsConnector>and</includeScenarioTagsConnector> <excludeScenarioTagsConnector>or</excludeScenarioTagsConnector>
-
Support to specify multiple
sourceFeatures
(#55), e.g.:<sourceFeatures> src/test/resources/features/sometests, src/test/resources/features/MyFeature.feature:8:15 </sourceFeatures>
-
Ability to generate runners with a specific number of features by specifying
desiredNumberOfFeaturesPerRunner
(#70)
-
includeScenarioTags
andexcludeScenarioTags
are now specified as a list of strings:<includeScenarioTags>@tag1,@tag2</includeScenarioTags> <excludeScenarioTags>@tag3</excludeScenarioTags>
-
includeScenarioTags
andexcludeScenarioTags
can now be used without the preceding@
:<includeScenarioTags>tag1,tag2</includeScenarioTags>
-
Completely rewritten feature handling to support more options
1.3.2 - 2019-02-01
- Feature parsing on windows (#73)
- Arbitrary table cell content handling (#94)
1.3.1 - 2019-01-21
- Fixed handling of data and example tables containing line breaks (
\n
)
1.3.0 - 2018-11-30
- Support for scenarios with multiple example tables
parallelizationMode=features
now uses exact copies of the source features
1.2.0 - 2018-11-12
- New property
parallelizationMode
so that Cucable can optionally parallelize complete features instead of individual scenarios
- Logging tweaks and removed code duplication
1.1.0 - 2018-06-25
- Support for custom template placeholders via
[CUCABLE:CUSTOM:xxx]
1.0.0 - 2018-05-18
- Support a fixed number of runners running multiple scenarios in sequence
- New
[CUCABLE:RUNNER]
template placeholder that is substituted with the current runner name - New
[CUCABLE:FEATURE]
template placeholder that is substituted with the one or multiple features in the generated runner
- Feature and runner generation is now separated in order to support more features in the future.
- Better logging for missing example table placeholders in scenario outlines (contributed by @daczczcz1)
- Template placeholder
[FEATURE_FILE_NAME]
is not supported anymore, please use[CUCABLE:FEATURE]
and[CUCABLE:RUNNER]
instead
0.1.11 - 2018-05-08
- Fix for wrong unicode detection of source feature path in runner comments
0.1.10 - 2018-05-08
- Runner comments containing "\u" were wrongly considered unicode
0.1.9 - 2018-04-20
- It is now possible to use an existing Java runner class as a template for generated runners
- Source runner template is now included as a comment in generated runners
0.1.8 - 2018-03-30
- Source feature path is now included as a comment in generated features and runners
- Configurable logging with 4 levels: default, compact, minimal, off
- The number of generated scenarios per feature is shown in the default logs
- The total number of generated features is shown in a summary line in all log levels except off
- All dependencies are updated to their latest version
0.1.7 - 2018-03-02
- Updated to Gherkin 5.0.0
- All Gherkin languages are now supported
0.1.6 - 2018-02-09
- Ability to use example placeholders in scenario outline names (contributed by @daczczcz1)
0.1.5 - 2018-02-07
- Docstring support in steps
- Possibility to specify multiple line numbers to process specific scenarios (like in Cucumber),
e.g.
myFeature.feature:12:42:111
.
0.1.4 - 2018-02-05
- Scenario and feature descriptions were not included in generated feature files
0.1.3 - 2017-12-20
- Fixed handling of data tables that include example table values
0.1.2 - 2017-12-05
- Tag filtering now also considers feature tags
0.1.1 - 2017-11-28
- Removed debug logs
0.1.0 - 2017-11-28
- Ability to include and exclude scenarios based on certain tags
- More unit tests
0.0.9 - 2017-10-27
- Logging is now more compact
- Changed license blocks from trivago GmbH to trivago N.V.
- It is now possible to process a specific scenario inside a feature file by specifying a line number prefix (like in
Cucumber), e.g.
myFeature.feature:12
. - More unit tests added.
0.0.8 - 2017-09-24
- Fixed parse error on empty cells in data tables
- Fixed file name generation bug with special chars in source feature file names
- Unit tests for data table handling
0.0.7 - 2017-09-20
- Complete rewrite of the internal logic of the plugin to support all edge cases like
- empty scenarios
- background steps (also with data tables)
- scenario steps with data tables
- complex scenario outlines
- Better logging (including plugin version)
- Clearer error messages
0.0.6 - 2017-08-31
- Ability to run single features multiple times in parallel
- Properties are now logged on plugin start
- More unit tests
- Complete project now uses dependency injection via Google Guice
- POM parameter featureFileDirectory was renamed to sourceFeatures since it now supports specifying either a directory or a single feature file
0.0.5 - 2017-08-18
- Cucumber 'Background' is now supported in feature files
- More logging added.
0.0.4 - 2017-06-01
Initial project version on GitHub and Maven Central.