Report Templates: Stop Rebuilding the Same Report After Every Load Test
This is the sixth and final post in our "Features Sitting Idle" series, where we shine a light on OctoPerf features that are already in your account, ready to save you hours every week.
"Are You Rebuilding the Same Report Structure After Every Test?"¶
It's a quiet but recurring friction.
Teams that test regularly all end up with a preferred report layout. But in practice, that structure is often rebuilt manually after each run, or lost entirely when moving between projects.
The Situations We See Often¶
A few patterns come up across customer projects:
- Layouts that don't travel. Teams that have spent time building a well-structured report for one project, only to find there's no straightforward way to apply the same layout to new projects or workspaces.
- Reports that all look the same. Reports where the description and timestamp look identical across runs, making it impossible to tell them apart at a glance. A clear sign that no consistent naming or templating convention is in place.
- External reformatting. Engineers who export results to external tools to reformat them, not realizing that the report structure they need can be defined once and reused automatically.
The common thread: a lot of manual work to deliver something that should be a one-click action.
What Report Templates Do¶
Report Templates address these needs directly.
You configure a report once - the charts, the metrics, the layout, the text blocks - and you save it as a template. With one click, you apply it to any existing report in your workspace.
Two details that matter once you start using them:
- Dynamic variables. Templates support dynamic variables in text blocks and report descriptions. Test name, date, result number are injected automatically each time the template is applied. No more reports with identical descriptions.
- Workspace-wide sharing. Templates are shared across all projects within a workspace. The structure you built for project A is available the moment project B starts.
How to Build a Template That Actually Works¶
A few practical tips, based on the templates we see succeed in the field:
- Start from your "perfect" report. The one you built by hand for the project you cared about the most. That layout is your template baseline.
- Lead with Analysis Insights. Place the Insights report item at the top so every templated report starts with the alerts before the charts.
- Use dynamic variables in the description. Build version, date, and result number injected automatically means you can tell any two runs apart at a glance.
- Keep it lean. A template that contains 40 charts is a template no one will use. Pick the 10 to 15 items that answer 90% of the questions, and keep the rest as on-demand additions.
The Compound Effect with Other Features¶
Report Templates pay off the most when they're paired with other "Features Sitting Idle":
- Paired with Analysis Insights, every report starts with a clear alert section instead of an empty wall of charts.
- Paired with Trend Reports, every test result feeding the trend has the same structure, so comparisons are immediate.
- Paired with proper CI/CD integration, every Jenkins-triggered run lands in your account with the right layout already applied.
That's the real point of templates: they're not a productivity gain on their own, they're the connective tissue between the other reporting features.
Why It Matters¶
A standardized report is not a cosmetic concern. It's the difference between:
- A new team member who can open any report and immediately know how to read it.
- A stakeholder who gets the same one-page summary at every release.
- A trend report that compares apples to apples, because every result has the same items.
And from a pure time perspective: zero reformatting after each test is not a small win when you run dozens of campaigns a quarter.
Final Reflection¶
Most teams underestimate how much time they spend reformatting reports after each run. The minutes add up: five minutes here, fifteen minutes there, multiplied by every test, every week, every project.
Report Templates are the feature that gives those minutes back. The structure you've already perfected, applied in one click, every time.
That's a fitting close to this "Features Sitting Idle" series: the features are already there. The next move is yours.
Full documentation: api.octoperf.com/doc/analysis/edit-bench-report/templates/