--- title: OctoPerf v15.1 - Continuous integration and new trend report url: https://blog.octoperf.com/octoperf-v151---continuous-integration-and-new-trend-report/ date: '2025-10-12' authors: - gbetaillouloux categories: - Innovation tags: - Data - PDF - Reporting - CI/CD - Trending - Debug description: OctoPerf v15.1 brings new continuous integration features in order to make your tests even faster. The new trend reporting provides the best trend analysis in the load testing market. Find out about all this and more in this article. --- # OctoPerf v15.1 - Continuous integration and new trend report ## Summary OctoPerf v15.1 brings major improvements for CI/CD workflows and faster test automation. * A new integration wizard makes **Jenkins, Maven, and API-based automation easier** to set up with secure, prefilled configurations. * **PDF reports** can now be generated and emailed automatically at test completion, reducing manual steps. * The new **Trend Report** lets teams compare up to 25 tests, making long-term performance tracking far clearer. * Built-in **data generation** helps produce realistic datasets without external tools. * Multiple UX enhancements—preview tabs, clearer clickable elements, validation map, and visible time-ranges—smooth the overall user experience. ## Table of Contents - [Introduction](#introduction) - [Continuous integration improvements](#continuous-integration-improvements) - [Trend report](#trend-report) - [Data generation](#data-generation) - [UX changes](#ux-changes) - [Full changelog](#full-changelog) ## Introduction Version 15 of OctoPerf bring **a huge focus on continuous integration and Devops practices**. We've taken steps to highlight existing integrations, add many others and we've thrown **an entirely new report type on top of it.** ## Continuous integration improvements **It's always been possible to automate OctoPerf tests** using [our existing plugins](https://api.octoperf.com/doc/runtime/edit-scenario/integrations-automation/ci-cd/ci/jenkins/ "Load testing CI plugins") or simply [through our API](https://api.octoperf.com/doc/runtime/edit-scenario/integrations-automation/ci-cd/rest/ "Load testing REST API"). That said the setup of those integrations comes with a learning curve. In order to make this curve as flat as possible we've added a new wizard and the possibility to get a PDF report automatically at the end of the test. ### Easier integrations On the runtime screen, the integrations panel at the bottom lists the main integrations you can use in order to execute your load tests outside of OctoPerf: ![integrations](https://blog.octoperf.com/img/blog/octoperf-15-1/integrations.png "OctoPerf CI Integration") When you select one of them **a very detailed wizard will popup and guide you through the entire setup**. It covers everything from the installation of the third party tool to the setup of an automated OctoPerf test: ![integration wizard](https://blog.octoperf.com/img/blog/octoperf-15-1/integration-wizard.png "OctoPerf CI Integration Wizard") **Those examples come with every workspace/project detail prefilled** and also follow the best security guidelines regarding how to provide your API Key. In the example above, the actual API key is not in the XML file but will be provided in the command line along with **guidelines on how to secure your API key or projets:** ![maven](https://blog.octoperf.com/img/blog/octoperf-15-1/maven.png "OctoPerf CI Maven Integration") With this, we are confident that **you will be able to execute your OctoPerf tests in the safest way possible** while not having to spend large amounts of time learning an entirely new system. Another example is for our HTTP API, here we will provide a command line that you can execute in order to run the test: ![api](https://blog.octoperf.com/img/blog/octoperf-15-1/api.png "OctoPerf CI HTTP Integration") You can even choose the command/language you want to generate, that way **you can get a working example in your context with a few clicks through our wizard**. And of course we'll improve those based on real uses cases and feedbacks, **so make sure to get in touch with us if you encounter any challenge.** ### PDF report It was already possible to generate the PDF report [at the end of a test launched with our plugins](https://github.com/OctoPerf/octoperf-maven-plugin?tab=readme-ov-file#additional-parameters-3 "OctoPerf Maven Plugin Parameters") or even with a [test executed from the API](https://api.octoperf.com/doc/runtime/edit-scenario/integrations-automation/ci-cd/rest/#downloading-a-report "OctoPerf API Download Report"). In order to make this even easier we've added it to the notifications system as well. With that you are now able to **ask OctoPerf to generate a PDF report and send it via email when the test is finished**: ![notification](https://blog.octoperf.com/img/blog/octoperf-15-1/notification.png "Load Testing PDF Report by Email") Combine this with our **notification filters** and you can get the PDF only for relevant tests, that way you avoid [notification overload](https://en.wikipedia.org/wiki/Information_overload "Information Overload"). ## Trend report **OctoPerf's strong suit is already our reporting but that doesn't mean we can't improve it further**. With this brand-new report type it is possible to compare up to 25 tests in a single report. Comparison reports already give a lot of details but are limited to 4 tests, this new trend report takes a median approach with fewer details per test, but a larger number of tests. Our hope is that it will make more sense in the case of very regular tests for instance within a Devops or CI pipeline that includes load testing: ![bar-trend](https://blog.octoperf.com/img/blog/octoperf-15-1/trend-bar-chart.png "Load Trend Bar Chart") And of course every metric is compared to a Reference result of your choice: ![summary-trend](https://blog.octoperf.com/img/blog/octoperf-15-1/trend-summary.png "Load Trend Summary") And there's even new report items you can use to highlight differences: ![trend-stacked-bar](https://blog.octoperf.com/img/blog/octoperf-15-1/trend-stacked-bar.png "Load Trend Stacked Bar Chart") You can select the Reference when you create the Trend report and then chose to have a static trend or one that auto-updates with every new test: ![trend-config](https://blog.octoperf.com/img/blog/octoperf-15-1/trend-config.png "Load Test Trend Configuration") ## Data generation When you want to run a test quickly with production-like data you often need to spend a lot of time creating meaningful datasets. To simplify this process, you can now directly [generate your fake datasets](https://api.octoperf.com/doc/design/edit-virtual-user/configuration/data-generation/ "Data Generation") inside OctoPerf. This feature is available on [any CSV variable](https://api.octoperf.com/doc/design/edit-virtual-user/configuration/variables/csv/ "JMeter CSV Variable"): ![data-columns](https://blog.octoperf.com/img/blog/octoperf-15-1/data-columns.png "Faker Data Columns") First select your locale and the type of fake data you want. ![file](https://blog.octoperf.com/img/blog/octoperf-15-1/file.png "CSV file generation") Then you get an overview of the file that will be generated. Once finished, you can find it in the [files menu](https://api.octoperf.com/doc/design/edit-virtual-user/configuration/files/#files-list "Load Testing Files") and download/edit it to your needs. ## UX changes In this section are some of the minor changes we've introduced based on **your feedbacks, so keep them coming!** ### Validation map The [validation panel inside the design page](https://api.octoperf.com/doc/design/edit-virtual-user/validation/ "OctoPerf Validation") now comes with an interactive map, exactly like the [location selector from the runtime screen](https://api.octoperf.com/doc/runtime/edit-scenario/edit-user-profile/location/ "Load Testing from Multiple GeoLocations"): ![map](https://blog.octoperf.com/img/blog/octoperf-15-1/map.png "Load Testing Map") With this change, new users will be able to better understand the purpose of the virtual user validation, which we hope will reduce errors down the line. ### Time range visible in report summary You can apply a time range filter to your test results, in order to see only a subset of the total duration of the test. The issue with this is that it's not obvious when such a filter is in place so things can get confusing quick. To improve this, we've decided to display the time range on the test summary displayed on top of every report: ![summary](https://blog.octoperf.com/img/blog/octoperf-15-1/summary.png "OctoPerf Summary Time Range") Now this graph shows 2 important details: - The real end of the test versus the theoretical duration (in discontinued lines), - The time range being displayed in all other graphs (with highlighted background colors). ### Preview tab When navigating through lists of items, a single click would select and a double click would open for edition. Our goal was to prevent too many tabs to open automatically when you click during your navigation because it could get confusing and/or slow. But a lot of the feedbacks were asking us to enable a single click to open any item. We found that the best of the two worlds could be achieved by having a preview tab that opens on a single click, and updates when you click on another item. It's easy to recognize because it is always the first tab on display and it's named is italicized. And if you want an item to remain, you can still double click to open it in another tab that stays available: ![preview-tab](https://blog.octoperf.com/img/blog/octoperf-15-1/preview-tab.gif "OctoPerf Visual Studio Preview Tab") We've implemented this behavior for all lists of items inside OctoPerf. ### Clickable elements more visible Another issue we faced is that although a lot of the texts inside OctoPerf are interactable with a single click, it's not always clear until you've tried. To that end, we've underlined all interactable texts in order to suggest that those are hyperlinks (technically they're not) and as such can be clicked on. In the screenshot below you can see that the user profiles are clickable but also the text under the button to **Add first runtime property**: ![highlights](https://blog.octoperf.com/img/blog/octoperf-15-1/highlights.png "UX Clickable Links") ## Full changelog For the complete list of fixed bugs, please refer to [OctoPerf 15.1 Release Notes](https://api.octoperf.com/doc/release-notes/#1510-16th-september-2024 "OctoPerf 15.1 Release Notes").