SpecLink

Documentation
Source

The records that define expected verification before a run occurs.

Requirements, tests, checks, and mappings

Requirement metadata

  • A project-unique requirement ID, title, description, spec section, owner, rationale, and category.
  • Priority values from low through critical and lifecycle states draft, active, or deprecated.
  • Nested requirement categories with project-unique category codes.

Tests and checks

RecordImportant fields
Test Project-unique ID, directed/constrained-random/formal/manual type, source path, enabled flag, owner.
Check Test-local ID, name, scoreboard/assertion/coverage/manual/monitor/comparison type, optional source path and line.
RequirementTestMapping Required-for-closure flag, role, and rationale.
RequirementCheckMapping Required-for-closure flag, expected count, closure role, and rationale.

Mappings drive generated expectations

For each test, package generation selects required check mappings belonging to requirements that are mapped to that test. The resulting expectation table tells the runtime which requirement/check pairs should appear when a named test runs.