Testing

Overview

Testing validates delivered scope before release. Test cases should be linked to requirements for coverage tracking.

Key Concepts

• Test case: validation steps with expected outcomes
• Execution: running test cases and recording results
• Coverage: mapping of requirements to test cases
• Save View: repeatable testing review list

How It’s Used

Use test cases to validate requirements. Use linked tests for coverage reporting and go/no-go decisions.

Benefits

• Reduced release risk through repeatable validation
• Clear audit trail for validation results
• Faster scope impact analysis through linked coverage

Setup Steps

1

Create test cases

• Create Test Cases

2

Organize test views

• Test Organization and Views

3

Link tests to requirements

• Linking Tests to Requirements

Best Practices

• Require acceptance criteria before creating approval-ready tests.
• Keep test statuses consistent across Projects.
• Use Save Views for execution tracking and go/no-go readiness.

Summary

Testing validates delivered scope through linked test cases. Coverage links support governance and reporting.

Related:

• Requirements
• Working with Views