Concordion

When your Concordion specification contains example commands, you cannot use fixture-level implementation status annotations (like @ExpectedToFail or @Unimplemented) because these are checked at the JUnit test level and do not apply to individual examples.

Instead, you must set the implementation status directly on the example command using the status attribute. This allows you to specify whether a specific example is expected to pass or fail.

<!-- Example of an example command that is expected to fail -->
[Should fail](- "c:assertTrue=false")

<!-- Example of a successful example command -->
[Success](- "c:assertTrue=true")

Concordion uses the Manifold preprocessor to switch between JUnit Jupiter and JUnit Vintage test configurations at compile time.

The testVintage Gradle task sets the JUNIT_VINTAGE compiler argument. This allows you to use conditional compilation logic in your Java code, such as:

#if JUNIT_VINTAGE
@RunWith(ConcordionRunner.class)
#else
@ConcordionFixture
#endif

When importing the Concordion project into an IDE, the required dependencies will be downloaded automatically.

Note for IntelliJ IDEA users: To ensure the IDE correctly recognizes the Manifold preprocessor syntax (e.g., #if blocks), you should install the Manifold plugin.

To package Concordion into a JAR file, run the following command. The resulting JAR will be located in the ./build/libs folder.

./gradlew clean jar

To consume a version of Concordion installed in your local Maven repository, you must configure your Gradle project to look in mavenLocal().

1. Add mavenLocal() to your repositories block in build.gradle (or globally in ~/.gradle/init.gradle):

allprojects {
    repositories {
        mavenLocal()
    }
}

2. Reference the specific version in your dependencies:

dependencies {
    implementation 'org.concordion:concordion:2.0.0-SNAPSHOT'
    // Or use '+' for the latest version
    // implementation 'org.concordion:concordion:+'
}

To make the Concordion JAR available for other Maven or Gradle projects on your local machine, use the publishToMavenLocal task.

./gradlew pTML

Concordion supports both JUnit Jupiter and JUnit Vintage. You can run the full test suite (specification tests and unit tests) using the following commands:

To run with JUnit Jupiter:

./gradlew clean test

To run with JUnit Vintage:

./gradlew clean testVintage

Running these tasks will download dependencies, clean the project, recompile source code, and execute tests. The Concordion specification output is saved to the ./build/reports/spec directory.

Concordion uses Gradle as its build tool and includes the Gradle Wrapper. You can use the wrapper to manage tasks without installing Gradle manually.

To see all available tasks, run:

./gradlew tasks

*(Note: Use `.\