A Test Campaign is a structured way to group multiple test cases into a single, trackable campaign inside a project. It helps teams plan execution, keep the same run order, and follow progress from start to finish without losing context.
Why it matters
- Clarity: everyone runs the same set of test cases in the same sequence, which reduces gaps and duplicated work.
- Execution tracking: you can see campaign-level progress and keep testing aligned with dates, environment, and ownership.
- Team coordination: campaign comments and to-dos keep discussion and next steps attached to the work itself.
When to use it
- Regression cycles where you want a reliable, repeatable run list for each build or release.
- Release validation when you need to confirm a defined scope before shipping.
- Multi-tester coordination when several people execute different parts of the same campaign.
Core concepts
- Campaign – a project-level container that holds your test run scope
- Campaign Cases – the test cases linked to the campaign
- Order – the execution sequence (1, 2, 3…) used to keep runs consistent
- Status – a campaign state used to reflect where the campaign stands (e.g., Draft, In Progress, Completed)
- Environment – the target environment or setup where the campaign is executed
- Owner – the person responsible for coordinating the campaign
- Comments – context and notes related to the campaign
- To-Dos – action items that come out of the campaign (follow-ups, retests, confirmations)
How it works
- Create a Test Campaign inside a project and set the main details (title, dates, status, environment, owner).
- Attach test cases to the campaign and define their Order so execution stays predictable.
- Execute the campaign to run the linked test cases in sequence and collect results.
- Track progress and coordinate using campaign updates, comments, and to-dos until the campaign is complete.
How to use it
Step 1: Create the campaign
Start by creating a Test Campaign under the active project. Give it a clear name (usually including build/version and scope), then set the dates and optional metadata like status, environment, and owner.
Step 2: Add test cases and set order
Attach the test cases you want to run as part of this campaign. Assign an Order number for each one to define the run sequence.
Step 3: Run and follow up
Run the campaign to execute its test cases in order. Use Comments for context and To-Dos for action items such as retesting fixes or validating specific areas.
Best practices
- Use a naming convention: include build/version + scope (example: “Regression - Build 142 - Payments”).
- Order with intent: run smoke checks first, then deeper coverage, then edge cases.
- Keep campaigns focused: avoid mixing unrelated scopes in a single campaign.
- Write useful preconditions: short, practical setup steps that anyone can follow.
- Use to-dos for follow-ups: keep comments clean by moving action items into to-dos.
Common mistakes
❌ Creating a campaign without a clear scope
✔ Define exactly what the campaign covers (feature/module/build) in the title and description.
❌ Using random order numbers
✔ Keep order sequential and stable so different testers get consistent results.
❌ Turning comments into a task list
✔ Use comments for context, and to-dos for actions and follow-ups.
Security & permissions
- Project-based access: Test Campaigns follow the same access boundaries as the project they belong to.
- Role-based actions: creating, editing, and running campaigns depends on your role in the project.
- Controlled changes: shared fields like status and environment are managed to keep values consistent.
Related documentation
- Test Case
- Executing Test Cases
- Campaign Comments
- Campaign To-Dos