Skip to main content

​
Steps

​
1. Navigate to the Testing Space

From the main navigation sidebar, click Testing or V&V to open the Testing Space dashboard. This displays all test specifications organized by verification level (system, subsystem, design).

​
2. Select or Create a Test Specification Document

Locate the appropriate test specification document for your verification level:
  • SystemVerificationSpecification — for system requirement verification
  • SubsystemVerificationSpecification — for subsystem requirement verification
  • DesignVerificationSpecification — for design requirement verification
If the document doesn’t exist, create it through Documents > Create Document, selecting the testsSpecification document type and placing it in the Testing/ folder.

​
3. Create a New Verification Test Case

Within the test specification document:
  1. Click the ➕ Add Work Item button
  2. Select Verification Test Case as the work item type
  3. Fill in the required fields:
    • Title: Brief description of what is being verified (e.g., “Verify radar detection range specification”)
    • Description: Detailed test objective and acceptance criteria
    • Test Procedure: Step-by-step instructions to execute the test
    • Expected Result: Observable outcome indicating requirement satisfaction
Example Verification Test Case Structure: Title: Verify Camera FOV meets 120° horizontal specification Description: Validate that the Camera Module achieves the specified 120° horizontal field of view per Design Requirement DR-CAM-005. Test Procedure:
  1. Mount camera in test fixture at standard installation angle
  2. Position calibrated target grid at 5m distance
  3. Capture image and measure angular coverage using tool XYZ
  4. Record horizontal FOV angle measurement Expected Result: Measured horizontal FOV = 120° ± 2°
Establish verification traceability using the verifies link role:
  1. In the Verification Test Case work item, scroll to the Links section
  2. Click Add Link and select verifies as the link role
  3. Search for and select the requirement(s) being verified
  4. Save the work item
Use the System Verification PowerSheet or Design Verification PowerSheet to create test cases and establish verification links in a single interface. The entity factory feature allows inline test case creation directly from requirement rows.

​
5. Set Classification and Priority

Configure test case metadata for filtering and reporting:
  • Classification: Set to match the requirement classification (SC for Safety Critical, CC for Conformance Critical, or blank for standard requirements)
  • Priority: Assign based on requirement ASIL level or business criticality
  • Test Type: Select “Verification” (distinguishes from validation test cases)
Requirements classified as SC (Safety Critical) or CC (Conformance Critical) must have at least one linked verification test case to achieve 100% verification coverage in the Safety Readiness Scorecard. Use the Check Verification Coverage workflow to identify gaps.

​
6. Add Test Evidence References

Link supporting artifacts that demonstrate test execution:
  1. In the External References section, click Add Reference
  2. Enter URLs or file paths to:
    • Test execution logs
    • Measurement data files
    • Screenshots or videos
    • Laboratory reports
    • Certification documents
This establishes the complete verification chain: Requirement → Test Case → Evidence. Verification Evidence Chain: Design Requirement (DR-CAM-005) ↓ [verifies] Verification Test Case (VTC-CAM-014) ↓ [externalReferences]
  • Test Report: camera_fov_test_2026-02-15.pdf
  • Laboratory Data: fov_measurements.csv
  • Calibration Certificate: cal_cert_12345.pdf

​
7. Organize by Test Phase

Group verification test cases by V-model phase using outline numbering or document sections:
  • 1. Component Verification — Design requirement verification at component level
  • 2. Subsystem Integration — Subsystem requirement verification with integrated components
  • 3. System Integration — System requirement verification with integrated subsystems
  • 4. Safety Validation — Safety goal and functional safety requirement verification
This hierarchical organization mirrors the V-model verification strategy and supports phased test planning.

​
Verification

You should now see:
  • ✅ New verification test case work item with complete test procedure
  • ✅ verifies link role connecting test case to requirement(s)
  • ✅ Test case classification matching requirement SC/CC status
  • ✅ External evidence artifacts linked via externalReferences
  • ✅ Test case visible in Verification PowerSheet expansion rows
  • ✅ Updated verification coverage percentage in Testing Space Dashboard
When you navigate to the requirement being verified, the Verified By section should display your new test case in the backlinks panel.

​
See Also