A suite is a folder for test cases. You create suites around functional areas, features, or testing domains, whatever grouping helps your team find and run the right cases quickly.
Suites can nest inside each other to form a tree: a top-level "Payments" suite might contain child suites for "Checkout," "Refunds," and "Subscriptions."
Suites carry no test logic themselves. They're purely organizational. The power is in the hierarchy, a well-structured suite tree means your team can select entire branches when building test plans or starting test runs.
Creating a suite
Click + Suite or Create New Suite in the repository view. The creation form has four fields:
Field | Required | Purpose |
Suite Name | Yes | A clear name for the testing area (e.g., "User Authentication") |
Parent Suite | No | Place this suite inside an existing suite to create nesting |
Description | No | Context about what this suite covers and which cases belong here |
Preconditions | No | Steps or state required before executing any case in this suite |
Only the name is required. Start simple and add detail as your repository matures.
Nesting and hierarchy
Suites support unlimited nesting depth. To create a child suite, set the Parent Suite field during creation.
You can reorganize suites by dragging and dropping them in the suite tree, both to reorder within a level and to move a suite under a different parent. This works in the Nested Tree view and the Mind Map view.
Repository views
Qase provides three ways to navigate your suite structure:
Nested Tree View (default) — Shows all suites expanded in a tree. Best for small-to-medium repositories where you want everything visible at once. Open the suite tree sidebar to jump between suites.
Folder View — Displays only the currently selected suite and its immediate children. Better for large repositories with deep hierarchies — it reduces noise and lets you focus on one area at a time.
Mind Map View (Beta) — Renders suites and cases as an interactive mind map. Useful for visual thinkers and planning sessions. You can create cases and suites, drag nodes to restructure the hierarchy, and edit case titles directly from this view.
Switch between views using the layout toggle icon next to the Suite section header.
Cloning a suite
Hover over a suite and click the clone icon to duplicate it. The clone dialog lets you choose:
Project — clone into the same project or a different one
Clone Destination — where the cloned suite should land
Clone strategy — whether to include child suites and their cases
Prefix — an optional label to distinguish the clone
Cloning is useful when setting up a new project with a similar structure, or when creating a variant of an existing test area.
Deleting a suite
Click the trash icon on any suite to delete it. Deleted suites cannot be restored from the Trash Bin, only individual test cases can be recovered. Delete carefully, especially for suites with nested children.
FAQ
Can I move test cases between suites?
Yes. Edit the case and change its Suite field, or drag it in the Mind Map view. The case keeps its ID and history regardless of which suite it belongs to.
Is there a limit to nesting depth?
No technical limit, but we recommend keeping hierarchies to 3–4 levels. Deeper nesting makes it harder to find cases and creates unwieldy test plans.
What happens to cases when I delete a suite?
The cases inside the suite are also deleted. If the suite has child suites, those and their cases are deleted too. Individual cases can be restored from the Trash Bin, but the suite structure itself cannot.