Primary contract for Test harnesses and fixtures
Platform spec ADR
Primary contract for Test harnesses and fixtures
Spec standingStandard
- Contracts and edge cases Normative guarantees and known edge cases for `Test harnesses and fixtures`.
- Design model Conceptual model for `Test harnesses and fixtures` and its subsystem boundaries.
- Examples Practical examples that demonstrate `Test harnesses and fixtures` behavior.
- FAQ and troubleshooting Common questions and debugging guidance for `Test harnesses and fixtures`.
- Flow and algorithm End-to-end control flow and major algorithmic steps for `Test harnesses and fixtures`.
- Verification and traceability How `Test harnesses and fixtures` requirements map to tests and implementation anchors.
0 revisions (git unavailable at build; counts may be empty)
No commits recorded for this path.
| Section id | Required | Found |
|---|---|---|
what-this-feature-specifies | yes | yes |
implementation-anchors | yes | yes |
Full tree: run pnpm verify:platform-spec-layout (writes src/generated/platform-spec-layout-report.json).
Context
Section titled “Context”This feature explains how the project proves that implemented behavior remains stable release over release. It is organized into newcomer-friendly articles that move from model, to flow, to contracts, then practical verification and debugging guidance.
Decision
Section titled “Decision”The reference compiler must implement Test harnesses and fixtures as documented in this feature hub and its article bundle.
Consequences
Section titled “Consequences”Changes require hub/ADR updates and verification anchor extensions.
Verification anchors
Section titled “Verification anchors”compiler/crates/beskid_tests/src/analysiscompiler/crates/beskid_tests/src/runtimecompiler/crates/beskid_e2e_tests/src/tests/runtime_cases.rs