Concordion > Annotations >

Implementation Status

Since 2.0.0, this annotation can only be used with specifications that are not using the example command. Specifications that are using the example command must use the "status" attribute on the example command instead.

To allow you to include Concordion specifications in the build before they have been fully implemented, you can annotate a fixture class with one of the following annotations in org.concordion.api:

	SUCCESS is only reported if...
@ExpectedToPass	The specification contains zero or more successes, no failures, and no exceptions.
@ExpectedToFail	The specification contains one or more failures or exceptions. Note: When you use the `@ExpectedToFail` annotation, the specification must contain failures or exceptions. The final result will be reported as a FAILURE if the specification only has successes. This means you can't forget to change the annotation to `@ExpectedToPass` when the test begins to pass for the first time, and prevents you unwittingly introducing regression bugs.
@Unimplemented	The specification contains no successes, no failures, and no exceptions.
@FailFast	Processing of the specification is aborted if an exception is encountered
@FullOGNL	The full OGNL syntax is allowed in the specification.

Also note:

If no explicit annotation is specified, Concordion assumes @ExpectedToPass.
Do not use more than one annotation at a time.

Example Usage

import org.concordion.api.ExpectedToFail;

@ExpectedToFail
public class GreetingTest extends ConcordionTestCase {

   public String greetingFor(String firstName) {
        ...
   }