Sibling articles under this feature previously restated requirements in inconsistent forms.
Examples
Platform spec article
Examples
Spec standingStandard
-
This feature hub owns normative MUST/SHOULD contract text for Test harnesses and fixtures.
Context
Decision
This feature hub owns normative MUST/SHOULD contract text. Sibling articles must not redefine hub requirements and should link here for authority.
Consequences
Contract changes start on the hub or in linked ADRs, then propagate to articles and implementation anchors.
Verification anchors
site/website/src/content/docs/platform-spec/compiler/conformance/test-harnesses-and-fixtures/index.mdxarticle bundle under the same feature directory.
-
Platform-spec text supersedes informal crate comments for Test harnesses and fixtures.
Context
Implementation crates accumulated informal notes that diverged from published contracts.
Decision
Normative platform-spec prose and ADRs under this feature supersede informal comments in implementation crates until explicitly migrated into spec text.
Consequences
Engineers file spec/ADR updates when behavior changes; crate comments are non-authoritative for conformance arguments.
Verification anchors
compiler/crates/beskid_tests/src/analysiscompiler/crates/beskid_tests/src/runtimecompiler/crates/beskid_e2e_tests/src/tests/runtime_cases.rs
-
This feature explains how the project proves that implemented behavior remains stable release over release. It is organi
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
The reference compiler must implement Test harnesses and fixtures as documented in this feature hub and its article bundle.
Consequences
Changes require hub/ADR updates and verification anchor extensions.
Verification anchors
compiler/crates/beskid_tests/src/analysiscompiler/crates/beskid_tests/src/runtimecompiler/crates/beskid_e2e_tests/src/tests/runtime_cases.rs
- 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).
Example 1: Happy path
Section titled “Example 1: Happy path”A standard project exercises the expected producer -> consumer handoff with no contract violations. Trace this via:
compiler/crates/beskid_tests/src/analysisfor fixture-driven semantic assertionscompiler/crates/beskid_e2e_tests/src/tests/runtime_cases.rsfor source-to-runtime outcomes
Example 2: Contract mismatch
Section titled “Example 2: Contract mismatch”Intentionally alter a boundary definition (for example, a symbol or structure shape), then run the related conformance suite. The expected result is a deterministic failure that identifies the mismatched boundary.
Example 3: Regression-proofing a fix
Section titled “Example 3: Regression-proofing a fix”After applying a fix, add or update a focused fixture in the nearest test crate and rerun wider suites so the behavior remains locked for future refactors.