Overview

Concordion instruments examples in a specification as checks against a system under test, then generates documentation when those checks run. Results distinguish passing from failing assertions and show expected and actual values for failures; tables and links to other specifications can make the output useful to readers beyond the test team. This keeps examples tied to execution, but teams need to maintain the specifications as part of their software workflow for that connection to stay useful.

Fixtures can call application code directly or drive deployed interfaces through libraries such as Selenium WebDriver, JAX/WS, JAX/RS or JDBC. Java fixtures use JUnit, while Concordion.NET integrates with NUnit. The project dates to 2006 and is maintained by volunteers, with a Google Group and GitHub for contact and participation.

Key features

Specification formats and IDEs

Java specifications can be written in Markdown or HTML, and C# options are available. IntelliJ IDEA support includes completion, navigation and test-running, with both HTML and Markdown specifications; the Eclipse plugin supports HTML but not Markdown. Teams committed to Markdown should therefore favor IntelliJ over Eclipse for the documented plugin workflow.

Builds, extensions and reports

The Java distribution is version 4.0.1 and is available through Gradle and Maven, as well as a full ZIP containing source code and dependencies. Concordion also documents command-line execution and integrations with Spring. The concordion:run task with a JUnit 4 fixture additionally needs JUnit Vintage, a build detail worth accounting for when wiring an existing project.

Extensions can add commands, event listeners or changes to generated documentation; examples include Excel specifications, parallel runs, screenshots and logging tools. Jenkins' HTML Publisher plugin can publish results, retain per-build history and offer report output as a ZIP. But Jenkins Content Security Policy defaults can block the reports' inline CSS and JavaScript. Relaxing the policy is described as a workaround, so teams with strict security settings should evaluate that requirement before relying on Jenkins reports.

Pricing

Open source — 0.00 USD per free. The Java library is licensed under Apache License 2.0, with no paid plan or trial to weigh. This suits teams able to integrate and maintain a library within their own build and test workflows; it is less compelling for buyers seeking a commercial support tier, since the project is volunteer-maintained.

Platforms

Concordion supports Linux, macOS and Windows, and is self-hosted. Its execution mode is local, with Gherkin support, parallel execution, browser testing and API access. These capabilities make it relevant to teams running their own tests and interfaces, rather than a hosted test service.

Who it's for

Stakeholders and analysts can use the generated documentation to review examples of expected behavior, while developers and testers connect those examples to checks. Java teams have the most clearly documented build and IDE paths; C# teams have Concordion.NET with NUnit. The tool is a better fit for teams willing to keep executable specifications in their delivery process than for those wanting a standalone documentation product.

Pros and cons

Pros: Generated results show assertion status and expected-versus-actual values, making failures easier to interpret in context.
Pros: Java has Gradle, Maven, command-line, Jenkins and IDE integrations, with extensions for capabilities such as parallel runs and screenshots.
Cons: Jenkins' default Content Security Policy can interfere with report rendering, and the documented workaround involves relaxing that policy.
Cons: Eclipse's plugin does not support Markdown specifications, unlike the IntelliJ plugin.
Cons: Volunteer maintenance and community contact channels may not suit teams that require commercial support.

Alternatives

FitNesse is another free, open-source option for teams comparing specification-based tools; its plan has no stated commercial tiers or limits.

Serenity BDD is a free open-source library to consider when its broader Android, iOS, web and desktop platform coverage matters; its JUnit 4 support is deprecated and planned for removal in Serenity 6.0.0.

Cucumber Open is a free open-source project with Cucumber Reports also free, an alternative for readers evaluating another no-cost testing tool.

Ginkgo is a free Go testing framework, with v2 as its currently supported major version; choose it when a Go framework is the relevant fit.

CukeTest offers a free Lite plan with visual feature editing, JavaScript and Python, but some built-in automation libraries have usage limits and the plan includes 500 automation API calls and a 3-minute limit.

Karate is a free MIT-licensed framework for REST, GraphQL and SOAP API testing, browser and desktop UI automation, and Gatling performance testing; it is a stronger match when those API and automation workflows are the priority.

LightBDD is a free, BSD 2-Clause-licensed option with no paid tiers stated, worth comparing for teams considering another open-source framework.

Reqnroll offers a free Community plan with framework use, Visual Studio and Rider integration, community plugins and community support; its Professional plan is another tier to consider.

Browse more options in BDD Testing Tools.

Verdict

Choose Concordion if your team wants executable examples to produce readable, shared documentation and can own the integration work. Its strongest reason to choose it is the direct link between specification and test result; look elsewhere if you need commercial support or cannot accommodate the Jenkins report security workaround.

	Chorus BDD	Concordion
Free plan	No	Yes
Free trial	No	No
Paid from	—	Free
Open source	No	No
Platforms	Linux, macOS, self-hosted, Windows	Linux, macOS, self-hosted, Windows
Gherkin support	Yes	Yes
Execution mode	local	local
Browser testing	Yes	Yes
API access	Yes	Yes
Parallel execution	—	Yes

Chorus BDD vs Concordion

Chorus BDD

Concordion