Test suites and Browse
A test suite in Qualflare groups the test cases of a project. Create, organize, clone, archive and run suites from Browse, and see what deleting one removes.
Last updated
In Qualflare, a test suite is a named group of test cases in a project: each case belongs to exactly one suite, suites form a flat list with no folders, and a suite name is unique in its project.
| Where | Browse in the project sidebar (page title Browse Suites) |
| Roles | View: Viewer+ · project (requires the Viewer role or higher in the project); create, edit, clone, archive, import: Editor+ · project (requires the Editor role or higher in the project); delete: Owner · project (requires the Owner role in the project) |
| Limit | 10 test suites per workspace on Starter; see Limits and plan availability |
| CLI | qf <identifier> suites list, qf <identifier> suite get (Suites commands) |
| MCP | list_test_suites, get_test_suite, list_suite_cases (MCP server reference) |
What is a test suite?
A test suite keeps related test cases together, so you manage a few suites instead of hundreds of single tests. Suites serve four purposes:
- Organization: group related tests together (e.g., "Authentication Tests")
- Running: pick one or more suites when you start a manual launch
- Reporting: see coverage, pass rate and run history for each suite
- Maintenance: archive a suite to hide it and its cases while keeping their history
Teams usually group suites by feature area, test type or priority.
Every test case belongs to exactly one suite. Suites are a flat list: they don't nest, and a suite name is unique within its project. When you upload results with qf <identifier> collect, Qualflare matches each suite by name and creates the ones that don't exist yet.
Suites vs test plans
Suites and test plans serve different purposes:
| Aspect | Test Suites | Test Plans |
|---|---|---|
| Purpose | Where a case lives | A selection of cases for a release or a run |
| Membership | Each case belongs to exactly one suite | A plan can pick cases from any suite |
| Created by | You, in Browse, or Qualflare when you upload test results or import test cases | You, in Test Plans, or Qualflare each time you start a launch |
A suite owns its cases. A plan only selects them, and has no schedule or assignee.
Browse
Open Browse in the project sidebar. The page, Browse Suites, lists every suite in the project. Click a suite's chevron to show its cases inline.
Columns
| Column | What it shows |
|---|---|
| Name | The test type icon, a Manual or Automated icon, the suite number (such as #12), the name, and an Archived badge when archived |
| Description | The suite's description |
| Priority | The suite's priority |
| Created | When the suite was created |
| Updated | When it last changed |
| Cases | How many cases it holds |
| Team | The team responsible. Click to assign one. |
| Coverage | The suite's coverage score |
Each row's ⋯ menu has Edit, Clone, Archive (or Unarchive) and Delete. See Suite actions.
Toolbar
- Create Suite opens the Create Suite dialog.
- Browse actions (⋮) holds Expand all and Collapse all (for the current page), Import and Export. Import takes files from Qase, TestRail, Testmo or Allure TestOps, up to 20 MB, and runs in the background. See Import and export test cases.
Filters
Filter by Priority, Test Type, Automation, Team, Archived, Flaky, Not run in 30+ days and Search.
- Flaky All plans (available on Starter, Core, Scale, Enterprise, Open Source)
- Not run in 30+ days shows automated cases whose last run was 30 or more days ago.
Bulk actions
Select suites or cases to show Delete and Archive, and Unarchive while the Archived filter is on. Delete and Archive ask you to confirm. Deleting is permanent: see Delete a suite.
Create a suite
Qualflare deletes every suite that has no cases whenever anyone in the project deletes a case. A new suite starts empty, so add a case to it right away.
Open Browse and click Create Suite
In Browse, click Create Suite. When a project has no suites, the empty state also offers Create Suite and Import.
Enter the suite's details
| Field | Required | Notes |
|---|---|---|
| Name | Yes | 3 to 200 characters, unique within the project |
| Description | Yes | What the suite covers, up to 1,024 characters. Longer text fails to save. Qualflare doesn't create a suite without a description. |
| Priority | Yes | Low, Medium, High or Critical. Defaults to Medium. |
Click Create
Click Create. The suite appears in Browse with no cases.
Suites for automated tests are created for you. When you upload results with the CLI, Qualflare matches each suite by name and creates the ones that don't exist.
Add and reorder cases
Editor+ · project (requires the Editor role or higher in the project)To add a case, open the suite, go to its Test Cases tab and click Create Case. See Create a test case.
Each case belongs to exactly one suite. You can't add an existing case to a second suite, or move a case to another suite: Move to Suite isn't available yet.
To reorder cases, drag a row by its handle, or open a case row's ⋯ menu and choose Move Up or Move Down. The order saves automatically. Reordering is off while any filter is applied in the suite's Test Cases tab, or while Not run in 30+ days is on in Browse, because the order applies to the whole suite.
Suite panel
Click a suite to open it. The header shows the suite number and name, a Manual or Automated icon, the priority, the Team selector, the number of cases, when it was created and the description.
| Tab | What it shows |
|---|---|
| Overview | Coverage, Total Cases, Pass Rate and Changes |
| Test Cases | The suite's cases. See below. |
| Run History | The suite's runs in past launches |
Test Cases tab
- Create Case adds a new case to this suite. See Create a test case.
- Filter by Priority, State, Archived and Search.
- Reorder cases by dragging a row, or with Move Up and Move Down in its ⋯ menu. See Add and reorder cases.
- Select cases for Delete, Archive and Unarchive. Move to Suite isn't available yet.
Organize suites
Suites don't nest. To keep a large project organized:
- Assign each suite to a team from the Team column in Browse, then filter Browse by Team. See Teams.
- Set each suite's priority: open the suite row's ⋯ menu and choose Edit.
- Filter by Priority, Test Type or Automation.
- Open Browse actions (⋮) and choose Expand all to review the cases on the current page.
- Save the filters as a saved query on Explore, or build a test plan, to group cases from several suites.
Run suites
Suites have no Run button. To run suites by hand, go to Launches, click Start Launch, select the suites, choose the launch settings and click Start; the Test Wizard opens.
See Start Launch · Run manual tests with the Test Wizard.
Automated results fill suites when you upload them with qf <identifier> collect.
Suite actions
All suite actions are in the suite row's ⋯ menu in Browse.
| Action | What happens |
|---|---|
| Edit | Opens Edit Suite, where you change the Name, Description and Priority. A suite's priority isn't passed on to its cases. |
| Clone | Creates <name> (Copy N) right away, where N is the new suite number. It copies the description, priority, test type and automation, and makes new copies of the suite's cases with their name, description, state, priority and type. It doesn't copy the team, case steps, tags, run history or coverage history. |
| Archive / Unarchive | Archiving hides the suite and its cases from default views and keeps their history. Turn on the Archived filter to find it. |
| Delete | Permanently deletes the suite, its cases and their results. See below. |
To assign a team, use the Team column in Browse or the Team selector in the suite header. See Teams.
Suites have no Run action. To run suites by hand, go to Launches > Start Launch and pick them. See Run suites.
Delete a suite
Deleting a suite permanently deletes all of its test cases and every result recorded for them, including the suite's runs in past launches. There's no option to keep the cases, and it can't be undone. Deleting a suite from its row menu doesn't ask you to confirm. To hide a suite and keep its history, archive it instead.
- One suite: open the suite row's ⋯ menu in Browse and choose Delete. It happens at once.
- Several suites: select them, click Delete, and confirm.
Each deleted suite is recorded in the audit log.
Permissions
| Action | Role |
|---|---|
| View suites | Viewer or higher |
| Create, edit, clone, archive and import suites, and assign teams | Editor or higher |
| Delete suites | Owner |
In the web app today, buttons follow your project role. See Roles and permissions.
Limits and plan availability
Each plan sets how many test suites and test cases a workspace can hold:
| Limit | Unit | Starter | Core | Scale | Enterprise | Open Source |
|---|---|---|---|---|---|---|
| Test suites | test suites | 10 | 50 | 200 | 20,000 | 20,000 |
| Test cases | test cases | 200 | 1,000 | 5,000 | 500,000 | 500,000 |
For prices, see qualflare.com/pricing.
Suite names are 3 to 200 characters, and a description is required, up to 1,024 characters. See Plans and limits.
Related
- Guides: Create and edit test cases · Explore Cases and saved queries · Import and export test cases · Shared Steps · Executing Tests
- Reference: Test cases: fields, states and steps · Filter syntax · Glossary: test suite
- CLI and API: Suites commands · MCP server reference
Test management overview
Manage test cases in Qualflare: organize suites, write steps, find cases on Explore Cases, import or export them, and plan with milestones and test plans.
Test cases: fields, states and steps
Every test case field, state, step type, tab and action in Qualflare, how a test case differs from a test script, and what deleting a case removes.