1.7.0

A minor update that updates the surefire-api and common-java5 version to 2.22.2 to support JUnit5 integration via Maven's Surefire Plugin.

1.6.0

A minor update that adds a new method to the Runner, #getExitCode that can be called after a test run to determine the overall status of the test run.

The following list specifies the order in which the exit code is determined:

• If no tests are run the exit code will be 4
• If any block, test hook or test fails the exit code will be 1
• If any test is skipped the exit code will be 2
• If any test is pending the exit code will be 3
• If none of the above the exit code will be 0

1.5.0

A minor update with new Runner constructors to provide greater flexibility in the order in which Test Transforms are applied.

Changes:

• Exposes the run parameters for which groups/tags to run to the ConfigurationProvider via Configuration#getRunOptions() and Runner.TagRunOption option type.
• Tag Expression package has been moved from internal and is now public and supported.
• New Configuration#removeCoreTestTransforms() method to remove default Test Transforms.
• The two existing Runner constructors have been deprecated, and constructors that use the new Options to provide tag configuration are added.

1.4.0

A minor update with slight API changes.

Changes:

• Added new groupExpression property for specifying which groups/tags to run
• New model class builders have been added to make construction easier, especially when cloning an existing model object using the new #toBuilder() methods.
• Options constructor is private with a static Options.EMPTY

1.3.1

A bugfix release that fixes the following:

• Fix CompositeReporter to call new hook methods introduced in 1.2.0.

1.3.0

A minor update with slight API changes.

Changes:

• Added new method to the Options class to allow un-setting an Option
• Changed the #set method on the Options class to be immutable and return a new copy of the options with the option set.

1.2.0

A minor update with no breaking API changes.

Changes:

• Added new methods to the Reporter interface to report the start and successful execution of hooks. These methods have default, empty implementations to avoid breaking existing reporters.
• Use thread-local data structures internally to Cuppa to ensure that tests can be defined in a multi-threaded environment.
• Remove the restriction that at least one Option must be passed to Cuppa#with().

1.1.0

This release improves reporting.

Changes:

• Cuppa now marks a test as skipped if it was not run due to a hook failure. Previously Cuppa did not report anything for such tests.
• Introduced Reporter#testHookFail and Reporter#blockHookFail to distinguish between test hooks (beforeEach/afterEach) and block hooks (before/after). Reporter#testHookFail is passed the test that is associated with the test hook.
• Added Configuration#setAdditionalReporter to allow a configuration provider to specify an additional reporter. This reporter will be called in addition to the primary reporter provided to Cuppa by the runner.

Game on

This is the first public release of Cuppa.

We think that the public API is relatively stable now.