Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Create Test Cases

Overview

Test cases validate requirements through repeatable steps. Linking tests to requirements supports coverage reporting.

Key Concepts

  • Test case: steps and expected outcomes

  • Execution result: pass, fail, blocked, or not run (status set varies)

  • Coverage: mapping of requirements to test cases

How It’s Used

Use test cases during system testing and UAT cycles. Use linked coverage for go/no-go readiness decisions.

Benefits

  • Reduced release risk through repeatable validation

  • Faster triage through consistent expected outcomes

  • Better auditability through recorded execution history

Setup Steps

1

Create a test case

  1. Navigate to a Project.

  2. Open Testing.

  3. Select New test case.

2

Define steps and expected outcome

Add clear steps. Define expected outcome as an objective condition.

3

Link to requirements

Link the test case to one or more requirements. Use links for coverage reporting.

Best Practices

  • Create tests only after requirement acceptance criteria is stable.

  • Keep tests small and focused.

  • Use a consistent naming pattern, such as {Process} — {scenario}.

Summary

Test cases validate scope through repeatable steps. Links to requirements enable coverage tracking.

Related:

Last updated