Test Management
Test Case Tags
Tags organize test cases across suites — filter by feature, team, or component from the Test Case Explorer, with autocomplete to keep labels consistent and an optional project-level rule so tagging isn't just a suggestion.
Product news and testing tips.
Why it matters
Can't filter by feature or team
Hundreds of cases, no way to pull up “everything payments owns” or “everything touching checkout” without opening each one.
Tag conventions drift across teams
One team writes "payment," another writes "payments," a third writes "Payment" — free-text labels only work if everyone agrees, and they never fully do.
Nothing enforces tagging at all
Without a project-level rule, tagging is optional advice — and optional advice is the first thing skipped under deadline pressure.
How it works
Add tags to a case with autocomplete pulling from tags already used in the project. If a project requires tagging, cases can't be saved without meeting the rule — either at least one tag, or specific categories like feature, team, and component.
What you get
Tag any test case
Add up to 10 tags per case, with autocomplete from tags already used in the project so labels stay consistent.
Filter and search by tag
Pull up every case tagged "payment" or "critical-path" from the Test Case Explorer, across every suite.
Enforce tagging at the project level
Require at least one tag on every case, or go further and require specific categories — like feature, team, and component — before a case can be saved.
Tracked in the case history
Every tag added or removed is recorded in the case's changelog, so tagging changes are auditable like any other edit.
Ready to see it on your own test results?
Start free with Qualflare — connect your pipeline, upload a run, and see this in minutes.
Get Started FreeRelated features
Frequently asked questions
How many tags can a test case have?
Up to 10 tags per case. Each tag is up to 50 characters, and can use letters, numbers, and hyphens (no spaces — use a hyphen instead).
Can I require tags on every test case?
Yes, at the project level. Tagging requirements can be set to Disabled (optional), Required (at least one tag), or Specific Tags — which requires named categories, like "feature," "team," or "component," before a case can be saved.
Are tags shared across the whole workspace?
Tags are managed as a workspace-level list (create, edit, delete with a title, name, and description), then applied to individual test cases within projects — so autocomplete suggests existing tags instead of letting spelling drift.
Do defects and milestones support tags too?
Yes — tagging isn't limited to test cases. Defects and milestones both support tags as well, using the same free-form labeling approach.