What problem does it solve?
Provides a prescriptive policy and operational guidance to make Tier 3 module-level cocotb regressions consistent, traceable, and measurable so teams can reliably graduate modules to integration testing without ambiguous coverage or traceability gaps.
Core Features & Use Cases
- Policy & Naming Conventions: Enforces cocotb signal naming, clock/reset patterns, and reset sequencing to avoid common integration failures.
- Multi-Seed Regression & Execution Strategy: Defines a default five-seed strategy, parallelism rules, local-first execution, AWS gating, pipelined per-module execution, and early-termination thresholds.
- Coverage & Traceability: Specifies coverage targets (line ≥ 90%, toggle ≥ 80%, FSM ≥ 70%), merging procedures, and a requirement traceability matrix format for AC-level and REQ-level reporting.
- Use Case: Use this policy when running Phase 5 Tier 3 regressions to validate that module-level cocotb tests meet coverage targets, map failures to requirements, and produce a formal RTM for review.
Quick Start
Run the Tier 3 cocotb multi-seed regression following the policy to verify five seeds, merge coverage, and produce the requirement traceability report.