
7 steps to run a successful test campaign
A structured guide to define, scope, run, and govern a software test campaign.
A well-prepared test campaign prevents problems from being discovered at the last minute. It clarifies what needs to be tested, how to test it, who is responsible, and which criteria support the final decision.
Goal
Product quality
Structure
7 steps
Output
Clear decision
Step 1
Definition
A test campaign is a structured approach to evaluate the quality, functionality, and performance of a software product.
- Identify defects.
- Validate new features.
- Ensure existing features remain intact after updates or changes.
Step 2
Types of test campaigns
The type of campaign depends on the need, the risk level, the available resources, and the time constraints.
Validation campaign
Checks that a new feature or product behaves as expected, using deeper test cases to explore the feature thoroughly.
Regression campaign
Checks that recent changes have not introduced bugs or changed existing behavior. It is best automated and run regularly.
Acceptance campaign
Ensures that a code delivery has not caused critical issues. It covers core features and remains fast, often between 5 and 30 minutes.
Step 3
Scope
Scope clarifies what should be tested, how deeply it should be tested, and in which priority order.
- Identify all systems required to perform the test campaign.
- Identify the use cases and scenarios impacted by the campaign.
- Prioritize scenarios based on risk or severity.
Step 4
Test strategy
The strategy gives the campaign its operating frame and avoids ambiguity during execution.
- Actor: who will perform the tests.
- When: when the tests will run.
- Environment: which environment to use.
- Tools: which tools are required.
- Defect management: how defects are reported and handled.
Step 5
Roadmap
The roadmap makes milestones, expected duration, and campaign risks visible.
- Identify the main milestones.
- Estimate the expected campaign duration.
- Track risks and mitigation plans explicitly.
Step 6
Criteria
Criteria make it possible to approve or reject the test campaign result without implicit arbitration.
- Define success and failure criteria.
- Example: fewer than x critical defects.
- Example: x% of critical use cases without defects.
Step 7
Governance
Governance helps track progress, share decisions, and maintain alignment.
- Create reports and dashboards to track progress.
- Define the frequency of follow-up meetings.
- Clarify the expected participants.
Explore also

A structuring tool to design or evolve an agile community around identity, experience, and structure.