What is your primary use case for Micro Focus LoadRunner Professional?

We use OpenText LoadRunner Professional to run performance test for codes.

It's mainly used for performance testing. One of its features called TrueClient has helped us see how users interact with our applications.

My use case is for load testing and fine-tuning the system to prevent risks from going to production.

We use the solution for load testing.

We primarily use it for load testing. We were seeking AI-enabled load testing, where we could input functional requirements. The idea is that the tool suggests test cases based on those requirements. This would help us streamline the process and reduce the time due to our limited staff for load testing, considering we handle around 200 projects a year. Our use case is to address resource constraints.

My use cases span various industries, from banking and energy to health care and now in telecommunications. The requirements encompass tasks such as load generation, finding response times, UI interaction, and identifying network issues.

Our use case is very complex because our company uses a lot of tools. We have more than 500 applications. Some of them are legacy applications created 40 or 50 years ago. We have applications created with different platforms such as Visual Basic, .Net, and C++. We have different platforms. We have mainframes, but LoadRunner is always perfect. It is able to handle everything.

The main purpose is to simulate realistic scenarios to define and test the performance of different solutions or applications. For example, if there is a project to launch, a mobile app, and you want to see how it's going to perform when it is used by multiple users, OpenText LoadRunner will provide in-depth reports on potential performance bottlenecks and issues.

We use the solution to help customers test web applications.

Based on the requirements, we use Micro Focus LoadRunner Professional. Our clients have their licenses and access. So, we execute in the client environment itself, which involves, basically, running a load test or stress test using the tool and analyzing the system performance with different metrics like server session and clientset.

We primarily use the solution for enterprise performance modeling and validation of enterprise networks as well as tax applications.

We've been using Micro Focus LoadRunner for load testing to simulate the load and applications for microservices and Salesforce UI applications.

The solution is a performance-assessing tool. It supports a myriad of protocols. That is a big advantage of LoadRunner.

The solution is used for scripting and debugging.

My customers use it for performance testing. It is the ultimate tool for it.

We primarily use Micro Focus LoadRunner Professional to create scripts and run various types of performance tests, as well as to analyze the results.

Our primary use case was for performance testing and platform application problems. We used it mainly in the banking sector and for API testing. It's multi-purpose. I recently moved to a different company.

We are customers of Micro Focus and I'm an end-user.

I use this product primarily for performance testing in various software applications. There are web-related use cases, as well.

We are it using the solution mainly for the REST-based API.

We use this product to test our web application that is used for internet banking.

We use the solution for client service applications, mostly web-based applications. There are a lot of service conversions needed in terms of Apple to Apple talking or using with a protocol. If you need what they're offering then I think LoadRunner is a good tool. And it's from HP. Primary use cases are creating code-based operations for the latest updates, and API calls if we are in corporate. I'm a QA leader and we are customers of Micro Focus LoadRunner.

All of our installations are on-premises at the moment.

In our organization, the solution is required for the testing of the performance of applications, response time, and the utilization of resources.

We have several use cases for this solution. One of them is an automobile website for a huge dealership and we are doing load testing for them. We have projects in the hospitality industry, like hotel bookings. Our projects involve both API testing as well as browser-based load testing.

I am primarily using LoadRunner to perform tests on HTTP and HTTPS.

We primarily use the solution for performance testing and performance tuning.

We primarily use the solution for a variety of cases; the use case depends on the application.

Our primary use case of this solution is to do testing for banks and financial institutions.

Our primary use case of this solution is for performance testing and load testing.

We use this solution for performance testing, and to identify bottlenecks.

The primary use is for load testing and stress testing of applications. It tests whether services are running at an optimal point or not. It can also be used for benchmarking with other industry standards.

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

Our primary use case for LoadRunner is a lot of business transactions, physical scenarios, and incoming applications. We use LoadRunner for building and it is very easy to use because of its support for all of the protocols. LoadRunner is a very systematic tool for anyone to use. Even someone who is actually a first time user of LoadRunner can actually get a lot of benefit out of the tool.