Prerequisites
- VerificationTestCase or ValidationTestCase work items created and linked to requirements
- Test Run created in Polarion Test Management
- Test Cases added to the Test Run
Link Test Cases to Test Runs
Option 1: From Test Case Work Item
- Open the test case work item (VerificationTestCase or ValidationTestCase)
- Navigate to the Links section in the form layout
- Click Add Link → Test Records
- Select the Test Run from the picker dialog
- Click Save
Option 2: From Test Run Interface
- Navigate to Testing space in the sidebar
- Open the target Test Run document
- In the Test Run editor, click Add Test Cases
- Search for or select the verification/validation test cases to include
- Click Add
The Test Run automatically creates bidirectional links between Test Record entries and the source test case work items.
Use Test Runs for regression testing or periodic verification campaigns. Each Test Run instance preserves execution history while the test case work item stores the test design.
View Test Execution Status in PowerSheets
Once linked, test execution results appear automatically in PowerSheet views:
System Verification Sheet
The System Verification Sheet shows a three-tier expansion:
| Column Group | Data Displayed |
|---|
| System Requirements (purple) | Requirement ID, description (read-only) |
| Verification Tests (orange) | Test case ID, title, status |
| Test Run Results (green) | Latest execution result, executed by, executed on |
Test results propagate from the most recent Test Run record linked to each test case.
Design Verification Sheet
Similar pattern for design-level verification:
Color-coded columns show requirement → test → execution status chain.
Interpret Test Results
Test Run execution status values:
| Status | Meaning | Action Required |
|---|
| ✅ Passed | Test executed successfully, requirement verified | None — verification evidence complete |
| ❌ Failed | Test detected requirement violation | Investigate failure, create defect work item, retest |
| ❓ Blocked | Test cannot execute (missing precondition, environment issue) | Resolve blocker, reschedule test |
| Not Run | Test included in run but not yet executed | Execute pending tests |
Each new Test Run execution updates the test case’s latest result. Historical results are preserved in Test Run records, but PowerSheet always shows the most recent execution status. To track result history, review individual Test Run documents.
Workflow Diagram
Track Verification Coverage
After executing Test Runs, verification coverage metrics update automatically:
- Navigate to Testing Space Dashboard
- Review Verification Coverage bar chart
- Drill down into gaps:
- Requirements with no linked test cases
- Test cases not included in any Test Run
- Test cases with “Failed” or “Blocked” status
ISO 26262 Part 4 requires 100% verification coverage with evidence of passing test results for all ASIL-rated requirements.
Use the Verification Coverage Report (see Generate Coverage Report) to export verification status for safety audits. The report cross-references requirements, test cases, and Test Run results in a single view.
Verification Steps
After linking test cases to Test Runs:
- Open System Verification Sheet or Design Verification Sheet
- Expand a requirement row to show linked test cases
- Expand a test case row to show Test Run results
- Verify Status column shows latest execution result
- Verify Executed On date matches expected Test Run schedule
You should see a three-tier expansion with live test execution status propagated from Test Run records. Failed or blocked tests appear highlighted (if configured in cell decorators).
See Also