OpenText LoadRunner Professional Reviews

We use this tool to test loading charges, test the load and to restrict formats.

Before going into production, we use it to validate some transactions, new environments and cloud environments.

The reporting feature in this tool needs to be improved. After using it, in my opinion it seems a little complicated in some aspects. They can make that better.

It is stable. It is not always user friendly but it is efficient.

The scalability is fine with us.

It was a long time ago that we installed it.

You must test them on different protocols and on different transactions to see if it is good or not.

Personally, I don't understand HPE’s global strategy, i.e., how to sell the services and so on. It's so different from other companies. Every company includes services and stocks materials. However, in regards to HPE’s strategy it seems to me, that they increase parts and materials and instead stock on services. This is my view of HPE and I need to increase my understanding of their strategy.

The reporting tool isn’t so good. Sometimes, we must hesitate between the different types of protocols to obtain the results. That can seem a bit difficult.

The feature I find most valuable is the ability to find performance issues before putting a new application live.

LoadRunner is the standard choice for performance testing before any critical applications are allowed to go live, preventing any performance issues.

LoadRunner is a well-rounded, polished tool – but it does need more improvement when it comes to it application of load, more flexibility mid-test would be nice.

Since 1999

No

No

No

Customer Service: The Customer Service is good, the sales guys are not overly aggressive to sell, as the product does sell itself.Technical Support: The Technical Support is OK. It’s not as good as the Pre-HP acquisition days at Mercury.

LoadRunner runs an automated install which is quite simple.

LoadRunner was installed in house.

Research your strategic requirements. Think long term, it WILL work out cheaper. LoadRunner is not a tactical solution.

Our primary use case for this solution is across many environments and many applications.

It provides clients with an understanding of application and system performance.

Real-time performance stats, analysis tool, protocol coverage, and simple integration of external monitors are the most valuable features. 

Support for Microsoft Dynamics needs improvement.

More than five years.

The most valuable features are the ease of using it to create scripts and the broad number of technologies supported, including apps, SAP, and everything on the web.

It enables us to really reproduce what users are doing in the application, not only as a single button or web service, but in the whole application. This helps us anticipate performance issues in production.

• Licenses are too expensive in general.
• They should remove the location or worldwide licensing fee. It is a special fee that you need to pay when you want to use a LoadRunner controller installed in the UK when you're working from Spain.

It's quite stable.

It is scalable. The biggest we've done is 20,000, but I know it can be done bigger.

I have not used technical support in the past two years. Previously, it was too thick and too heavy to deal with them. They asked a lot of questions without providing solutions.

The initial setup was really straightforward. You just install, make a couple of tests, and everything is connected.

We also considered Neotys and SOASTA.

My advice would be to use it.

Powerful scripting tool to best record user actions programmatically. Flexible and versatile scripting engine to extend tests with success-failure checks, thus making testing more intelligent. Ramping of many concurrent users to make the most representative testing possible. Integration of external measurements in test scenario's. Extensive vendor documentation and help system included. Extensive experience and support on various fora, blogs and many other support resources. Good availability of expertise in the form of programmers and hardcore testers.

Complexity. LoadRunner is not simple to learn by installing it and "doing it". Especially when using different data sources to do cross measurements of system performance. Performance testing with a tool like this requires planning and skilled resources. Fortunately these are easily acquired these days. 

Price. I've used LoadRunner for performance testing purposes for a number of years on various projects and I've always been impressed by the versatility and plain power of this testing tool. LoadRunner's scripting engine is very flexible and the fact that it's able to quickly and easily simulate hundreds of concurrent users makes it the performance testing tool of choice for years running. LR is constantly updated and improved to cope with a changing world.

10 years

HP offers extensive documentation and support services to help its customer base. True, the product costs a few bucks more than the (open source) alternatives like Neoload, QA Load and others, but in my opinion you get a solid performance test in return (if properly executed of course).

I consider all features valuable (Load Generator, VuGen, Agent Process, Analysis), but Controller is the most valuable for me.

It's helped my organization to identify performance problems in the test environment before they occur in production.

It's a very mature tool. Still, if they provided integration with a monitoring tool it would be great.

I've been using it for six years.

No issues encountered.

No issues encountered.

No issues encountered.

Customer Service:

4/5

Technical Support:

4/5

I previously used MS VSTS and JMETER. I would recommend LoadRunner as it is user friendly and has support for many protocols.

It was straightforward.

Implementation was easy.

Pricing is the only thing which make people think many times before purchasing this product.

No other options were evaluated.

Analysis tool

LoadRunner helped identify bottlenecks during the testing phase in several instances especially before launch of major projects.

5 years

The load generators make use of all available NIC to send traffic. Some NICs on a machine were not configured for external access, hence causing http requests to fail.

Occasionally it crashed when it had to crunch large amounts of data.

Customer Service: Very poorTechnical Support: Strictly ok