docs: place the appliance in the four-tier testing model - #885
Merged
Conversation
testing-strategy.md is the map of what is tested where, and the appliance surface appeared nowhere in it — two different things were called tier 4 with different entry points and prerequisites. Tier 4 has one meaning (what only reality proves) and two harnesses, one per distribution channel: the live matrix for a DIY install, the KVM battery for the flashed image. The new section J catalogs the wizard's tier-1 tests, verify-image's static build-time assertions, and every battery phase, and the run/gate tables gain the battery's command line and its release-gate row. Closes #869 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This was referenced Aug 4, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #869
testing-strategy.md is the map of what is tested where, and the appliance surface appeared nowhere in it — two different things were called "tier 4" with different entry points, prerequisites, and release gates. The doc now says what is actually true: tier 4 has one meaning (what only reality proves) and two harnesses, one per distribution channel — the live matrix for a DIY install, the KVM battery for the flashed image.
New section J catalogs the appliance surface at its honest tiers: the wizard's Q&A→config logic at tier 1 (
test_wizard.py+wizard.test.mjs),verify-image.shas static build-time assertions (no KVM), and every battery phase — boot, update, install, provision (including the commit-gate honesty legs and the migration hold), rig, and the opt-in fault phase. The run-commands section gains the battery's invocation and the release-gate table gains its row.Depends on #883 for two of the cataloged rows (the migration-hold leg and its README wording) — merge after it.
make lint-mdandmake lint-docs-voicegreen; every row is derived fromtests/os/run.shandtests/os/README.mdon the branch state it documents.🤖 Generated with Claude Code