Skip to content

US-PAGES test specification

Use one real open spec and a synthetic accepted fixture with exact merged-code and passing-test receipts. Never mark a real spec accepted to satisfy a fixture. Record the existing catalog, architecture, and roadmap URLs before layout changes.

Scenario Requirements Expected result and evidence
Contribution navigation FR1 Pages build exposes guide and four skill links; CI link check resolves each.
Canonical edit FR2 A fixture edit changes output on rebuild without a maintained copy.
Open and accepted status FR3 Open entry shows pending evidence; accepted fixture has exact merged-code/test links; missing receipts fail validation.
Checkout isolation FR4, FR6 Required checks run with only this checkout and disposable dependencies; no sibling README or private service.
URL compatibility FR5 Deployed old URLs return content or working redirects; record HTTP smoke result.
Negative cases FR2, FR3, FR5 Missing source, broken internal link, invalid status, or absent redirect fails with affected path.
Live deployment FR5, FR6 Post-merge or scheduled Pages run reports deployed URL smoke separately.

Run pre-commit run --all-files for configured repository quality. For added code, run focused tests and configured CCCC/jscpd/Dupehound checks if present. Record absent commands or thresholds; do not claim a pass. Accepted status requires verified merged implementation and passing acceptance evidence.

Rows

Test Requirement Level and setup Expected observation
tests/pages_contracts.py::test_canonical_sources_and_existing_urls US-PAGES-R002 Offline MkDocs build of a disposable checkout Navigation links resolve and an edited canonical file changes the output.
tests/pages_contracts.py::test_navigation_matches_shared_template US-PAGES-R001 Planned. Compare the nav tree of mkdocs.yml with the shared template The hierarchy matches the template used by the other documentation sites.