Steps
1. Navigate to Validation Test Specification
Open the Testing space from the sidebar, then select the validation test specification document corresponding to your customer requirements module. Validation specifications are typically named <Module Name> - Validation Specification.
Validation tests answer “Did we build the right system?” (customer requirements) while verification tests answer “Did we build the system right?” (system/design requirements). Validation uses the validates link role, verification uses verifies.
2. Create New Validation Test Case
Click Add Work Item in the document toolbar, then select Validation Test Case from the work item type dropdown.
Fill in the required fields:
- Title: Descriptive test case name (e.g., “Validate AEB activation under 30 km/h”)
- Description: Detailed test procedure, expected behavior, and acceptance criteria
- Preconditions: Initial system state, test environment setup
- Test Steps: Numbered procedure steps
- Expected Result: Observable outcome proving customer requirement satisfaction
3. Link Test to Customer Requirements
In the Validated Requirements field (or linkedWorkItems custom field), select the customer requirement(s) this test case validates. Use the work item picker to search by ID or title.
The link role validates establishes bidirectional traceability:
- From test case →
validates → customer requirement
- From customer requirement →
is validated by → test case
Only customer requirements with at least one linked validation test case will count as validated in the Safety Readiness Scorecard metrics. Ensure every customer requirement has validation coverage.
| Field | Purpose | Example Values |
|---|
| Test Type | Validation method per ISO 26262 Part 4 §8 | Review, Analysis, Simulation, Testing |
| Priority | Execution priority | High, Medium, Low |
| Automation Level | Degree of automation | Manual, Semi-Automated, Fully Automated |
| Test Environment | Execution context | HIL, Vehicle, Simulation |
5. Add Evidence and Results
After test execution, attach evidence to the validation test case:
- Test reports (PDF, Excel)
- Logs and screenshots
- Video recordings (for physical validation)
- Simulation output files
Update the Status field to reflect execution state: Draft → Ready for Execution → Executed → Passed/Failed.
6. Check Validation Coverage
Navigate to Requirements Space Dashboard and scroll to the Traceability Coverage section. The nxLinkCoverage macro displays:
Click the gap count link to see which customer requirements lack validation test cases.
Open the User Need Validation Sheet PowerSheet for a tabular view showing customer requirements in the left column group and linked validation test cases in the right column group (orange header). Add test cases inline using the entity factory.
Verification
You should now see:
- New validation test case work item(s) in the validation specification document
- Bidirectional
validates links between test cases and customer requirements
- Increased validation coverage percentage on the Requirements Space Dashboard
- Test cases appear in the Validation Plan column of the Whole RTM Sheet PowerSheet
See Also
