Concordion Concordion Integration and Best Practices 3

Question 1

What is a common antipattern when writing Concordion specs?

Accepted Answer

Writing implementation details into the spec instead of business behavior

Answer

Embedding implementation details in specs couples the documentation to internals, making specs fragile and harder for stakeholders to read.

Question 2

How can Concordion tests be integrated with Selenium WebDriver for UI testing?

Accepted Answer

The fixture initializes a WebDriver instance and fixture methods drive browser interactions

Answer

The fixture manages the WebDriver lifecycle and exposes methods that navigate the browser; Concordion commands then assert the outcomes.

Question 3

What is the recommended granularity for a single Concordion specification file?

Accepted Answer

One specification per feature or user story

Answer

Aligning each spec to one feature or story keeps specs focused, readable, and maintainable as the system grows.

Question 4

How does Concordion's approach differ from Cucumber/Gherkin for acceptance testing?

Accepted Answer

Concordion uses free-form HTML prose; Cucumber uses structured Given/When/Then syntax

Answer

Concordion allows flexible prose HTML with embedded commands, whereas Cucumber enforces the structured Given/When/Then Gherkin format.

Question 5

What is the purpose of using @ConcordionOptions(markdownSuffix = '.md') on a fixture?

Accepted Answer

Tells Concordion to look for a Markdown spec file instead of an HTML file

Answer

Setting markdownSuffix points Concordion to a .md spec file, activating the concordion-markdown module for that fixture.

Concordion Practice Test