Concordion Concordion Integration and Best Practices 1 — Questions and Answers
Question 1: How is Concordion typically integrated into a CI/CD pipeline?
- It runs as part of the Maven/Gradle test phase alongside JUnit tests (Correct answer)
- It requires a separate CI server plugin
- It must run after deployment to production
- It only runs in Docker containers
Correct answer: It runs as part of the Maven/Gradle test phase alongside JUnit tests
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?
- mvn test (Correct answer)
- mvn concordion:run
- mvn verify concordion
- mvn acceptance-test
Correct answer: mvn test
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?
- target/concordion in a Maven project (Correct answer)
- src/test/resources/reports
- build/reports/concordion
- tmp/concordion-output
Correct answer: target/concordion in a Maven project
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?
- Name them to match the feature described in the specification (Correct answer)
- Prefix all names with Concordion
- Use generic names like Test1, Test2
- Suffix all names with IT for integration
Correct answer: Name them to match the feature described in the specification
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?
- Concordion supports BDD by making acceptance criteria executable specifications (Correct answer)
- Concordion is only for TDD, not BDD
- Concordion replaces Gherkin/Cucumber entirely
- BDD requires Concordion's proprietary DSL
Correct answer: Concordion supports BDD by making acceptance criteria executable specifications
Concordion implements BDD principles by turning acceptance criteria written in plain English into executable, verifiable specifications.
Question 6: What system property configures the Concordion output directory?
- concordion.output.dir (Correct answer)
- concordion.report.path
- concordion.output.path
- test.output.dir
Correct answer: concordion.output.dir
Setting the concordion.output.dir JVM system property redirects the HTML reports to the specified directory.
How is Concordion typically integrated into a CI/CD pipeline?