Skip to main content

Create Verification Test Cases

Design and document test cases that verify system, subsystem, and design requirements meet their specifications.

Create Validation Test Cases

Define validation test cases that confirm the system meets user needs and intended use conditions.

Link Tests to Requirements

Establish bidirectional traceability between test cases and requirements using Polarion work item forms and PowerSheet.

Use Verification PowerSheet

Leverage interactive verification sheets to manage test cases, track results, and visualize coverage across requirement levels.

Track Verification Evidence

Record and link test results, logs, and supporting evidence to verification and validation test cases.

Check Verification Coverage

Verify that all design requirements are tested and trace coverage back to system and customer requirements.

​
V-Model Test Strategy

The verification and validation process follows the V-model methodology, with tests designed at each level to confirm requirements: diagram
Each requirement level has corresponding test cases that verify specifications at that abstraction level. System requirements are verified by system verification tests. Design requirements are verified by design verification tests. Validation tests confirm the complete system meets user needs under real-world conditions.

​
Key Concepts

​
Verification vs Validation

  • Verification: “Did we build the system right?” Tests confirm that each design level meets its specified requirements (system, subsystem, design). Uses VerificationTestCase work item type.
  • Validation: “Did we build the right system?” Tests confirm that the complete system meets customer needs and intended use. Uses ValidationTestCase work item type.

​
Traceability Requirements

ISO 26262 Part 8 Clause 6 requires bidirectional traceability between:
  • Each requirement and its corresponding test case(s)
  • Test cases and design requirements (forward: requirements verify test cases)
  • Test results and test cases (via external references)

​
Test Case Organization

Test cases are typically organized in Polarion modules by level:
  • Testing/SystemVerificationSpecification — System-level verification tests
  • Testing/DesignVerificationSpecification — Design-level verification tests
  • Testing/ValidationSpecification — Validation tests (customer needs)

​
Coverage Metrics

The nxLinkCoverage macro calculates:
  • Requirement Coverage: % of requirements with linked test cases
  • Test Coverage: % of test cases with passing results
  • Trace Coverage: Bidirectional verification (requirements → tests → results)
Any design requirement classified as SC (Safety-Critical) or CC (Custom Critical) MUST have at least one linked verification test case. Gaps in SC/CC coverage are safety compliance violations and must be resolved before document approval.

​
Common Workflows

TaskReference PageTime
Create a new verification test caseCreate Verification Test Cases5 min
Link a test to a design requirementLink Tests to Requirements3 min
Bulk link tests via PowerSheetUse Verification PowerSheet10 min
Record test result and evidenceTrack Verification Evidence5 min
Check coverage across all requirementsCheck Verification Coverage5 min
Audit requirement-to-test traceabilityRequirements Traceability Report10 min

​
Getting Started

If you’re new to TestAuto2 verification workflows:
  1. Start with Create Verification Test Cases to understand test case structure and properties
  2. Move to Link Tests to Requirements to establish traceability
  3. Use Use Verification PowerSheet for bulk operations and visualization
  4. Periodically run Check Verification Coverage to audit gaps
If you need to track test results:
  1. See Track Verification Evidence for linking results and logs
  2. Use Check Verification Coverage to confirm all tests are executed
For compliance audits:
  1. Generate the Requirements Traceability Report to show bidirectional traceability
  2. Check dashboard metrics on the Testing Space Dashboard