Add docs/verification/test-strategy.md documenting Section 12 methodology #31

New issue

Closed

opened 2026-05-24 15:23:23 -03:00 by navigator · 2 comments

navigator commented

2026-05-24 15:23:23 -03:00

Owner

Goal

Write a single concise document under docs/verification/test-strategy.md that captures the verification methodology from PLAN.md Section 12 in a contributor-facing format. This becomes the canonical reference for area:verification work.

Sections to include:

Test pyramid (system 10% / integration 25% / unit 50% / formal 15%)
Tooling matrix (chiseltest, Cocotb, Verilator, Spike, Yosys-SBY)
Per-module requirements checklist (SPEC.md, unit bench, golden model, coverage targets)
PopLink-specific verification expectations (single-link, multi-VC, torus, formal, BER)
CI lane definitions referencing the four-tier CI (fast / standard / nightly / weekly)
Sign-off criteria before tapeout

Acceptance criteria

docs/verification/test-strategy.md exists
Document mirrors PLAN.md Section 12 structure but in contributor-facing language
Coverage targets stated: >=85% line / >=70% condition per module; >=95% line / >=85% condition for tapeout sign-off
CI lane table includes time budgets (5min / 30min / 4h / 24h) WITHOUT touching .forgejo/workflows/**
Cross-references PLAN.md Section 12 explicitly
Adds entry to docs/verification/README.md if it exists, or creates one

Plan refs

Section 12 (all subsections); Section 8.3 (testbench plan acceptance criteria)

Notes

Document only — does NOT modify CI workflows (off-limits per ADR-017). The doc describes what CI should run; actual workflow YAML stays for Marcos to wire up.

## Goal Write a single concise document under `docs/verification/test-strategy.md` that captures the verification methodology from PLAN.md Section 12 in a contributor-facing format. This becomes the canonical reference for `area:verification` work. Sections to include: - Test pyramid (system 10% / integration 25% / unit 50% / formal 15%) - Tooling matrix (chiseltest, Cocotb, Verilator, Spike, Yosys-SBY) - Per-module requirements checklist (SPEC.md, unit bench, golden model, coverage targets) - PopLink-specific verification expectations (single-link, multi-VC, torus, formal, BER) - CI lane definitions referencing the four-tier CI (fast / standard / nightly / weekly) - Sign-off criteria before tapeout ## Acceptance criteria - [ ] `docs/verification/test-strategy.md` exists - [ ] Document mirrors PLAN.md Section 12 structure but in contributor-facing language - [ ] Coverage targets stated: >=85% line / >=70% condition per module; >=95% line / >=85% condition for tapeout sign-off - [ ] CI lane table includes time budgets (5min / 30min / 4h / 24h) WITHOUT touching `.forgejo/workflows/**` - [ ] Cross-references PLAN.md Section 12 explicitly - [ ] Adds entry to `docs/verification/README.md` if it exists, or creates one ## Plan refs Section 12 (all subsections); Section 8.3 (testbench plan acceptance criteria) ## Notes Document only — does NOT modify CI workflows (off-limits per ADR-017). The doc describes what CI should run; actual workflow YAML stays for Marcos to wire up.