LoadRunner non production and test environment scope

LoadRunner is a performance testing tool, which means almost everything it touches is a test or a non production environment by design. An audit that counts those environments as though each were a chargeable production deployment misreads the very purpose of the product, and the finding inflates by every environment the license never intended to meter. Scoping the estate correctly is the difference between a defensible Vuser count and a number built on environments that should never have been in scope.

LoadRunner, the load and performance testing product that came to OpenText through the Micro Focus acquisition, exists to simulate load against systems before they go live. Its controllers, load generators, and test assets are spread across staging, integration, and pre production environments because that is where load testing happens. When an audit treats the breadth of that footprint as evidence of a larger entitlement requirement, it counts the tool doing exactly what it was bought to do, and the non production scope question becomes the decisive line in the finding.

Why LoadRunner is mostly non production by nature

A performance test is not run against the live system that customers depend on; it is run against a copy, a staging tier, or an isolated environment built to absorb synthetic load without risk. That is the entire point of the product. As a result, the LoadRunner footprint is dominated by environments that exist only to be tested, and the licensing question is what the entitlement actually meters, not how many places the software happens to be installed. The metric that matters is the Vuser, the simulated user that generates load, and the way Vusers are licensed is examined in what is a Vuser and how is it licensed.

An audit that builds a finding from environment count rather than the licensed Vuser metric is changing the basis of the charge. The license meters the simulated load a test can generate, capped by the Vuser entitlement, and the number of non production environments where that capacity sits does not multiply the entitlement. Counting installations as if each were a separate chargeable deployment is the error, and it is the same kind of error that inflates a finding when environment counts are stacked across an estate, the subject of LoadRunner environment counts and license exposure.

Where the non production scope decides the finding

The decisive question is what the entitlement charges for. Where the license meters Vusers, the finding should rest on the peak simultaneous Vuser load the estate can or does generate, not on a tally of environments. A buyer who can show that the Vuser entitlement was never exceeded holds the finding to the licensed capacity regardless of how many non production environments host the controllers and load generators. That is why separating the test footprint from the chargeable metric is the first move, and why scoping precedes counting.

The same reasoning extends to how a load test is sized in the first place, because a single test that briefly spins up a high Vuser figure is not the same as a sustained entitlement requirement, a distinction explored in how to scope LoadRunner Vuser bursts. A non production environment built to absorb a one time burst should not anchor a finding as though that burst were a permanent production load, and scoping the environment correctly is what keeps the burst in its proper context.

How the controller and load generator footprint is read

LoadRunner separates the controller, which orchestrates a test, from the load generators, which produce the simulated traffic, and an audit can misread this architecture by counting each component as a chargeable item. The licensing of these components is set out in LoadRunner Enterprise controller and load generator licensing, and the principle there carries directly into the non production scope question: a load generator sitting idle in a staging environment is not generating chargeable load, and a controller that coordinates a capped Vuser test is not a separate entitlement. The footprint is large because testing is distributed, not because the entitlement requirement is large.

How we defend a non production scope finding under the four Rs

Respond. OpenText gives seven days notice before an audit and the right to copy relevant records, and the seven day notice clock starts immediately. Within that window we take over the single controlled channel and establish which environments are non production testing tiers and which, if any, carry a production load, so the scope is defined by us before the vendor reads the footprint.

Reconstruct. We build the effective license position against entitlements and the Additional License Authorizations independently, establishing the Vuser entitlement and the peak simultaneous load the estate generates, so the finding rests on the licensed metric rather than on a count of environments.

Rebut. We challenge every line that counts a non production or test environment as a chargeable deployment, presenting the testing architecture and the Vuser data that shows the entitlement was respected. The finding falls by every environment that was never meant to be metered.

Resolve. We settle on the count that reflects the licensed Vuser capacity and, where it serves you, convert forward into an OpenPass agreement that records how LoadRunner is measured and that non production testing environments are scoped out, so the next review cannot rebuild the finding from environment count.

An anonymised outcome

Scope matters because the remedy is severe. On noncompliance the licensee is deemed to have acquired licenses at then current list price, owes back maintenance and support, owes first year maintenance on the new licenses, and reimburses the cost OpenText incurs performing the audit, so counting non production environments as chargeable multiplies the error across every charge at once. Our anonymised case files show what correcting the basis of a count achieves: a banking ArcSight finding driven by events per second and connector counts was reduced from $6.0M to $1.8M, a 70 percent reduction built on separating what genuinely loaded the system from what did not. A LoadRunner finding answers to the same correction, because a test environment is not a production deployment.

Scope the estate before you accept the count

The durable point is that LoadRunner is defended by scoping the estate first, because the product is a testing tool whose footprint is non production by design and the licensed metric is the Vuser, not the environment count. A buyer who separates test tiers from production load and produces the Vuser data holds the finding to the licensed capacity. To build the position, read what is a Vuser and how is it licensed, LoadRunner environment counts and license exposure, how to scope LoadRunner Vuser bursts, and LoadRunner Enterprise controller and load generator licensing. For the full method see our ALM and LoadRunner audit defense track and our complete OpenText audit defense playbook for 2026. If a LoadRunner finding has counted your test environments, open a case.