Altium Cruncher Test Strategy

Scope

Altium Cruncher is the command-line and design-review layer over altium-monkey. The test suite validates CLI routing, generated artifacts, public workflows, release metadata, and integration contracts that connect design JSON, schematic SVG, schematic IR, PCB SVG, and review manifests.

Rack And Release Gates

Rack is the suite manifest and execution model. The root manifest is tests/rack.toml. Lower strata cover focused command behavior and public workflows; L99_signoff is the release metadata, governance, and packaging gate.

A release candidate must pass the public workflow lane, the full L99 signoff lane, package build checks, and an installed-console smoke test. Large Altium fixture coverage depends on WN_TEST_CORPUS and should be recorded when it is used for release validation.

External Fixtures And Oracles

Real Altium projects and large generated artifacts live outside the Git repository under WN_TEST_CORPUS. Tests that use those projects should degrade cleanly when the corpus is unavailable and should make the dependency explicit in the test name or skip reason.

Design Review Contracts

The design-review bundle is the primary end-to-end integration surface. It must preserve links between the high-level design JSON, schematic SVG group identifiers, physical compiled pages, schematic IR, PCB SVG primitives, and manifest entries. Repeated-sheet and channel projects must prefer physical page identifiers over ambiguous logical SVG ids.

CLI Governance

Public and experimental commands are listed in docs/contracts/command_manifest.a0.json. Each command entry points to its CLI design document under docs/design/cli/. Changes to command behavior should update the relevant command design document and any public workflow tests that depend on the behavior.