01 · Capability
Case repository
Folders, tags, priorities, and reusable steps — the backbone of serious test management.
Your test cases are the single source of truth for what “done” means before every release. QualiTag gives you a structured repository that scales from a handful of smoke checks to thousands of regression scenarios — without collapsing into spreadsheet sprawl or wiki pages nobody trusts.
Organize work the way your team already thinks: product areas in folders, risk levels through priorities, and discoverability through tags. Reusable step libraries mean you define “log in as admin” once and reference it across dozens of suites, so updates propagate everywhere instead of silently rotting in copy-pasted rows.
Every case carries history — who changed it, when it last ran, and whether automation or manual execution owns it. That audit trail turns your repository from a static document into a living map of product quality.
Key outcomes
- One authoritative catalog instead of scattered docs and Slack threads.
- Faster onboarding — new QA hires browse folders instead of shadowing for weeks.
- Less duplication — shared steps eliminate “which login case is correct?” debates.
- Clear release scope — filter by tag + priority to build the right suite every time.
Capabilities
Hierarchical folders
Nest folders by product module, squad, or release train. Drag-and-drop structure mirrors your org without forcing a single flat list.
Tags and custom fields
Tag cases by platform, persona, risk tier, or compliance scope. Filter and bulk-assign in seconds when scope changes mid-sprint.
Priority and severity
P0–P3 (or your own scale) surfaces what must pass before ship. Sort dashboards and run queues by priority automatically.
Reusable step templates
Shared steps for login flows, API setup, or device prep. Edit once — every linked case picks up the change on next run.
Rich step definitions
Expected results, preconditions, attachments, and links to requirements. Manual testers get clarity; automation authors get unambiguous targets.
Version awareness
See which cases changed since the last milestone. Diff-friendly history helps release managers sign off with confidence.
Bulk import and export
CSV in/out for migration from legacy tools. Bring historical cases without retyping years of tribal knowledge.
Search across everything
Full-text search across titles, steps, tags, and IDs. Find “checkout coupon” in three keystrokes, not three meetings.
How teams use it
- 1
Define structure
Create folder tree aligned to product areas or squads.
- 2
Author cases
Write steps manually, import CSV, or promote from exploratory findings.
- 3
Tag and prioritize
Apply P0–P3 and tags so release scope is always filterable.
- 4
Reuse libraries
Link shared steps for common flows — login, reset, permissions.
- 5
Maintain over time
Review change history and retire obsolete cases each milestone.
Common scenarios
- →Regulated teams documenting evidence-ready test definitions for audit.
- →Mobile squads maintaining platform-specific cases under one product folder.
- →Teams migrating off spreadsheets who need structure without a six-month rollout.
- →Organizations standardizing onboarding flows as reusable step blocks across apps.
Best practices
- · Keep folder depth shallow (3 levels max) so browse stays intuitive.
- · Reserve P0 for ship-blockers; inflation erodes trust in the priority field.
- · Name reusable steps with verbs (“Login as standard user”) not screen IDs.
- · Review orphaned cases quarterly — stale inventory hides real gaps.