We performed a comparison between BlazeMeter, OpenText LoadRunner Cloud, and Tricentis Flood based on real PeerSpot user reviews.
Find out what your peers are saying about Apache, OpenText, Tricentis and others in Load Testing Tools.
"Using cloud-based load generators is highly valuable to us, as we can test from outside our network and increase load generation without having to upscale our hardware as much. The cloud load generator is there when we need it and is the feature we leverage the most."
"It has a unique programming dashboard that is very user-friendly."
"The feature that stands out the most is their action groups. They act like functions or methods and code, allowing us to reuse portions of our tests. That also means we have a single point for maintenance when updates are required. Instead of updating a hundred different test cases, we update one action group, and the test cases using that action group will update."
"Its most valuable features are its strong community support, user-friendly interface, and flexible capacity options."
"It supports any number of features and has a lot of tutorials."
"BlazeMeter has allowed us to simplify and speed up our load testing process."
"BlazeMeter's most valuable feature is its cloud-based platform for performance testing."
"One thing that we are doing a lot with the solution, and it's very good, is orchestrating a lot of JMeter agents. This feature has helped us a lot because we can reuse other vendors' performance scripts that they have used with JMeter before."
"The most valuable feature is having load generators in countries where we don’t have access to them."
"The product supports a wide variety of technology compared to any other tool."
"It is feature-rich. It supports most protocols, which is important because I am in charge of a team at the bank, and we do performance testing for all kinds of different applications. We have tons of them. We even do video streams."
"The record and playback feature is the most valuable feature. It's all driven by the script, so it's a script-based tool where the background tracing starts. Java's background process does a lot of tracing. The process starts in the background. It sees what peaks of volumes that the process can handle. It's easy to use because it's script based, record, and playback. I"
"The usability and ability to integrate with other solutions is quite good. When I use it in on Azure, then Red Hat is the most likely solution I use. When I use AWS, then I tend to use Lambda functions. In either case, it works well and you can use it either way."
"The fact that the solution supports multiple protocols such as open source, VuGen, TruWeb, TruClient, and SAP is very important because these protocols help us to concentrate on what is really needed to produce performance tests. If something is not supported, you have to use other tools or find other ways of assimilating loads."
"The reports are very relevant to the customers’ expectations."
"It's fast, easy to use, has a user-friendly UI, and you can split users."
"You can utilize this tool on the cloud, and also access application on-premises. That is a very good part of the solution."
"The most valuable feature is the support for Java, where we can quickly code what we need."
"Their technical support is awesome."
"BlazeMeter needs more granular access control. Currently, BlazeMeter controls everything at a workspace level, so a user can view or modify anything inside that workspace depending on their role. It would be nice if there was a more granular control where you could say, "This person can only do A, B, and C," or, "This user only has access to functional testing. This user only has access to mock services." That feature set doesn't currently exist."
"From a performance perspective, BlazeMeter needs to be improved...BlazeMeter has not found the extensions for WebSockets or Java Applet."
"The reporting capabilities could be improved."
"For a new user of BlazeMeter, it might be difficult to understand it from a programming perspective."
"We encountered some minor bugs, and I would like to have the ability to add load generators to workspaces without having to use APIs. We can't do that now, so we're beholden to the APIs."
"BlazeMeter has room for improvement in terms of its integration with GitLab, particularly in the context of CI/CD processes. While it has multiple integrations available, the level of integration with GitLab may need further enhancements. It is known to work well with Git and Jenkins, although the extent of compatibility with GitLab is uncertain."
"Having more options for customization would be helpful."
"I don't think I can generate a JMX file unless I run JMeter, which is one of my concerns when it comes to BlazeMeter."
"In terms of new features, they can natively integrate with Chaos engineering tools such as Chaos Monkey and AWS FIS. With LoadRunner, we can generate load, and if Chaos tools are also supported natively, it will help to get everything together."
"I'd like to see more ability to dive more deeply into the configuration."
"Reporting and analysis need improvement. Compared to the old school LoadRunner Windows application, the reporting and analysis are mediocre in LoadRunner Cloud."
"We are trying to put it into a complete CI/CD pipeline, but there are still some challenges when you try to run it through different protocols. The challenges are around how you can containerize applications. There are some limitations to some protocols, such as desktop. And when it comes to database testing, there are some things that we can't do through CI/CD."
"It should have a feature to report with a 99.9 percentile success rate."
"The product price could be more affordable."
"There is a steep learning curve for the product, too."
"Their documentation is not technical enough for us. We would like to have much deeper technical documentation so that we can self-serve without constantly having to go back to them and ask."
"We used an implementation strategy to deploy the solution, not because of the tools, but mainly because of the scripting part of the tool."
"The solution is quite immature, it is not in an optimal state."
"The performance of the tool needs to improve."
