Link tests to the model
The Tests viewpoint closes traceability with typed verification intent. A TestCase identifies the elements and interfaces under test and links directly to the requirements it verifies.
val staleObservationTest = TestCase(
name = "Stale observation is rejected",
description = "Given a sensor observation older than 100 ms, when one fusion cycle runs, " +
"then the observation is excluded and degraded health is published within 50 ms.",
asil = ASIL.B,
elementsUnderTest = listOf(fusionActivity),
interfacesUnderTest = listOf(fusionActivity.cameraInput, fusionActivity.fusionHealthOutput),
verifies = listOf(fusionRequirements.rejectStaleObservations),
)
Keep test cases inside a Tests with an explicit subject element. Use Given/When/Then structure, explicit ASIL, real elements and interfaces under test, and typed verifies links. Missing required attributes and references are HIGH findings. Element boundary flags do not waive test verification; there are no per-test or per-container assumed switches.
Check and render
./gradlew :path:to:element:stigCheckModel
./gradlew :path:to:element:stigGenerateHtml
See the Tests section of the generated model-rule catalog for the exact current checks.
Ask $stig:specification
Use $stig:specification to review the Tests viewpoint for <module path>. Check Given/When/Then
structure, elements and interfaces under test, ASIL, and typed requirement
coverage. Report uncovered or inconsistent links without editing.
23 October 2026