If they can afford it, then I would recommend it. It's a good product. The problem is the price. So, if they have the budget, then it's the best tool you can go for.

Overall, I would rate the solution an eight out of ten because if it weren't so expensive, I'd give it a nine and a half or even a ten. The price is really steep. 

It's an enterprise-level tool, but there are also smaller companies developing applications that need testing, and they might not have the budget for such expensive tools. So, if the price were more reasonable, it would be accessible to any size enterprise, big, medium, or small.

We are currently not using LoadRunner Developer, but we are planning to use it. We also do not use the TruClient feature. It has some disadvantages where it requires a lot of hardware capacity, and we are currently not at that level.

Overall, I would rate LoadRunner Enterprise an eight out of ten. We are pretty satisfied with LoadRunner Enterprise, but it would be great if they also added performance engineering capabilities. It meets our current requirements, but there is scope for improvement. In terms of future growth, we are looking for more contributions from the OpenText side.

LoadRunner is user-friendly and adaptable for enterprise-scale testing, with easy knowledge transfer to newcomers. However, its resource consumption and cost are considerable drawbacks.

I recommend it with one remark. Please hire a professional consultant if you don't have in-house resources for the first test. So, with the right consultancy, LoadRunner is a powerful OpenText tool. 

If you don't have the right consultancy, you'll be using it at 10 to 20% maximum, and then it's a waste of money.

Overall, I would rate the solution a ten out of ten. 

I would rate LoadRunner Enterprise a ten out of ten. It is a product that I have known as being a market-leading tool in that space for years. Being more of a software engineer and architect, testing tools are not something that I am intimately familiar with, but everything I am hearing from the guys that do that work is that it is the tool to use. It is great to have it in the OpenText family.

OpenText LoadRunner Enterprise helped us overcome debugging and scripting challenges. It has enabled us to manage projects. We have a place where we can put our results and scripts. It has streamlined our testing process. The tool has improved productivity and result quality. 

I use LoadRunner Developer. The tool reduces and makes our lives easier by recording the workflow and helping us identify the correlation. 

LoadRunner helps us save time. We can create the scripts for dynamic parameterization and automatic correlation in two hours. Earlier, it used to take five to six hours. 

I rate the solution a nine out of ten. 

I would recommend downloading the software for personal use to test it out. The solution solves my needs and provides everything required to carry out performance load testing so I rate the solution nine out of 10. 

I am not using the latest version of the solution.

While we use on-premises deployments right now, we are starting to look into the cloud. 

I'd advise potential new users to look at their budget. If it's a larger enterprise, LoadRunner will make sense due to the big environment. If budget is a concern for a company, it may be better to look at other options. 

I'd rate the solution five out of ten.

LoadRunner Developer’s shift-left process is becoming more and more important for us. It's a newer initiative for Costco. We are pushing towards it. We already have teams that have started doing lower-level performance testing. It'll continue to get adopted more and more as we push it out.

We are using the solution's TruClient feature. I work in administration. The people who work on scripting have some technical issues with TruClient's scripting. There are a number of scripts out there. LoadRunner Enterprise has helped streamline our testing processes. It is the only method of doing some of our testing processes. We find it very valuable.

Streamlining our testing processes has helped us through further improvements and validation that our systems are performing at the high level that we need them to perform.

LoadRunner Enterprise has reduced our workload. Without it, we wouldn't have performance testing, and things would break a lot more. LoadRunner Enterprise has helped improve our product quality. If it weren't there, things would break. The fact that we're still using LoadRunner is a pretty good sign.

LoadRunner Enterprise has helped us save time. Without it, things would break a lot more. Our primary experience with performance testing is with LoadRunner. I have played around with some other applications, and all of them have ups and downs. LoadRunner provides ease of use and a nice and concise interface.

Overall, I rate the solution a seven out of ten.

The solution has all the capabilities. The only area they need to work on is the low-code platform which has started emerging in the market lately. If they could do something in that area, it would be a great overall tool in the market. Right now, it takes a lot of time for me to train people and get them onboarded. However, while I use other tools like NeoLoad, I can easily train my team.

I rate the overall solution an eight out of ten.

Overall, we are pleased with the solution as it satisfies our requirements and meets our expectations. I would rate it eight out of ten.

One person is enough for the maintenance of the solution when we have three people using it.

I rate Micro Focus LoadRunner Enterprise a ten out of ten.

We are customers.

If a client has a budget, I would recommend the solution. It is a good tool. However, there are stability issues, and it does have a complex UI. It's good if you have specific protocols and specific requirements. When that is the case, there may be no other tool available. 

I'd rate the solution seven out of ten.

Overall, I would rate LoadRunner Enterprise a nine out of ten.

Overall, I rate the solution an eight out of ten.

We use the TruClient feature. We use TruClient for understanding webpage rendering. It's TruClient's strong suit. TruClient has been very important to us. Without it, we won't understand the JavaScript rendering the users see on the front end. TruClient is a great option if using standard HTTP is either unsuccessful or time-prohibited.

LoadRunner Enterprise has definitely helped streamline our testing processes. We're using it almost 24/7 to support a host of platforms across the enterprise. If we didn't have it in place, the organization would have hundreds of performance-related incidents every year. However, we don't have them because we're catching them.

Streamlining our testing processes allows us to meet business demands and keep up with very aggressive schedules. LoadRunner has a lot of capability straight out of the box. One of the best things about it is the automation that's built into it. It has a lot of automation and functionality that many other tools don't have.

LoadRunner Enterprise has helped me save time. LoadRunner Enterprise has helped improve our product quality by ensuring transparency between product, delivery, and test. With load testing, we can accurately inform the business of how the platform is doing. By doing so, we can ensure that expectations between product, business, and IT are aligned. If they're not, those issues can be addressed before we go to production.

Overall, I rate the product a nine out of ten.

A lot of people choose JMeter because it is free. However, JMeter is not as good as LoadRunner. Overall, I rate the solution a nine out of ten.

I'm an end-user.

I'd recommend the solution. For API testing, LoadRunner, getting the script developed in LoadRunner is very straightforward. It's not super difficult. You can get a REST API script in LoadRunner done within an hour if you have all the information and if you know the HTTP headers and stuff like that. You can get it up and running in an hour. 

I'd rate the solution a nine out of ten. I would give them a perfect score if the pricing was better.

In terms of the number of resources using Micro Focus LoadRunner Enterprise, I'm in a large organization, and in the beginning, there were ten resources. Nowadays, with the solution being tailor-made for my company, twenty-five to thirty resources belonging to different teams use Micro Focus LoadRunner Enterprise.

The solution is used every day as my company can't live without performance testing.

I'm rating Micro Focus LoadRunner Enterprise nine out of ten because it still has some room for improvement.

My company is a customer of Micro Focus LoadRunner Enterprise.

On a scale from one to ten, I would rate OpenText LoadRunner Enterprise at six.

I give the solution a seven out of ten.

I recommend that anyone that wants to use the solution first have their requirements written out.

I give the solution a ten out of ten. Micro Focus LoadRunner Enterprise is the best in the market, depending on what it is being used for. For API testing, we can find something cheaper. But the solution is good for that as well. For bigger applications that are Gooey-based, it's the best option.

Creating a script depends greatly on the type of application we have. If we have an API system, it will likely take less time to create a script since the developers have likely already set it up for us to use. However, if we have a lengthy application, it may take us days to create a single script.

We have between five and ten developers using the solution.

I recommend the solution, but it's expensive and only a big company could afford it. A small company wouldn't have the capacity to use the solution or the money to pay for it.

It's a tool that really helps you when you have a very varied landscape and you have technologies and platforms and infrastructure which include legacy and new ones, with a mix of SaaS. LoadRunner has the ability to support different protocols and that serves the purpose. It's a one-stop solution.

We wanted to integrate LoadRunner reports to a time-series database, an open-source tool like Grafana. We learned a lot from that integration. The integration of the solution into a CI pipeline is something that we haven't explored widely, but it's an area we are looking forward to investing in soon. We are exploring more in terms of the integration capabilities of LoadRunner with other tools.

Performance testing is a specialized skill and we don't have too many using the solution, but we do have a couple of professionals who have been doing performance testing for more than 15 years. The rest have been into performance testing for the last seven to eight years, with exposure to different protocols and technologies. We are aiming to scale up and cross-train them in multiple protocols so that we can reach some of our goals without any hindrance this year. We would like to have less dependency, in terms of expertise, on specific technologies and protocols.

Make sure you know what your use case is before you buy it.

On a scale from one to ten, I would give this solution a rating of nine. It's very good at doing what it needs to do. I think that the reporting needs a little bit of work, but that's pretty much it. I think every reporting system needs a little bit of work, so take that with a grain of salt.

I would rate LoadRunner Enterprise ten out of ten.

At this time, we do not make use of LoadRunner Developer Integration. We are thinking of migrating to the latest version of LoadRunner, which probably has the LoadRunner Developer functionality. Once we upgrade to the new version, we plan to use it.

We are not currently using any of the cloud functionality offered by OpenText. In our organization, we do have multiple applications that are hosted on the cloud, and we do test them using LoadRunner Enterprise, but we do not use any component of LoadRunner Enterprise that is hosted on the cloud.

I am an active member in several online communities, including LinkedIn, that are specific to performance testing. As such, I have seen different experts using different tools, and the overall impression that I get from LoadRunning Enterprise is that it offers good value for the price. The level of coverage in terms of scripting and analysis had helped to solidify their position as a market leader, at least a decade ago.

Nowadays, while others have closed the gap, it is still far ahead of other tools in the space. My advice is that if LoadRunner Enterprise can be made to fit within the budget, it is the best tool for performance testing and load testing.

I would rate this solution an eight out of ten.

It does everything you could hope for in a performance testing solution. It's not cheap, but that's not necessarily a concern for us because we're a large company. But it does anything you can think of. It's a pretty mature, robust tool.

When comparing Micro Focus LoadRunner Enterprise with the competitors that are coming into the market, I would look for an open-source version of this tool, if possible. The cost is one thing that is preventing people from using Micro Focus LoadRunner Enterprise. 

Some of the upcoming protocols are coming into the market, some of these are not supported by Micro Focus LoadRunner Enterprise. I can easily choose NeoLoad and complete what I need to with it. 

Micro Focus LoadRunner Enterprise is still evolving in the coming DevOps sector,  once the CICD architecture comes in, we will see more changes. I presume it is not up to date from a CICD support perspective.

I rate Micro Focus LoadRunner Enterprise a five out of ten.

It's an expensive tool, so you need to be prepared to invest in training your people and to have patience as they will need to use it a lot to become adept at it.

The main challenge we resolved using the product is ensuring the functional equivalency of applications that migrated from old to new environments. 

OpenText LoadRunner Enterprise has streamlined our testing process. It acted as a single source for the test cases and criteria. We could pull reports and show the management that the system is tested and can be taken live. 

The solution has helped us save time. 

Before OpenText LoadRunner Enterprise, a customer did not have a repository of test cases. Hence, they needed to redevelop the previously used test cases. However, the solution helps to reuse test cases. 

I rate the product an eight out of ten. 

As professionals, we're supposed to be some what tool agnostic. We'll find a way to get it done. That said, it's a mature player in the space. We do enjoy some long time knowledge about squeezing the good stuff out of it.

I rate OpenText LoadRunner Enterprise a ten out of ten. 

The advice I would give to someone considering this product is that they should try LoadRunner first before they start using Performance Center — especially if it is a small company. They need to know and be able to compare LoadRunner to Performance Center in the right way. After you have used LoadRunner then compare Performance Center. If they are part of a small company and they expect to expand they will know the difference. If they are already a very big company, they can save some money by using Performance Center directly. We are quite a big company, so Performance Center makes sense for us.

On a scale from one to ten where one is the worst and ten is the best, I would rate Performance Center as an eight. It is only this low because we have had so many problems here installing it and upgrading it. Sometimes it runs very slow just to set up tests, or it just crashes. Like when setting up a spike test, you start using the spike test process and it suddenly crashes after you have almost finished everything. Executing the tests were a lot easier and more stable in LoadRunner.

You can manage to make Performance Center work, but you have to be patient.

It's generally for enterprise level, however they now offer a SaaS version for smaller companies or clients.

I would definitely recommend LoadRunner for performance testing of any application/system with a wide variety of protocols. It's a great tool for capturing performance bottlenecks and its commendable analysis and reporting.

I would rate it nine out of ten

It is definitely one of the best products available on the market. Definitely programming knowledge around C programming would be greatly advantageous.

The most important criteria when selecting a vendor are, I suppose, support, and the reliability in the industry.

They have a good road map for moving forward. It's going to be integrating with a lot more other products that the DevOps world is starting to push upon us.

It's not quite perfect. It's still the best in the market. It holds up to a lot of the scrutiny that the developers constantly throw at us.

There have been a few issues, especially around the scripting and the IDEs, handling of some of the protocols, that still don't perfectly match with what we have in production. But overall, we're able to pretty well defend it. You can almost always reliably pull up the application, and the response times seem to match what we have coming out of LoadRunner.

I would definitely advise looking at Performance Center, it's still the best in the breed. Just make sure that you have a good team in place that can implement it.

The most important criteria when selecting a vendor to work with are the product, how easy it is to use the product and, again, how scalable the product is and how it suits the needs of United Airlines. And, of course, the customer support, and how technical support deals.

Regarding advice to a colleague, it depends on the industry and what kind of problem they are trying to solve. If it is in the airline industry, I would definitely suggest to them, "Okay, this is a perfect product because of the number of protocols it supports," because we looked at other open source software and we couldn't find a product which matches Performance Center, which supports so many protocols. So, especially in the airline industry, we are using multiple protocols and we need that support. I would definitely recommend that.

When selecting a vendor I would judge them on the criteria that I have myself: they've got to have experience, they've got to have done the testing on the solutions that they've worked on. I think seniority is good too, little gray hairs don't hurt anything.

Regarding advice to others, invest in training. Invest in mentoring. Invest in experienced people that have done the job before. Don't go into it thinking that you're going to open the box, get it out, and it's going to be perfect. It's a complicated tool for a reason. You don't want someone operating on you who says, "Well, I read a book on brain surgery." It's complicated for a reason.

Nothing wrong with it, but I have to learn more about it to see if it's going to match our needs. Performance Center has everything which LoadRunner offers, plus additional things.

Have a well-defined process, have a strong reporting structure, meaning in your process you want a lot of measurability. If you define your output, the reports and the questions you need to answer from what you're doing, which your process should be managing for you. In our company, we are very specific about what our executives and stakeholders want.

We have a very well-defined set of measurements that we have to take. We then put a process designed to ensure those measurements are always taken. That then allows you to deal with your outputs and your reporting structure, which then allows you to properly architect your tooling. The technology is very flexible. You have to decide as a client area how you really want to use it and that's going to start with what your business needs are the values that you're trying to get out of it.

That's the biggest advice that I have, it's not even on the technology. The technology will do great things for you if you have a plan and a structure and you know what you want it to do for you. Half the time they don't know, they want the tool to do it for them and it's the other way around. So that's what I advise people to do.

Think about it, have a vision, have a plan, tie that to outcomes, and measure those outcomes. If you're answering the right questions and asking the right questions, your technology will really enable you. You've got to look at it from that standpoint.

During implementation, make sure you're talking about a cloud solution. You may be implementing in multiple areas, so planning is very important.

My advice to people considering LoadRunner is that if you are going to use the product, use it as part of your everyday application development lifecycle. Do not just use it right at the end, because it gives you some great insights during the development phase as well as at the end. You will end up writing cleaner application code with it. So bake the use of LoadRunner into your full application life cycle.  

On a scale from one to ten where one is the worst and ten is the best, I would rate this solution as between and eight and nine-out-of-ten. I could be slightly biased, having worked for the company that sells it. But it is a very good, professional solution. With the latest updates, it is very comprehensive and one of the best products of the sort. Let's say nine-out-of-ten because there is always room for improvement.  

When looking at vendors, support is the big one. Also, ease of training people on the tool, and just the variety of technology supported.

In terms of advice, I would say the biggest choice is that Performance Center really is for a very large enterprise. So I'd say evaluate if it's really what you need for the size of your organization. But if it is, it really can support pretty much any kind of technology you throw at it.

Performance Center is really our go-to tool for anything that we have to test. It's just our default tool for whatever technology we have.

Proper training is important. If you have teams that want to use the product, you need to ensure that they go through the right training. Get your guys to sit through the LoadRunner training or get someone experienced to train them.

Make sure that your team trains before they go and apply the system because LoadRunner is not actually something that you do, plug-and-play. You do need a little bit of configuration, and it's not for beginners. It is meant for people with at least an intermediate understanding of networks, and an intermediate understanding of performance application — you need to have that. I would say it's always important to ensure that you work very closely with the development team. To get the best out of the tool, you need to have a solid collaboration. When you want to troubleshoot, you want to review or uncover the performance issues; you need to make sure that you work quite closely with the development teams as well.

On a scale from one to ten, I would give LoadRunner a rating of eight. We have not used it for global distributed testing, and we also don't know its full capability from a mobile perspective. That's an area that I cannot comment on yet, so I'm reserving my judgment on that. That's the reason why I am giving it an eight.

From my perspective, there's still a gap in terms of the area that LoadRunner is being marketed to. Its biggest strength, in my opinion, is the reporting. If they could keep the reporting, but give it a lighter engine to generate virtual users, that would be perfect. 

My advice is to identify well the scenarios, protocols and maximum number of virtual users needed for load testing. Also, simulating a real-world load testing scenario is very important if you need to get a near-real results. For example, simulating network speed to reflect the real case. Some scenarios may require using a paid e-service, which may cost a lot when simulations repeat with a huge number of virtual users. At this point, another product called HP Service Virtualization could be used to sniff the in/out going traffic, then simulating the e-service function later after learning its function. At this point we can then replace the real e-services communications with HP Service Virtualization, so a budget-wise trade-off may be held between using HP Service Virtualization and the paid e-services. I recommend consulting HP presales to get the most proper setup with least possible licensing.

HP has very masterfully re-engineered this tool and integrated it with Application Lifecycle Management to create one of the most seamless project management suites I've used in years. When simultaneously integrated with Unified Functional Testing, which also supports service testing, I feel the richness of testing information that can be managed from within a single tool (ALM) is hard to beat--despite the price tag.

I would give LoadRunner Enterprise a rating of nine out of ten.

We're partners with OpenText.

I haven't found many products in this particular niche that have compared to JMeter and BlazeMeter tools.

I'd rate the solution eight out of ten.

I suggest other potential users review OpenText. If the client has the budget for the solution, I'd recommend it. If they don't have a budget, I'd suggest they instead opt to look a freeware solution, and I'd suggest they evaluate JMeter or BlazeMeter.

When looking for a vendor to work with the number one thing is does a tool do what it needs to do? Second, of course, support. Stability and the ability to scale are pretty important but I think that's grouped under the tool itself. It has to be an enterprise ready scalable tool.

Regarding the vendor itself, support, being responsive, having a way to access the support that's not overly obtrusive. I don't mind doing emails or logging onto a website, just as long as it's not too convoluted. Sometimes I feel like you have to go through 20 steps to get somebody to call you back and every customer support or technical support has their process. As long as it's not overly going through hoops to be able to access that.

In terms of advice, you have to do the math. There are a lot of free tools or tools that you write yourself. You just have to make sure that, long term, are those things maintainable, supportable? Do you have the training? Do you have the support? You have to bake all that in before you make a decision. It's not to say those other tools aren't valid, and people do a lot with them but, for example, if the tool needs programming skills, do you have those skills? Do you have a team with those skills? And how much is it going to cost to keep, hire, or maintain your staff with those tools? So you have to do the math to make that kind of decision, what the right tool is.

I think the tool does what it really needs to do and I've never had an issue with their support. I think they're definitely the industry leading product for performance.

When we selected a vendor, it was a trade-off between having the best in class and the price. It needs to be cheap and we need to get along with them.

Whether I would advise colleagues to choose this solution is entirely situationally dependent. It fits our needs and our project portfolio, but that doesn't mean that it will meet everyone else's needs.

I think it's the best product out there for performance and load testing.

Performance Center is not difficult to pick up for a beginner. When I was first introduced to Performance Center, I had just started my career as a performance test engineer. It is not completely intuitive though. I believe there are some extraneous requirements. As I mentioned before an experience administrator is recommended.

The command line feature allows you to set a parameter value at the scenario level. It can be applied to all scripts in a scenario. This feature has saved me a great deal of time.

When it comes to organization, people compare automation testing with performance testing. Automation testing is something that is very easily integrated within an agile and faster delivery framework. The scripting in automation testing is robust because it is GUI-based. When it comes to performance testing, it is request-response-based and the scripts are not very robust in some of the application platforms. Because of that, people feel that performance testing is a bottleneck and it takes a lot of time.

I would rate this solution a seven out of ten.

Technical support is the most important element for us when choosing a vendor.

I would say this is a very good tool as it allows small and huge applications to test with limitless size.

I would say that it is a great investment for your organization. Going forward, HP is going to implement many impressive new features in this software.

I would rate Micro Focus LoadRunner Enterprise an eight out of ten.

It's a very capable solution and I highly recommend it.

no

I like the tool.

Even though I was a beginner, I was at ease while using this product but I believe the documentation provided alongside it could be improved. It is a great product that provides one with an extensive amount of functionality.