Skip to main content

​
Prerequisites

  • Test cases created in Testing space (Verification or Validation)
  • External evidence artifacts accessible via URL
  • Project permissions to edit test cases

​
Steps

​
1. Open the Test Case

Navigate to the test case that needs evidence linkage:
  1. Go to Testing space from Home dashboard
  2. Open the relevant verification or validation specification document
  3. Locate the test case requiring external evidence
  4. Click to open the work item form
In the test case form:
  1. Scroll to External References section
  2. Click ➕ Add External Reference
  3. Enter the external URL:
    • JIRA test execution: https://jira.company.com/browse/TEST-123
    • Jenkins build: https://jenkins.company.com/job/regression/456/
    • Test management tool: https://testmgmt.company.com/run/789
  4. Add a description: "Test Execution Report - Build 456 - PASSED"
  5. Click Add

​
3. Set Reference Type (Optional)

For better organization, use the reference type field:
TypeUse Case
Test ExecutionLinks to test run results in external test management systems
Build ArtifactLinks to CI/CD build outputs proving test execution
Evidence ReportLinks to detailed test reports or logs
Video RecordingLinks to recorded test sessions for validation evidence
External URLs must be accessible to all stakeholders who need to review evidence. Avoid localhost URLs, temporary file shares, or authentication-required links without documenting credentials separately.
Check that the link appears in verification tracking: 
Test Case                    External Evidence
─────────────────────────────────────────────────────
TC-SYS-001: Brake Response   → Test Execution Report
                               https://jenkins...456
The evidence link will now appear in:
  • System Verification Sheet (guides/verification/use-verification-powersheet.md)
  • Design Verification Sheet (for design requirement tests)
  • Validation PowerSheets (for customer requirement tests)

​
5. Bulk Linking Pattern (Multiple Tests)

For linking many test cases to the same evidence source: 
Evidence Artifact              Linked Test Cases
──────────────────────────────────────────────────
Jenkins Build #456            ├── TC-SYS-001
  URL: https://jenkins.../456 ├── TC-SYS-002
  Type: Test Execution        ├── TC-SYS-003
                              └── TC-SYS-004
Add the same external reference URL to each test case, or use Polarion’s bulk edit feature:
  1. Select all test cases in the document
  2. Right-click → Edit Multiple Work Items
  3. Add external reference to all selected items

​
PowerSheet Evidence Column

The verification PowerSheets display external evidence in the third column tier:
RequirementsVerification TestsEvidence
SYS-REQ-001TC-SYS-001Jenkins #456
TC-SYS-002JIRA TEST-123
This implements the complete V-model traceability chain per ISO 26262 Part 4, Section 6: Requirements → Test Cases → Objective Evidence.
For ISO 26262/14971 compliance, use external references to link to immutable evidence artifacts (archived test reports, signed-off build outputs). Avoid linking to live dashboards that change over time.

​
Verification

You should now see:
  1. External reference icon in test case work item
  2. Evidence URL column populated in verification PowerSheet
  3. Clickable link to external evidence artifact
  4. Evidence count in Risk Control Effectiveness Report (reference/reports/risk-control-effectiveness.md)

​
Common Issues

ProblemSolution
Link not showing in PowerSheetCheck that externalReferences link role is in RTM model expansion path
URL inaccessibleVerify URL is public or document VPN/auth requirements
Multiple evidence per testAdd multiple external references; each appears as separate row in evidence column

​
See Also