Test Suites

Test Cases

Overview

A test suite is a named collection of test cases grouped by a common purpose — a feature area, a sprint's scope, a regression set, or a release checklist. Suites let you run a focused subset of your test library without filtering every time.

A test case can belong to more than one suite. This means you can have a "Regression" suite containing all smoke tests and also a "Sprint 12" suite containing only the tests relevant to that sprint — the same test case appears in both without duplication.

Creating a test suite

1Navigate to Test Cases in the project sidebar
2Click the Suites tab
3Click + New Suite
4Enter a name — use something specific like "Checkout Flow — Regression" rather than "Suite 1"
5Optionally add a description explaining the suite's scope
6Click Create

Organising test cases in suites

ActionHow
Add test caseOpen suite → click Add Test Case → search or create new
Move test caseDrag the test case row to a different suite, or use the ⋮ menu → Move to Suite
Copy test case⋮ menu → Copy to Suite — creates a linked copy in the target suite
Remove from suite⋮ menu → Remove — removes from suite but keeps the test case in the project
Rename suiteClick the suite name inline and edit, or open suite settings
Archive suiteSuite settings → Archive — hides from active views but preserves history

Running a test suite

You can start a test run scoped to a specific suite rather than running all test cases:

1Open the suite from the Suites tab
2Click Run Suite
3Give the run a name (e.g. "Sprint 12 — Pre-release")
4Optionally link the run to a sprint or release
5Click Start Run — a test execution session opens with only the cases in this suite

Common suite patterns

  • Feature suite — all test cases for a specific feature or module. Good for testing a new feature end-to-end.
  • Regression suite — core flows that must pass before any release. Keep this lean — too many cases means it never gets run.
  • Sprint suite — test cases created or updated during a sprint. Useful for sprint-scoped test execution before close.
  • Release suite — the specific test cases that need to pass before a release is marked ready. Can be created from a release template.
  • Smoke suite — the smallest set of tests that confirms the system is alive after a deployment. Usually 5–15 cases.
Avoid creating a suite for every sprint and never reviewing it. Suites accumulate fast. Retire sprint suites after the sprint closes, or promote the most important cases into a permanent regression suite.

Troubleshooting

I can't find the Test Suites option

Test Suites appear in the Test Cases section of the project. Navigate to the project and click Test Cases in the left sidebar, then look for the Suites tab at the top.

A test case appears in multiple suites

That's expected — one test case can belong to multiple suites. The same test case being in both a regression suite and a feature suite is a valid organisation strategy. Changes to the test case (steps, expected results) are reflected in both.

Deleting a suite deleted my test cases

Deleting a suite removes the suite and its contents. If you only want to remove the grouping, use Archive instead of Delete, or move the test cases to another suite first.

I can't reorder suites

Suites can be reordered by dragging the suite header row in the sidebar. If drag-and-drop isn't working, try refreshing the page.

On this page