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.
Sharing dynamic values across Virtual Users is often required in realistic load-testing scenarios. AMQP provides a simple and reliable way to exchange data between scripts by pushing values into a queue and retrieving them later. The tutorial demonstrates how one Virtual User can publish generated IDs to RabbitMQ, while another consumes them on demand.
CloudAMQP is used as the example broker, but the method works with any AMQP-compatible system. OctoPerf integrates easily with these HTTP endpoints, allowing both insertion and retrieval of queued values. Combined with JSON extractors, this approach makes cross-VU coordination straightforward and scalable.
This guide shows** how to connect Spira and OctoPerf to streamline load-testing workflows**. The integration lets teams launch OctoPerf scenarios directly from Spira test cases and automatically receive results back in Spira. Setup involves enabling the OctoPerf app, configuring server credentials, and adding custom properties to Spira test cases.
Running a test from Spira triggers an OctoPerf execution using the referenced scenario ID. A webhook combined with OctoPerf notifications pushes the final test results into Spira for centralized reporting. The process improves collaboration by keeping performance test execution and results within the same toolset used for QA management.
Load-testing applications using OpenID Connect requires simulating real authentication flows and validating token handling under stress. The guide walks through the OIDC “code” flow, explaining tokens, JWT internals, and the roles of the application, user, and identity provider. A full JMeter scripting workflow is detailed—from recording traffic to extracting dynamic values like state, nonce, session codes and authorization codes.
The process includes generating tokens, decoding them, managing headers, and preparing for token refresh logic. Keycloak is used as a reference example, but the same approach applies to any OIDC-based system. Guidance is provided on load modeling, login frequency, token expiration, and designing realistic test policies.