Concordion Cheat Sheet 2026

The 30 highest-yield Concordion facts, distilled from real exam questions. Print it, save it as a PDF, or study it here — free, no sign-up.

1. Can a Concordion specification contain regular HTML content alongside concordion: commands? → Yes, non-annotated HTML is treated as descriptive prose
2. What library provided Markdown specification support in Concordion projects prior to version 2.0? → The concordion-markdown-extension library
3. Which Concordion expression syntax is used to call a fixture method with arguments? → methodName(#arg1, #arg2)
4. How does Concordion's approach differ from Cucumber/Gherkin for acceptance testing? → Concordion uses free-form HTML prose; Cucumber uses structured Given/When/Then syntax
5. How does Concordion indicate a failing assertion in the HTML report? → Red background with expected and actual values
6. Can Concordion fixture methods be overloaded with different parameter counts? → Yes, Java overloading works normally
7. What file extension is used for Concordion Markdown specification files? → .md
8. What is the purpose of the concordion:run with runner='concordion' attribute? → To execute a linked HTML specification using the Concordion runner
9. What Maven plugin command runs Concordion acceptance tests? → mvn test
10. What is the purpose of @BeforeEach or @Before annotated methods in a Concordion fixture? → Set up shared state before each spec assertion or table row
11. What does concordion:assertTrue do? → Passes if the fixture expression returns true
12. How does using Concordion relate to the BDD (Behaviour-Driven Development) practice? → Concordion supports BDD by making acceptance criteria executable specifications
13. Can multiple Concordion extensions be used together on the same fixture? → Yes, @Extensions accepts an array of extension classes
14. What role does the element's xmlns:concordion declaration play? → It binds the concordion: prefix to the Concordion namespace URI
15. What Markdown link syntax asserts that a Concordion expression equals the expected value "Hello, World!"? → [Hello, World!](- "?=#result")
16. Which Concordion command is used in Markdown tables to verify that rows in a table match a collection returned by a fixture method? → c:verifyRows
17. What does the concordion:echo command output to the HTML report? → The result of an expression printed into the document
18. Why should Concordion acceptance tests not be used to replace exploratory or manual testing? → Concordion only tests scenarios explicitly written in the spec, missing unknown unknowns
19. In Concordion Markdown, what is the correct way to express a set-variable command inline within a paragraph? → Embed `[value](- "#var")` directly in the sentence text
20. What happens to surrounding whitespace in a concordion:set value? → It is trimmed automatically
21. A Concordion spec is described as 'active' documentation. What does 'active' mean? → The spec is executed as part of the test suite
22. What file format does Concordion use for writing specifications? → HTML
23. Why is it beneficial to publish Concordion HTML reports as build artifacts in CI? → Stakeholders can review living documentation and verify behavior after every build
24. What does the concordion:assertFalse command display in the report when it passes? → Green highlight on the element
25. What does the Concordion Screenshot extension do? → Captures browser screenshots on test failure for web UI tests
26. How should Concordion specs handle environment-specific configuration such as base URLs? → Read configuration from system properties or environment variables in the fixture
27. What is the primary goal of Concordion's Living Documentation? → Keep specifications synchronized with implementation
28. Which version of Concordion first introduced native support for Markdown specifications? → Concordion 2.0
29. How do Concordion extensions receive the ConcordionExtender object? → Via the addTo(ConcordionExtender extender) callback method of ConcordionExtension
30. How is Concordion typically integrated into a CI/CD pipeline? → It runs as part of the Maven/Gradle test phase alongside JUnit tests