Welcome to OctoPerf's blog, where we embark on a journey through the dynamic landscape of load testing, a crucial aspect of ensuring your applications thrive in the face of user demands.
Whether you're a seasoned performance engineer or just diving into the world of load testing, our blog is your go-to resource for insights, best practices, and cutting-edge tools.
JMeter Load-testing
Load-testing using the n°1 open-source solution: Apache JMeter™.
Real-Browser Load-testing
Load-testing using real-browser solutions like Playwright and Selenimum Web-Driver.
Load-testing Methodology
Load-testing methodology and tools comparison.
OctoPerf's releases
Stay tuned on the JMeter™ Performance Center latest releases: OctoPerf!
Whether you're a developer aiming to optimize your code, a QA engineer ensuring application resilience, or a business owner safeguarding user satisfaction, load testing is your ally. Join us on this expedition into the heart of performance excellence.
Are you ready to transform your understanding of load testing? Let the journey begin!
A VuGen script is C. Some scripts are a recorded journey with helpers around it, others are a framework that happens to send a few requests. OctoPerf 17 ships a LoadRunner migration playbook for AI agents whose first job is to tell you which one you have.
Real prompts, real output, script downloadable.
Migrating a load testing project is rarely hard. It is long, and easy to abandon halfway. OctoPerf 17 ships a NeoLoad migration playbook for AI agents.
Real prompts, real output, project downloadable.
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.