v0.9.5

Fixed Issues

• Fixed issue with primitive arrays and the @table annotation #162
• Fixed an issue when using the @Table parameter that could lead to unwanted parameters in the data table #161
• Fixed an issue with the Maven Plugin where the customJsFile parameter actually set the customCssFile parameter #167
• Fixed an issue with the @table annotation when combining numberedRows with columnTitles #166
• Fixed an issue in the console report that new lines a data table messed up the layout of the table #152

New Features

• CamelCase in step methods is now supported (thanks to albertofaci) #164, PR #165

v0.9.4

New Features

• Spring support has been simplified by a new annotation @EnableJGiven and XML element <jgiven:annotation-driven />. Special thanks to TripleNail for this contribution. #153
• Scenarios without steps can now be excluded from the report by using the new --exclude-empty-scenarios report generator option #151
• Underlines in parameter names are now replaced with spaces in the report #147
• HTML Report: highlight failing cases of a scenario #150
• HTML Report: indicate the number of failed cases #156
• HTML Report: limit the width of columns in the data table #141

Fixed Issues

• Fixed an issue that blank values could not be formatted #157
• Fixed an issue that the total duration of a scenario was shown as the duration of the first case instead of the sum of all case #155
• HTML Report: fixed the minor issue that clicking the status doughnot does not work when the report has just been opened #149

v0.9.3

Fixed Issues

• HTML Report: Fixed an issue that inline attachments are shown multiple times #145
• HTML Report: fixed an issue with attachments that could lead to the generation of attachments with identical names, overriding attachments of other scenarios #144

New Features

• Attachments can now have a custom filename #144
• HTML Report: allow arbitrary protocols in custom navigation links #146

v0.9.2

New Features

• Cases can now have custom descriptions by using the new annotation @CaseDescription #139.
• Custom test class suffixes can now be configured using the @AbstractJGivenConfiguration annotation.

v0.9.1

New features

• Global formatters now apply also to subtypes of the types they are configured for #137

Fixed Issues

• Fixed an issue with TestNG that when using a data provider and one case fails the TestNG status was still reported as success. #138

v0.8.4

Fixed Issues

• Fixed in issue with TestNG introduced with v0.8.3 that a failing case does not lead to failed TestNG status #138

v0.9.0

New Features

• The name of the test class is now used by JGiven to group scenarios. The @As annotation can be used to define a different name. #133
• Scenarios can now have an extended description by annotated the test method with @ExtendedDescription. #35
• The stack trace of a failing scenario is now stored and shown in the HTML report #95
• Formatter for step parameters can now be defined by using the @JGivenConfiguration annotation on a test class.
• HTML Report: made title of the HTML report configurable using the new --title parameter of the report generator #131
• HTML Report: added possibility to provide a custom.js file that is included in the generated report. This allows you to further customize the report. #129
• HTML Report: made status circle clickable to show failed, pending, or successful scenarios #130

Fixed Issues

• Special characters like parentheses are not treated as part of a placeholder name anymore #118

Backwards incompatible changes regarding placeholder variables

It is now not possible anymore to have spaces/underlines in placeholder variables. The rational behind this change is that the old behavior was hard to understand and did not really give much additional value.

Old Behavior

The old behavior allowed placeholder variables to have spaces/underlines if the variable was terminated with another$. Consider the following example:

given().a_step_with_a_$placeholder_variable$_with_spaces( "foobar" );

Before v0.9.0 this resulted in the following report:

Given a step with a foobar with spaces

I.e. the complete string $placeholder_variable$ was replaced. From v0.9.0 on this will not be possible anymore. In fact, the terminating $ will be treated as a new placeholder variable.

New Behavior

A placeholder variable must match the regular expression \$[a-zA-Z0-9]*. In particular, it cannot contain the _ character. The above example, will now even throw a JGivenWrongUsageException because the number of arguments do not match the number of placeholders anymore.

Migration

If you relied on the fact that placeholders can contains spaces or underlines, you have to rename your variables to camelCase. In addition, you have to remove the trailing $. So the above example becomes:

given().a_step_with_a_$placeholderVariable_with_spaces( "foobar" );

v0.8.3

Fixed Issues

• Fixed an issue with TestNG that when using a data provider a failing case prevented following cases from finishing #123
• Fixed an issue that the status of the overall scenario could be successful although some cases of the scenario failed #125

v0.8.2

New Features

• Introduced the annotation @DoNotIntercept, to completely circumvent the JGiven interception mechanism of step methods. #103
• Introduced new feature to directly show image attachment in the HTML report. This is done by calling showDirectly() on the Attachment object. #117
• Introduced the possibility to automatically number the rows or columns of a table parameter. #116
• HTML Report: introduce pagination to better deal with large lists of scenarios. #120

Fixed Issues

• HTML Report: fixed an issue that caused the scenario list to only shows the first 20 entries #119

v0.8.1

New Features

• Parameters of test methods can now also be formatted with formatters like step parameters. This is only relevant, however, when you have scenarios with multiple cases that do not generate a data table, but multiple cases #114

Fixed Issues

• Fixed the issue that test classes had to be compiled with the -parameters option of javac when using Java 8. This was fixed by upgrading to the newest version of the Paranamer library that now fully supports Java 8 #106
• Fixed an issue where different formatted parameters having the same value in all cases were collapsed to a single parameter #104
• Fixed issue introduced with v0.8.0 that tag descriptions that differ depending on a tag value are not correctly reported
• Fixed an issue that the dataprovider with TestNG could not be used in parallel mode #105
• Fixed an issue that when using TestNG only a report for one test class was generated #115