By implementing LoadRunner Cloud, we wanted to make sure that our applications are stable when there is a peak load with 3,000 or 4,000 users. We wanted to make sure that our applications are stable at any given point. To validate that, we are using LoadRunner Cloud. We are putting our expected load through LoadRunner and making sure our applications are stable.

We can plan and run tests using LoadRunner Cloud without having to manage testing infrastructure. That is very helpful. One of the reasons why we moved to LoadRunner Cloud was that they manage the infrastructure, and it is up 99% of the time. We used to support Performance Center, which was on-premise, and we also support application servers and all the load generators. It is a lot of work to manage them. Migrations, security scans, and all the patching take a lot of time, whereas, with the cloud option, our work is reduced by 50% to 60%. We can now focus on testing instead of managing the whole infrastructure. LoadRunner Cloud has been very helpful. It is stable and user-friendly. They provide scalability. They have a flexible licensing model, so everything is great.

LoadRunner Cloud has partially saved us money by not having to maintain hardware and the power costs associated with that hardware. In my company, we are still using on-premise load generators, so in our case, the savings are a little bit less, but any other company that has all public-facing or hosted applications does not need to spend any money on on-premise infrastructure. Because we are using a hybrid version, we are still spending some money.

OpenText LoadRunner Cloud helps us save money through its flexible scheduling feature. We can shut down resources when not in use, minimizing costs.

OpenText LoadRunner Cloud eliminates the need for our own testing infrastructure when running tests.

I love that we can plan and run tests using LoadRunner Cloud without having to manage testing infrastructure. That was a part of the reason we went to the cloud. It was not too bad to manage Silk Performer infrastructure, but it was still a pain. 

By moving to the cloud, I am hoping we can spend less time managing and more time testing. I also hope that LoadRunner Cloud will save us money by not having to maintain hardware and the power costs associated with that hardware, but only time will tell. I do not know it yet.

We have an infrastructure that is developed on the cloud. We use the product because it is more feasible to have our applications on the cloud. It is a trustworthy brand. The data I present to my customers are to the point. I do not have to check on the matrices again to verify whether it is false.

Before LoadRunner, we weren't even testing performance and now we're performance testing. So we now do performance testing as part of the delivery of a new release, which is an improvement compared to a couple of years ago. 

One of the main benefits is that we don't need to worry about load generators. Before we had Loadrunner Cloud, we had 10 to 20 load generators, and we needed to maintain them. There were always upgrades. We would also have to configure the load generators when we were ready to test, and at times there was stuff to clean up. None of that is necessary anymore. We can concentrate most of our time on creating scripts and configuring Loadrunner based on our objectives. It's very easy for us. We don't need to worry about what happens in the backend or how the load is distributed.

A second advantage is the reporting system. Once a test is done, even if it's in continuous integration and continuous delivery, it automatically triggers and produces reports. We can send the reports to multiple dev teams whose developers are expecting the reports.

Another advantage of the solution is seen compared to others we have used, like JMeter, and IBM solutions. LoadRunner has reduced a lot of the time involved in the scripting cycle because of TruClient. We only need to record one time and we can configure it accordingly to create various scenarios. It has reduced scripting time by about 50 to 60 percent.

When we do mobile applications, every build can be tested with LoadRunner Cloud. Once the developer checks into a particular branch, we call it a mod branch, the performance test is already integrated into it. They can trigger it through their continuous pipeline. For mobile development platforms, it's very crucial because notifications and other things need to be tested before we send to prod. Notifications are very load-sensitive because they go to every user—it could be 10,000 or 20,000 users—and we previously had issues with this. Using LoadRunner Developer and continuous integration has helped us.

better decision making was done Business KPI & technical KPI can be set by automating loy of endurance testing where given resources thresholds capacity can be measured against  business kpis

The best benefit would be budget. It's a really inexpensive if you are testing your application every spring or every month. Even for less frequent applications that you have to test regularly. You can hook up your infrastructure to StormRunner Cloud and you can get the best of both worlds.

In larger enterprises, we have different departments using Performance Center and StormRunner or Selenium. So, StormRunner can act like an umbrella and plug-in everything, get it executed or done across the world. Since they use both HPE Cloud, AWS, and Microsoft, it uses more access points geographically to test it making it best of the class.

The solution has improved the performance of the software.

We can determine response times for our external applications, from most places around the world, for a small fee.

We do online testing for the States as we have contracts with them. We have to be able to support a certain number of students, so this helps us confirm and validate that we can support the number of students that are taking online testing at one time.

HP StormRunner Load has provided us a) flexibility for on demand load generation b) reduced over all TCO on our load testing efforts c) Reduced the skill level to develop load test scripts.

I had to do overload testing on our homepage. I couldn’t use our regular tools because I wanted to simulate a real scenario and StormRunner Load does this. It enabled us to upload the scripts into the cloud and gave me unlimited resources.

It's used to improve our customers, but we don't use it in-house.

Being able to setup and run 300,000 load tests using LoadRunner Performance Center takes around 1 to 2 hours when creating four scenarios of 75,000 each, including allocating/blocking load generators required for testing, initializing the fusers and running the test.

Running a 300,000 test was very easy using StormRunner. We just had to upload the script and create scenarios for 300,000 and run the test in 20 minutes.

Running back to back high concurrency test was very easy using StormRunner.

We are not benefitting a lot at this time because it has its bad parts.

I have been able to run several tests from outside the corporate LAN, which in the past used to be an infrastructure nightmare as it required opening up ports, disabling firewalls, etc.

StormRunner Load helped us evaluate the performance of the product version we were about to launch. It showed us bottlenecks, where our product reaches its limits, and different characteristics that affect this. For example, we had metrics we thought were affecting our response time. Initially we thought there were two metrics, but we found another significant metric we should have taken into account. Without StormRunner Load we wouldn’t have known about this "missing" metric.

This solution is SaaS based so we can utilize cloud technology, which is less time consuming and saves a lot of of money.

LoadRunner Cloud allows us to do performance testing without having to create our own physical infrastructure and set up a load generator. Normally, these steps would be required.

This software solution has allowed us to run larger, high concurrency performance testing cycles in a very repetitive manner…a requirement for validating our application solutions and supporting infrastructure for customer facing web apps.

Its ability to work well with other HP products, particularly SiteScope, allows us to maintain consistency in our infrastructure. The different solutions work seamlessly together and free up resources that would otherwise be spent on conflicting vendors and products.

We are able to ensure very quickly and frequently that our product is ready for prime time. Using StormRunner, Codefresh has managed to identify performance issues and when these issues are introduced.