Story: Test infrastructure follow-up
Table of Contents
This page documents a story in Sprint 04. It captures the goal, current status, acceptance criteria, and the tasks that compose it.
Goal
Close out the BLOCKED item from sprint 03's test_infrastructure:
CTest only reported one Catch2 test per suite, making per-test
failure analysis impossible.
Status
| Field | Value |
|---|---|
| State | DONE |
| Parent sprint | Sprint 04 |
| Now | Completed 2025-11-20. |
| Waiting on | None. |
| Next | None. |
| Last touched | 2025-11-20 |
Continued from: Test infrastructure.
Acceptance
- Each individual Catch2 test case shows as its own CTest entry on the dashboard.
- Per-test failure messages are surfaced through CDash.
Tasks
| Task | State | Start | End | Description |
|---|---|---|---|---|
| CTest shows only one test per test suite | DONE | 2025-11-20 | 2025-11-20 | Resolve the CTest-only-shows-one-test-per-suite behaviour that was BLOCKED in sprint 03. |
Decisions
- Successor story rather than re-opening the predecessor
- per the
v2 lifecycle, BLOCKED items that carry forward become a new story
in the next sprint with
#+predecessor:linking back. Sprint 03'stest_infrastructurestory closedDONEfor what landed there; this story handles the leftover.
Out of scope
- Other test-infra improvements (separate testing-related work that isn't carrying over from sprint 03).
See also
- Test infrastructure (sprint 03) — the predecessor story.
- ores.testing — the testing component hosting the suite-level registration.