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

Test Organization and Views

Organize test cases with saved views so execution stays clean and reviewable.

Overview

Test cases grow quickly during delivery.

Views keep execution organized and reviewable.

Screenshot placeholder: test case list with filters and a saved-view menu.

Key Concepts

  • Test case: verification step tied to scope

  • Phase: execution grouping, such as system test or acceptance test

  • Status: readiness and outcome signal

  • Save View: repeatable view configuration for execution

How It’s Used

Use test views during execution cycles.

Use them during governance to review readiness and defects.

Benefits

  • Faster execution through standardized views

  • Cleaner handoffs across testers

  • Better coverage visibility when tests link to requirements

Setup Steps

1

Define minimal fields

Use a minimal structure:

  • Status: Draft → Ready → In progress → Passed/Failed

  • Phase: System test, acceptance test, regression

  • Priority: High/Medium/Low

  • Owner: one accountable Teammate

2

Open Tests

  1. Open the Project.

  2. Go to Tests.

  3. Choose List or Board view (if supported).

3

Filter and group for execution

Common execution views:

  • UAT — Ready to run (Phase = UAT, Status = Ready)

  • UAT — Blocked (Status = Blocked)

  • Failed — Needs retest (Status = Failed)

Screenshot placeholder: grouping by Status with a Phase filter applied.

4

Save and share

  1. Click Save view.

  2. Name it with a consistent prefix.

    • For example: Tests — UAT — Ready

  3. Share to the team when Project permissions allow sharing.

Best Practices

  • Keep status meanings consistent across execution cycles.

  • Keep phase names consistent across Projects when possible.

  • Link tests to requirements early for coverage reporting.

See Linking Tests to Requirements.

Troubleshooting

My test list looks empty

Check:

  • Project selector (when multiple Projects exist)

  • Filters (Phase, Status, Owner)

  • Archived or hidden items

Quick fix: clear filters, then reapply.

Status meaning differs across teams

Pick a minimal workflow.

Keep “Draft” and “Ready” separate.

That prevents half-written tests from entering execution.

Summary

Test views keep execution structured.

They also make governance review faster and more consistent.

Related:

Last updated