Tests
Plan, run, and prove verification.
Define test cases that prove requirements are met, organize them into plans, run them, and capture evidence as you go. Verification stays linked to the requirements it proves, so coverage and suspect status are always live — never reconstructed before an audit.
Test cases, plans, and runs with pass/fail status and connected defects — verification kept on the same thread as the requirements it proves.
What it does
Verification that stays connected to what it proves.
The value of a test is not just its result — it is the live link between that result and the requirement it verifies.
Test cases with steps
Define exactly what gets verified and how, as controlled records that reference the requirements they prove.
Plans, runs & milestones
Organize cases into plans for a milestone or release, execute runs that capture pass, fail, and evidence, and plan verification over time instead of scrambling.
Defects linked back
Defects logged against a failure link to the items they affect, so nothing falls through the gap between a failed run and the work it touches.
Live coverage
Because tests trace to requirements, coverage is something you measure and prove — which requirements are verified, which are not, and where a change left a gap.
On the thread
Coverage as a first-class signal.
Tests turn “is everything verified” from a hopeful yes into a defensible one, because the links are real.
Each test case references the requirements it proves, so coverage and suspect status stay current.
Runs connect to the model elements they exercise, tying verification to the design.
A release bundle carries its verification results, so what shipped is provably what was tested.
Derive with AI
Derive test cases from your requirements.
Point the governed derivation engine at a set of requirements and it proposes the verification they need — test cases and a plan — each cited to the requirement it covers. You review, cherry-pick, and accept; nothing is written until you do.
Prove it, and keep proving it.
Run verification that stays linked to the requirements it covers — so coverage is always live and always defensible.