Concordion Concordion Specifications 2

Question 1

What is the recommended file extension for a Concordion specification?

Accepted Answer

.html

Answer

.xml

Answer

.txt

Answer

.spec

Question 2

How does Concordion match a specification file to its fixture class?

Accepted Answer

By class name and package path mirrored in the classpath

Answer

By a @SpecFile annotation

Answer

By a properties configuration file

Answer

By scanning all HTML files at startup

Question 3

What is the benefit of writing Concordion specs in plain HTML rather than a custom DSL?

Accepted Answer

Any browser can render them without special tools

Answer

They compile faster

Answer

They are automatically unit-tested

Answer

They require no classpath setup

Question 4

What is a Concordion 'index' specification?

Accepted Answer

A spec that uses concordion:run to link to and execute child specifications

Answer

The first test that always runs

Answer

A spec that only contains assertions

Answer

A spec that imports database fixtures

Question 5

Can a Concordion specification contain regular HTML content alongside concordion: commands?

Accepted Answer

Yes, non-annotated HTML is treated as descriptive prose

Answer

No, all elements must have concordion: attributes

Answer

No, only concordion: elements are allowed

Answer

Only if surrounded by special comment tags

Question 6

What is the preferred approach for adding styling to Concordion HTML reports?

Accepted Answer

CSS linked in the spec's <head> element

Answer

Inline styles on every element

Answer

A separate XSLT transform

Answer

The Concordion CSS configuration API