Concordion Concordion Integration and Best Practices 1

Question 1

How is Concordion typically integrated into a CI/CD pipeline?

Accepted Answer

It runs as part of the Maven/Gradle test phase alongside JUnit tests

Answer

Because Concordion uses the JUnit runner, any CI system that supports Maven or Gradle test phases runs Concordion automatically.

Question 2

What Maven plugin command runs Concordion acceptance tests?

Accepted Answer

mvn test

Answer

Concordion tests are standard JUnit tests, so `mvn test` executes them via the maven-surefire-plugin without any special configuration.

Question 3

Where does Concordion write its HTML report output by default?

Accepted Answer

target/concordion in a Maven project

Answer

By default Concordion writes reports to target/concordion (Maven) or build/concordion (Gradle), mirroring the project's build output directory.

Question 4

What is a recommended best practice for naming Concordion fixture classes?

Accepted Answer

Name them to match the feature described in the specification

Answer

Naming fixture classes after the feature or behavior they test makes the test suite self-documenting and easy to navigate.

Question 5

How does using Concordion relate to the BDD (Behaviour-Driven Development) practice?

Accepted Answer

Concordion supports BDD by making acceptance criteria executable specifications

Answer

Concordion implements BDD principles by turning acceptance criteria written in plain English into executable, verifiable specifications.

Concordion Practice Test