Search, filter, tag and switch off test cases

The Test cases page lists every test case in the project with its last result, the plans it belongs to, its tags, its last change and whether it is enabled.

Column	Shows
Name	The test case. Click it to open the editor. New marks a test case Self-driving wrote this week.
Last run	The status of its most recent test and how long ago it ran, or Never.
Plans	The plans it belongs to, or Not in a plan. Up to two are named; +N stands for the rest.
Tags	Its tags.
Last change	How long ago it last changed, and Self-driving when Self-driving made that change and nobody saved it since.
Enabled	Whether it takes part in runs.

• Search test cases matches names and tags as you type. Press / to jump to it.
• Tags shows test cases that have every tag you tick.
• Status: All, Enabled or Disabled.
• Plan: Any plan, one plan, or Not in a plan.
• Last change: Last changed by anyone or Last changed by Self-driving, to review what it wrote and fixed.
• Group by: No grouping, Group by Plan or Group by Tag. A test case in several plans or with several tags appears in each group.

When some test cases are in no plan, a hint above the list says how many; click show to list just those. A test case in no plan only runs when you run it on its own or run all test cases, so the hint helps you catch tests that no schedule covers.

Tags are free text, saved in lower case. Add them in the test case editor. Use them for cross-cutting groups such as smoke, checkout or regression:

• Filter the list by tag.
• Start a run of every test case with a tag from CI or an AI agent. See Run tests from CI.

Plans are the better tool for a set you run together on a schedule; tags are for slicing the suite.

The Enabled switch on each row, also in the editor, takes a test case out of every run without deleting it: all test cases, plans, schedules and tags. Use it for a test that is failing for a known reason while the fix is on its way.

• A switched-off test case can’t be run on its own either.
• Its tests already waiting in the queue are skipped and not charged. A test already running finishes.
• It stays in its plans, and comes back into their runs when you switch it on.

Changing Enabled needs the Editor role or above. Self-driving may switch off a test that no longer makes sense; Undo on its change switches it on again.

While an exploration has suggestions nobody has added or declined, a banner at the top of the page says how many are waiting. Click it to review them. See Review and add suggestions.