Releases: Comcast/zucchini
Releases · Comcast/zucchini
Upgrade cucumber-reporting version
Compare
Sorry, something went wrong.
No results found
Depend on cucumber-reporting version 3.2.0
2.2.9
Compare
Sorry, something went wrong.
No results found
Added new feature fastrun. This uses all of the contexts to run through the features files just once.
2.2.8
Compare
Sorry, something went wrong.
No results found
Updated the cleanup() method to be called even if the over written setup() fails
2.2.7
Compare
Sorry, something went wrong.
No results found
Added trace logging throughout the system.
Performance improvement in the writing of the cucumber results.
2.2.6
Compare
Sorry, something went wrong.
No results found
Fix the issue where failure of all test contexts resulted in failure of subsequent scenarios.
2.2.5
Compare
Sorry, something went wrong.
No results found
Fix BarrierSync() when a cucumber test is using a Scenario Outline
2.2.4
Compare
Sorry, something went wrong.
No results found
Fixes bug in barrier sync. This was causing an ungraceful thread termination.
2.2.3
Compare
Sorry, something went wrong.
No results found
No major changes from previous release. Added code to the pom for automatically signing and deploying to maven central in a staging repository.
All future releases will be available via maven central:
<dependency>
<groupId>com.comcast.zucchini</groupId>
<artifactId>zucchini</artifactId>
<version>2.2.4</version>
</dependency>
2.2.2
Compare
Sorry, something went wrong.
No results found
dimaj
released this
15 Sep 18:11
Added a version string to the end of the report title. This makes debugging and error reporting more accurate.
Fixed potential error where a AbstractZucchiniTest throwing within a cleanup() method could cause false negatives in error reporting.
2.2.1
Compare
Sorry, something went wrong.
No results found
dimaj
released this
15 Sep 03:34
Added a version string to the end of the report title. This makes debugging and error reporting more accurate.
Fixed potential error where a AbstractZucchiniTest throwing within a cleanup() method could cause false negatives in error reporting.