Tracker
Roadmap search
Versions, deliverables, workstreams, tasks, and pages
Test harnesses and fixtures
featureStandard
src/content/docs/platform-spec/compiler/conformance/test-harnesses-and-fixtures/index.mdx
import SpecPageHeader from '@beskid/beskid-ui/platform-spec/SpecPageHeader.astro'; import DomainTiles from '@beskid/beskid-ui/platform-spec/DomainTiles.astro'; import SpecSection from '@beskid/beskid-ui/platform-spec/SpecSection.astro';
<SpecPageHeader status="Standard" ownerName="Piotr Mikstacki" ownerEmail="pmikstacki@cybernomad.it" submitterName="Piotr Mikstacki" submitterEmail="pmikstacki@cybernomad.it" /> <SpecSection title="What this feature specifies" id="what-this-feature-specifies"> 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. </SpecSection> <SpecSection title="Implementation anchors" id="implementation-anchors"> - `compiler/crates/beskid_tests/src/analysis` fixture-driven semantic assertions - `compiler/crates/beskid_tests/src/runtime` runtime behavior checks - `compiler/crates/beskid_e2e_tests/src/tests/runtime_cases.rs` source-to-runtime outcomes - `compiler/crates/beskid_tests/src/doc_tests.rs` docs-driven verification </SpecSection>Decisions
No open decisions. Closed choices are normative ADRs under adr/ (D-COMP-CONF-0004 … D-COMP-CONF-0006); use the reader ADRs tab for expandable detail.