LoadRunner review

LoadRunner is a performance-testing product family for generating virtual-user load against applications and services. It sits in a test workflow: teams use it to model demand, exercise systems under load and assess performance before or during releases. It is not presented as an application API, SDK or general-purpose load-generation library.

The published editions are Community, Professional, Enterprise and Cloud. Community supports 50 virtual users for proof-of-concept and non-production testing. Professional licensing is based on concurrent VUser capacity by protocol bundle, with Virtual User Flex Days also available. Enterprise uses shared VUser pools, instances and protocol suites. Cloud offers fixed VUs or Virtual User Hours (VUH), with published scale up to 5,000,000+ virtual users.

The product family spans different licensing models, but the vendor does not establish deployment-platform details on its homepage. Confirm where each edition runs, how load generators are deployed and what controller components your architecture needs before choosing an edition.

LoadRunner is a testing product rather than a developer-facing hosted API. The vendor homepage text identifies OpenText Support and regional sites, but it does not name a REST API, webhooks, CLI, plugins, SDKs or programming languages. The product facts identify protocol support and licensing bundles, not the mechanics for authoring, launching or automating tests.

That leaves an integration question for teams planning CI/CD use: confirm the supported automation interfaces, scripting languages, version-control workflow and report export options in the current LoadRunner product documentation. Ask the vendor which interfaces work across Community, Professional, Enterprise and Cloud; do not assume an integration feature in one edition is available in another.

Community supports listed protocols, excluding COM/DCOM, Templates and GUI bundles. Professional protocol capacity and additional bundles vary by protocol. Those distinctions affect what tests you can run, so validate protocol coverage against the application stack before committing to a license.

The pricing page does not publish monthly or annual prices, and no starting price is listed. LoadRunner Community is the clear low-cost entry point: it includes a perpetual free license and 50 virtual users for proof-of-concept and non-production testing. Its listed protocol support excludes COM/DCOM, Templates and GUI bundles.

Professional licensing is based on concurrent VUser capacity by protocol bundle. Virtual User Flex Days (VUFD) and additional Web, Web 2.0, SAP and Database protocol bundles are available, but their costs and exact Flex Day limits are not published. A free trial is listed; its duration and limits are not published.

Enterprise uses shared VUser pools, instances and protocol suites. Additional load generators and multi-project controller capacity are available, with costs not published. Cloud can be licensed by fixed VUs or VUH and is described as pay-per-use based on consumed VUH, scaling up to 5,000,000+ virtual users. Additional VUH and cloud load injector regions are listed, but their costs and the VUH overage rate are not published. Request a quote that covers peak load, protocol needs and schedule changes.

The vendor homepage does not state an open-source licence or make source-availability terms clear. It also does not establish which editions can be self-hosted or where their components run. Ask OpenText for the licence terms, supported deployment models and any data residency options before placing tests or results in a production workflow.

LoadRunner Cloud's VU and VUH licensing indicates a cloud offering, but it does not settle how test scripts, results or configurations can be exported. The published materials do not describe data export or migration tools. Confirm script portability, report formats and access to historical test data in writing.

Lock-in will depend on the protocols, scripting model and reporting your team adopts. Before expanding usage, validate whether scripts can be reused outside LoadRunner and what would need rewriting if you later change test runners.

LoadRunner's published scale ranges from 50 Community virtual users to 5,000,000+ virtual users in Cloud. That makes the editions relevant to different testing sizes, but capacity is not the same as a production plan: verify protocol coverage, load-generator placement, controller capacity, concurrency rules and Cloud VUH overages with the vendor. The vendor does not publish prices, so model costs against realistic test schedules before relying on pay-per-use capacity.

Security and compliance requirements also need a vendor review. Confirm data handling, region availability, retention, access controls and the deployment model for your chosen edition; the homepage does not establish those details.

Reddit feedback is mixed. One r/QualityAssurance commenter said LoadRunner made sense where a company already used it, while another reported license-date problems, slow support responses and frustration with fixed license periods. Those are individual reports, not service guarantees, but they make support hours, renewal terms and license flexibility worth checking before a large rollout.