Test Case Templates

A test case template in QAM Hub is a reusable, pre-filled blueprint for new test cases. Instead of rewriting the same title pattern, step structure, expected result, automation status, and custom fields every time, your team defines a template once and applies it when creating a case. Templates are project-scoped — each project keeps its own set.

This guide covers what a template stores, how to create one, and how applying it works. To create the cases themselves first, see creating test suites and test cases.

What a template stores

Each template captures the default content a new test case should start with:

• Name — the template's own label, shown in the picker (e.g. "API endpoint test", "UI smoke check").
• Description — an optional hint that helps users choose the right template.
• Category — an optional grouping label (e.g. "API", "UI", "Regression"). Templates are grouped by category in the UI; those without one appear under "Uncategorized".
• Title — the pre-filled test case title.
• Steps — the pre-filled test steps.
• Expected Result — the optional pre-filled expected result.
• Automation status — the default state (Not / Yes / In Progress / Not Possible / Backlog).
• Custom fields to include — a selected set of the project's custom fields that appear, ready to fill in, on cases created from the template.

Creating and managing templates

Templates are managed in Project Settings → Test Case Templates:

1. Click Add template and fill in the name, optional category and description, and the title / steps / expected-result content.
2. Tick which of the project's custom fields the template should include.
3. Save. The template now appears in the list, grouped by category.

Existing templates are listed by category, each showing its name, category badge, description, and the custom fields it carries (as tags). An expand control reveals a read-only preview of the title, steps, and expected result. Templates can be edited inline (pencil icon) or deleted (trash icon, with a confirmation showing the template name).

Applying a template to a new test case

You apply a template when creating a case in a suite:

1. When adding a new test case, click "From template."
2. A modal lists available templates grouped by category, each with its name, description, and a preview of its title.
3. Select one. The new case's title, steps, and expected result are pre-filled, and the template's custom fields are surfaced (reset to empty) ready for you to complete.

Important behavior to know

• Non-destructive and non-linked. Applying a template only pre-fills the creation form. It creates no ongoing link — editing or deleting a template later has no effect on cases already created from it.
• No template versioning. Templates themselves are not version-tracked (only test cases are — see version history and rollback).
• Custom-field safety. If a custom field is used by one or more templates, QAM Hub warns you when you try to delete that field and requires a confirm step, so templates don't silently break.

Who can manage templates

Templates are managed by users with edit rights (project Admin, and org admins who are admins on the project). Read-only Viewers can see templates but cannot create, edit, or delete them. All template changes are recorded in the audit log. See roles and permissions for details.

Related

• Using custom fields
• Creating test suites and test cases
• Working with steps and expected results