"Fail-fast" option

By default, exceptions are reported but Concordion continues processing the rest of the test. (More details)

However, fixtures can be annotated with @FailFast to stop further processing if an exception is encountered. This can be useful if further processing after an exception is undesirable (e.g. because it's slow, could cause corruption or would make the results hard to explain to others). It is possible to specify specific exceptions on the @FailFast annotation.

Note that the @FailFast annotation is transitive when used with the run command. That is:

Given one fixture executes another fixture, and both fixtures are annotated with @FailFast,
When the called test throws an exception,
Then further processing of both tests is stopped.

Example

When the fixture is annotated with @FailFast and processes the following:

<p concordion:execute="myExceptionThrower()">
This method throws an exception.
</p>

<p concordion:execute="myMethod()">
This method executes quietly.
</p>

It does not call myMethod() in the Java fixture code because the exception thrown by the first method call stops further processing of the test.