A campaign is a named group of tests organised around a concrete performance purpose. Where a single test run tells you how a feature performs at a given moment, a campaign tells you whether your system is consistently meeting a defined standard over time. After each test run completes, Gatling Enterprise computes a campaign score and adds it to the score trend, giving you an evolving picture of your system’s performance health across days and weeks.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/gatling/gatling.io-doc/llms.txt
Use this file to discover all available pages before exploring further.
Campaigns are only available on Gatling Enterprise paid plans. To learn more, explore our plans.
What is a campaign score?
The campaign score (0–100) is the average of three category scores: Methodology, Objectives, and Confidence. Each category aggregates scores from every test linked to the campaign.Methodology
Measures how well each test is configured to produce meaningful, stable results. Checks for a meaningful test name, a defined load test type, and at least one configured objective or assertion.
Objectives
Measures whether each test is meeting its defined goals. Checks that the last run completed successfully and that all configured SLOs or assertions passed.
Confidence
Measures result stability over time. Computed as a weighted average of Objective scores from the last 3 runs (current run: 50%, two previous runs: 25% each).
Accessing campaigns
Click Campaigns in the main navigation menu to open the campaigns list. Each row shows the campaign name, its owning team, and its latest score. Click a campaign name or See details to open the detail page, which shows the score trend over time and a per-test score breakdown.Creating a campaign
Provide campaign details
Fill in the required fields:
| Field | Description |
|---|---|
| Title | A name that reflects the performance purpose the campaign is tracking. Choose something meaningful—it appears in the score trend over time. |
| Team | The team that owns the campaign. This assignment cannot be changed after creation and determines which tests can be linked. |
| Description | (Optional) Additional context about what this campaign is tracking and why. |
Linking tests to a campaign
Tests are linked from the campaign detail page. Only tests belonging to the same team as the campaign are eligible.Open test management
On the campaign detail page, click Manage tests. A modal opens listing all tests belonging to the campaign’s team.
Select tests
Check the tests you want to include. Tests already linked to another campaign are shown as disabled and cannot be selected.
A test can belong to at most one campaign. Adding a test starts tracking it from its next run; removing a test stops tracking it but does not delete previously recorded scores.
Understanding score categories
Methodology
Methodology measures whether each test is configured to produce results worth analysing.| Metric | What it checks | Weight |
|---|---|---|
| Test name | A custom name has been manually assigned | 20% |
| Load test type | A load test type is explicitly defined in the test parameters | 20% |
| Objective set | At least one objective (SLO or assertion) is configured | 60% |
Objectives
Objectives measures whether the last run met its goals.| Metric | What it checks | Weight |
|---|---|---|
| Execution valid | The last run completed successfully (not failed or aborted) | 20% |
| Objectives pass | The last run met all configured SLOs or assertions | 80% |
Confidence
Confidence measures consistency across the most recent runs.| Metric | What it checks | Weight |
|---|---|---|
| Last 3 runs stability | Weighted average of Objective scores: current run (50%), previous run (25%), run before that (25%) | 100% |
When a campaign is first created, tests that have not yet completed a run will score 0 on execution-based metrics. This is expected. Scores stabilise naturally once all linked tests have accumulated at least a few runs.
Acting on low scores
Every metric is actionable. Low scores always point to something concrete you can fix:- Low Methodology
- Low Objectives
- Low Confidence
- Assign a meaningful name to the test
- Define the load test type in the test’s parameters
- Configure at least one SLO or assertion
Score trends
The trend chart in the campaign detail page shows one data point per day, captured at midnight UTC. As your tests accumulate runs, you build a complete historical record of your system’s performance health that you can review at any cadence.Editing and deleting campaigns
- Edit: open the campaign detail page and click Edit to update the title or description. The team assignment cannot be changed.
- Delete: click Delete on the campaign detail page. Deleting a campaign permanently removes it and all its recorded scores. The linked tests themselves are not affected.