Skip to main content

​
Steps

​
1. Navigate to Verification Sheet

Open the appropriate verification PowerSheet for your requirement level:
  • System Requirements: Testing/SystemVerificationSpecification (System Verification Sheet)
  • Subsystem Requirements: Testing/SubsystemVerificationSpecification (Subsystem Verification Sheet)
  • Design Requirements: Testing/DesignVerificationSpecification (Design Verification Sheet)
The sheet displays a three-tier view: diagram

​
2. Expand Evidence Columns

Click the icon on the Verification Evidence column group (red header) to reveal evidence attachment fields. Each test case row now shows expandable evidence slots. If evidence already exists, you’ll see the artifact name and type.

​
3. Attach Evidence Artifacts

For each verification test case that has been executed:
  1. Click the evidence cell in the red column group
  2. Select attachment type:
    • Test Report (PDF)
    • Test Log (TXT, LOG)
    • Analysis Results (XLS, CSV)
    • Screenshots (PNG, JPG)
    • Video Recording (MP4)
  3. Upload the file or paste the external URL
  4. Add description explaining what this evidence proves
If you have multiple evidence files from a test campaign, attach them all to the relevant test case in one session. Use consistent naming: TC-{TestID}-{EvidenceType}-{Date}.ext
Some evidence artifacts (like system integration test reports) may verify multiple test cases:
  1. Upload the evidence to the first test case
  2. Copy the evidence URL from the attachment field
  3. Navigate to other test cases that share this evidence
  4. Paste the URL as an external reference (don’t re-upload)
This creates reusable evidence without file duplication.

​
5. Verify Traceability Chain

Use the PowerSheet expansion to confirm the complete chain: 
Requirement → Test Case → Evidence

Example:
SysReq-123 "Brake response time < 100ms"
  ├── VTC-045 "Measure brake actuation latency"
  │   ├── TestReport-VTC045-2026-02-15.pdf
  │   └── LabLog-BrakeTest-Run3.txt
  └── VTC-046 "Verify brake response under load"
      └── LoadTestResults-VTC046.csv
All three tiers should be visible when the sheet is fully expanded.
ISO 26262 Part 4-6 requires objective evidence for all verification activities. A test case without linked evidence cannot be counted as verified during safety assessment. The Risk Control Effectiveness Report will flag test cases without evidence as “Verification Gaps.”

​
6. Check Coverage with Dashboard

Navigate to Testing Space Dashboard and locate the Verification Evidence Coverage widget. This macro-driven widget shows:
  • Total test cases (by requirement level)
  • Test cases with evidence (green count)
  • Test cases without evidence (red count)
  • Coverage percentage
LevelCoverageStatus
System Level45/50 (90%)Compliant
Subsystem Level23/30 (77%)Attention needed
Design Level12/40 (30%)Non-compliant
Click the counts to drill down to specific test cases missing evidence.

​
7. Address Evidence Gaps

For test cases flagged as missing evidence:
  1. Not yet executed: Schedule test execution, attach evidence afterward
  2. Executed but not documented: Retrieve logs/reports from test environment, upload retroactively
  3. Evidence lost: Re-execute test case if required for compliance
  4. Test case obsolete: If requirement changed and test is no longer relevant, remove the test case link from the requirement
Per ISO 26262 Part 8, retain all verification evidence for the product lifecycle plus the statute of limitations period (typically 10+ years). Store evidence in version-controlled artifact repository, not just Polarion attachments.

​
Verification

You should now see:
  • ✅ Evidence artifacts attached to all executed test cases
  • ✅ Green coverage percentages (≥80%) in the Testing Space Dashboard
  • ✅ Complete traceability chain visible in expanded PowerSheet view
  • ✅ No “Verification Gaps” warnings in the Risk Control Effectiveness Report

​
See Also