Concordion Concordion Markdown Specifications 3

Question 1

Which Concordion command is used in Markdown tables to verify that rows in a table match a collection returned by a fixture method?

Accepted Answer

c:verifyRows

Answer

`c:verifyRows` iterates over a fixture-returned collection and verifies each item matches a corresponding row in the Markdown table.

Question 2

In a Concordion Markdown project, where must the `@RunWith(ConcordionRunner.class)` annotation be placed?

Accepted Answer

On the Java fixture class

Answer

The `@RunWith(ConcordionRunner.class)` annotation is placed on the Java fixture class to instruct JUnit to use Concordion's runner for that test.

Question 3

How does Concordion treat standard Markdown formatting (bold, italic) inside a specification file?

Accepted Answer

Bold and italic are purely presentational and do not trigger any Concordion commands

Answer

Markdown formatting like bold and italic is only presentational in Concordion specs; commands are exclusively expressed through the Concordion link syntax.

Question 4

What naming convention links a Concordion Markdown specification file to its Java fixture class?

Accepted Answer

The Markdown file name (without extension) must match the fixture class name

Answer

Concordion uses convention over configuration: a fixture class `com.example.GreetingTest` maps to a spec file at `com/example/GreetingTest.md` on the classpath.

Question 5

What library provided Markdown specification support in Concordion projects prior to version 2.0?

Accepted Answer

The concordion-markdown-extension library

Answer

Before Concordion 2.0 added native Markdown support, developers used the separate `concordion-markdown-extension` library to enable Markdown specifications.

Concordion Practice Test

Concordion Practice Test

Concordion Concordion Markdown Specifications 3