Concordion Concordion Integration and Best Practices 2

Question 1

What is the recommended scope for Concordion acceptance tests versus unit tests?

Accepted Answer

Acceptance tests at feature/behavior level; unit tests at method/class level

Answer

Concordion acceptance tests verify high-level behavior from a user perspective, complementing low-level unit tests rather than replacing them.

Question 2

Why is it important to keep Concordion fixture methods free of assertion logic?

Accepted Answer

Assertions belong in the spec; fixture methods should only compute and return values

Answer

Putting assertions in the spec rather than the fixture keeps the spec as the single source of truth for expected behavior.

Question 3

What is a good strategy for handling database setup in Concordion acceptance tests?

Accepted Answer

Use @Before to set up known data and @After to clean it up in the fixture

Answer

Using JUnit setup/teardown lifecycle methods in the fixture ensures each test starts with a known database state and cleans up after itself.

Question 4

How should Concordion specs handle environment-specific configuration such as base URLs?

Accepted Answer

Read configuration from system properties or environment variables in the fixture

Answer

Fixture methods should read environment-specific values from system properties or environment variables, keeping specs environment-agnostic.

Question 5

What is the benefit of using Concordion's verifyRows command over multiple assertEquals calls for list verification?

Accepted Answer

verifyRows checks the full collection in one command and handles missing/extra items

Answer

concordion:verifyRows compares an entire collection at once, reporting missing, unexpected, and matched items clearly in the report.

Concordion Practice Test