OpenText LoadRunner Cloud Reviews

I have been using the solution for testing Salesforce and a few other applications.

The solution has improved the performance of the software.

The solution is intuitive, easy to use and navigate.

They should minimize the use of coding for the solution. Also, they should include features to import other scripts without rewriting them.

I have been using the solution since 2019.

It is a stable solution.

The solution is scalable. I rate its scalability between a seven and nine out of ten.

The solution's technical support has been good.

Positive

We have used StormRunner and JMeter before. Also, we are doing a proof-of-concept for NeoLoad.

The solution's setup process was easy. Although, we encountered a few issues sometimes.

The solution is expensive. There should be a version that optimizes the price-to-performance ratio for the service package.

The solution is costly. I rate it a nine out of ten.

Our primary use case for the solution is performance testing, validation and baseline testing. We deploy the solution on the cloud.

We find the ease of infrastructure maintenance and the enhanced capabilities of the cloud version, such as browser metrics, valuable.

The product price could be more affordable compared to similar products.

We have been using the solution for approximately three years.

The solution is stable.

The solution is scalable.

The initial setup was straightforward, and it took approximately a day.

I rate the solution a nine out of ten. My advice to users considering this solution is to pay attention to scheduling.

We use it to get response times around the world for external applications. We use it on top of our own virtual users for remote site testing. We include it in our scenarios in our performance center and use the results in the LoadRunner analysis tool.

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

The most valuable feature is having load generators in countries where we don’t have access to them.

An area for improvement is analytics on why response times are slow from certain countries. Slowness can be caused by the laptop, the connection, the VPN, the internal network, the country's internet, etc.

It has been stable every time I have used it. We don’t put much stress on it since we have our own performance center and load generators.

In terms of integration and configuration of the product in our AWS environment, it is the easiest Micro Focus tool I have ever used.

The pricing is very reasonable and the licensing is straightforward.

You decide on the number of virtual users you will need to support multiple runs or for a year and purchase that quality of virtual-user hours. We chose to procure this solution via the AWS Marketplace because of remote site testing and low cost.

I rate this solution a ten out of ten. It addresses a need in performance testing tools and is easy to purchase and use.

The reason we chose it and the most valuable feature is the amount of virtual users we can run in a test. We have run up to 900,000 users.

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.

I think the reporting could be better. I think you could have a little more variety of reports. Right now, you get an email saying, "Here's your report". You can't put in the analysis tool. You can't export it to Excel. Those are the things that would make it a little better. That's probably my biggest pain point, it is the reporting.

I think it's fairly stable. There's some features that I think could be made better but, for what they have, I think what they have works well.

I think it scales really well. I like that you can add users on the fly or remove users on the fly. That's a great feature.

I have used the support. We were one of the first users for Beta, so we have a relationship with the developers, so we tend to just go right to them when we have questions or problems.

They've been great. A lot of the times, it's not really a problem with StormRunner, it's just our understanding of what it's supposed to do, so they are very great about explaining the reasoning and what will be coming in the future. If we don't think that's really what we want, they'll explain how it's in the roadmap and how it's going to be made better.

We were using another HPE product, Performance Center. We haven't totally switched, but StormRunner Load is our option for the test where we need a lot of virtual users where we can run it in the cloud. Whereas, on Performance Center, you have to have load generators in-house, or what HPE provides. That's why we use it. It's for when we want to use a lot and perform a big test.

I wasn't involved in the deployment.

Not really because we're mostly an HPE shop and this was working with HPE they to meet our needs, so they provided this and it's worked out great.

I don't like their reporting. Other than that, I think it's great. It does what it's supposed to do and I know it's just the beginning, so there's going to be a lot more features added.

You should look into it. I know there are other solutions that have more bells whistles, but,when it actually comes down to function, I think StormRunner does the job.

StormRunner Load reduces the overall time for performance testing engagement and is best suited for the products in agile process. Easy to automate and execute the tests, StormRunner Load provides a feature to compare the current test results with the previous results to see if the current build is better than the previous or not.

With the ability to integrate with monitoring tools like SiteScope and APM tools like New Relic, performance bottlenecks in the applications can be identified very quickly and easily.

Protocol Support

StormRunner Load supports Web, Web Services, SAP Web and JMeter scripts

Easy Automation

StormRunner Load uses Truclient and TruAPI (which uses node.js) which enables developers and testers to quickly automate the user actions at the browser level, which also helps measuring the end user experience by measuring the browser rendering times as well. Performance testers can upload their LoadRunner scripts that are developed using LR 12.XX to StormRunner Load directly.

High Scalability

StormRunner Load is highly scalable and supports upto 1 million concurrent users.

On Premise Load Generators

StormRunner Load introduces the concept of On Premise Load Generators to compare the application performance within the network to various other geographical locations.

Configure SLAs

SLAs can be configured in StormRunner Load during the test execution. The tool highlights all the transactions that did not meet the SLAs and further drill down can help the users understand the geographical locations and times where the SLAs are not met.

Real time anomaly detection

During the test execution, StormRunner Load detects any anomalies where the test results are deviated for a specific transaction / geographical location / script / counter to identify the issues real time and further drill down provides more details about the anomalies.

Integration with Monitoring Tools

StormRunner Load integrates with monitoring tools like SiteScope to provide the hardware and application level metrics during the performance tests. StormRunner Load can also integrate with New Relic and other similar APM tools that helps identifying the server side bottlenecks so that organization can reuse investments

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.

Custom load patterns for the performance tests: Currently StormRunner Load supports only linear ramp up of the user load and doesn’t provide the user load to follow a step incremental load pattern or any other pattern that a performance tester wants to.

Load distribution among on premise LGs: StormRunner Load currently supports load generation from only one of the On premise load generators and the user load cannot be distributed to multiple on premise LGs.

Simulation of latencies: There is no provision to simulate network latencies to simulate realistic geographical locations and mobile networks.

Ability to create custom reports: StormRunner Load provides only the default reports and there is no provision available currently to generate the custom reports

Backward compatibility: StormRunner Load expects the LoadRunner scripts that are generated from LR 12.00 and above. Any scripts developed using the older versions are not supported.The work around to overcome this problem is to open the scripts in LR 12.00 or higher and save it again before uploading to StormRunner Load..

We have used the product for more than 14 weeks now and tested on some of our internal applications in the organization that would require performance testing.

HP StormRunner Load doesn’t need any installation or deployment unless you wanted to configure few on premise load generators. Configuring on premise load generators is pretty straight forward. All that you need is to have an account with HP SaaS to start using StormRunner Load.

HP SaaS web application is pretty stable and no issues were seen during the evaluation process.

There were no issues with the scalability, however, the time taken to initialize the test is directly dependent on the number of users to be simulated.

5/5.

The support provided to us very good which helped us to evaluate the solution for our context.

We are in the process of adopting a SaaS based option, this led us to evaluate a bunch of tools.

It is simple - just registering with HP SaaS platform called pronq.com.

We evaluated through our in-house resources.

Our estimated ROI is positive we need a couple of months to gain insight into actual ROI.

HP StormRunner load is SAAS offerings so the initial setup costs are very minimal when compared to the traditional approach (no or minimal capex ), and the day to day costs would be purely driven by the duration and number of virtual users required to simulate the traffic.

We have evaluated HP StormRunner Load against other market competitors that include Blazemeter, SOASTA’s Cloud Test, NeoLOAD, VSTS, Load Complete and StressStimulus.

HPStormRunner load is an apt product a) if your application stack has Web 2.0 traffic b) your requirement is for a service that allows for pay as you go model c) proven and reliable load testing solution with superior support.

This review was co-authored by Sravanthi Naga & Ramanjaneyulu Narra, Performance Architects at Gallop Solutions. Gallop is a US based Co-located Independent Testing Services operating since 2003 with offices in Philadelphia & California. World's largest and leading organizations have relied on Gallop's specialist independent software testing services for more than a decade and have achieved significant market acceleration, returns on investments in their software quality initiatives.

The platform is easy to use for uploading and backing up 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.

The monitoring abilities were lacking. The reporting didn’t present the information in a clear manner for me. It took me four days to understand why I couldn’t upload the scripts from my computer to the cloud, and I discovered I was missing an important feature that StormRunner Load is missing, called Corver, and this converts the script for the tests.

I used it once in a testing session and have been using it for one month in a live environment.

No issues encountered.

There was a bug and we opened a ticket with HP, and it was fixed after a few days.

No issues encountered.

It was great, there was an issue and I worked with Kim from HP who was great.

It was great.

No previous solution used.

It was straightforward, we just needed to register on the site. In comparison to other HP products, it was very user-friendly.

We did it in-house.

The most valuable feature is the ability to configure browser settings for different operating systems and on different versions without the need to install every single version on each machine and to manage them. This is the most useful feature that I'm interested in.

I'm also interested in mobile center services related to StormRunner functions because we are going to determine which will be the best solution for developing mobile testing. And we are interested in outsourcing mobile testing, so this kind of environment will be useful as we are not engaged in the configuration of infrastructure. Also, I think it will be useful because Storm Runner functionality does not need specific configuration because the configuration basis is in the UFT and the UFT can be in our environment. We do a lot of configuration because we develop a custom framework related to UFT. So, I appreciate that configuration can be managed by us, while the browser can be released on the remit version.

I'd like to see more ability to dive more deeply into the configuration.

I think the product is still immature because we have some problem reaching the mobile center connection related to a proper configuration on our machine. In fact, we are in touch with the R&D team to fix the configuration for our environment. I also think that it will be useful to have an object recognition tool because the specific configuration on the browsers are to be managed so as to fix our specific test. I need to recognize what was the configuration on the remit browser and I need a tool to analyze the impact of the browser configuration on the test.

I think the scalability is fine with this kind of solution because I have no problem with how many machines will be available to run the test; it's a matter of the cloud provisioning. It will be useful to run the tests in multiple environments in parallel. That will be a good tool for us when we have to make tests with a shortage of time.

I have not used technical support recently. HPE support is always prompt to solve the issues. That is the main thing I appreciate regarding support.

JMeter script integration. This integration feature is a good approach provided by HPE. Sometimes, we need to run scripts developed in an open source tool like JMeter. Instead of spending time on creating new scripts, the scripts developed in JMeter can be uploaded and based on the protocol license because it is a DEV user protocol, it provides a valuable feature when integrated with StormRunner.

Monitoring and sample access to servers needs to be provided, so that we can explore this and keep up-to-date.

The licensed version / free edition needs to be configured with SiteScope or AppDynamics, which many customers might not have. The LoadRunner feature of Windows Resource Monitor should come in handy in such scenarios. It is not only for Windows-based monitoring but also for UNIX-based monitoring. Dependency on the other tools or HP tools (SiteScope) would be reduced.

It needs to be more mature.

The client breakdown is a separate report and is not part of the existing load test report. The client breakdown is basically the response time observed from different browsers. We need to take a snapshot and place it in the load test report and that is not available when the load test report is generated from StormRunner.

Also, for the VuGen Web protocol, it supports only 12.50 and above, which is tough and compatibility is lost.

More than a year and half

I did not encounter any issues during deployment, but there are not enough tutorials available for the TruClient protocol and also on the reporting side.

I have worked extensively on the various module supported by STRL2.1v and provided my suggestions/improvements/recommendation to the HP R&D Team

Good

The level of customer service / technical support is satisfactory, with a few times good.

For example, when trying to learn the monitoring feature of StormRunner, I requested access to the Web Tours application that is installed on the server so I could explore that feature in depth. However, access was denied (monitoring-only access was provided). My question was: When both the application and the tool belong to HPE, why was access denied?

The end user needs to have strong skills in any of the load testing tools, specifically if they already have experience with LoadRunner.