Our BlazeMeter to OctoPerf Maven plugin is archived. What replaces it is not another tool to install: OctoPerf 17 ships a BlazeMeter migration playbook for AI agents.
Real prompts, real output, run against a real BlazeMeter account.
OctoPerf 17.0.0 is available, on the SaaS platform and for On-Premise installations. It rebuilds how test results are stored and read, upgrades Playwright, and considerably extends what an AI agent can do through the OctoPerf MCP server.
One thing to know before you upgrade. A result recorded before this version must be updated before its report shows data again. Nothing is lost, and the update runs on its own the first time you open the report.
The OctoPerf web application is a large Angular workspace: 7,786
TypeScript files, around 381,000 lines of code, 1,166 components and 2,738 test files. We have
just taken it from Angular 20 to Angular 22, deleted zone.js, and replaced Karma and Jasmine with
Vitest.
The interesting part of this story is not the version number. It is that we got the strategy wrong first. We spent months migrating the codebase component by component, drowned in manual regression testing, and still let bugs reach production. What unblocked us was not a better migration technique. It was realising that our bottleneck was validation, not transformation, and building an automated safety net before touching the framework again.
So this post is the thought process rather than the changelog, with the numbers we measured rather than the ones we hoped for. It ends on a question we cannot dodge: this migration would not have happened in this timeframe without an LLM. So are we now dependent on one?
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.
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.
This is the fifth post in our "Features Sitting Idle" series, where we look at OctoPerf features that are already in your platform but often missed by the teams that would benefit the most.
This one is for IT teams running OctoPerf on-premise.
IT teams managing an on-premise OctoPerf instance regularly run into the same friction around SSO.
The pattern is so consistent that we've come to recognize it as a tell-tale sign that the team hasn't migrated to the new dynamic configuration introduced in version 15.