Files
aevolution/docs/adr/0004-test-benchmark-framework.md
2026-10-08 12:08:53 -04:00

1.2 KiB

[Reviewed]

ADR-0004: Bounded test and benchmark harness

Status

Owned CTest/chrono harness adopted for proof only; Catch2/Google Benchmark proposed before M2 expansion.

Context

The small proof needs real deterministic, restore and malformed-input checks without dependency bootstrap.

Decision

Release-active checks, named failures, nonzero exit, CTest and a steady-clock benchmark outside simulation. Record seed/count/ticks/compiler/build. Report shared-runner timings without pass thresholds.

Alternatives Considered

Catch2 (BSL-1.0) offers expression diagnostics/fixtures; Google Benchmark (Apache-2.0) offers dedicated measurement; GoogleTest is viable without a present required advantage.

Benefits

Immediate verification and a small review surface.

Costs

Limited diagnostics, no shrinking/statistical measurement framework.

Risks

Homemade harness becomes a maintenance project or hides failure.

Consequences

Do not grow a custom DSL/mock/statistics framework. Pin/evaluate frameworks before M2. Seed ensembles are sampled invariants, not exhaustive proof. Catch2, Google Benchmark.