We performed a comparison between Apache JMeter, BlazeMeter, and Tricentis Flood based on real PeerSpot user reviews.
Find out what your peers are saying about Apache, Tricentis, OpenText and others in Load Testing Tools.
"The most valuable feature in JMeter is the Thread Group, which helps us to see whether the performance is good."
"The ease of use is the solution's most valuable feature. Also, the ability to easily create test cases is also very good. It's easy to just ramp up on the solution."
"The solution is free. You don't need to worry about licensing costs."
"The solution helps by detecting bottlenecks."
"User-friendly and open source."
"The most valuable feature of this solution is being able to launch many requests and scheduling simulating human interactions with the application."
"API testing, Database Testing, and MQ testing can be done with ease."
"Due to process automation, I don't have to prepare reports, making it the perfect solution."
"It is a stable solution. When we compare BlazeMeter with other tools in the market, I can say that the solution's overall performance has also been very good in our company."
"The solution offers flexibility with its configurations."
"BlazeMeter can be used for both API and performance testing, it is a multi-facility tool."
"In our company, various teams use BlazeMeter, particularly appreciating its cloud license software, which supports up to 5,000 users. BlazeMeter's cloud capabilities allow us to load test or simulate traffic from any location worldwide, such as Europe, North America, South America, Australia, and even specific cities like Delhi. So, with one cloud license, we can simulate user load from various locations globally."
"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."
"The extensibility that the tool offers across environments and teams is valuable."
"I really like the recording because when I use the JMeter the scripting a lot of recording it takes me a lot of time to get used to. The BlazeMeter the recording is quick."
"With the help of the Mock Services, we are overcoming everything. Wherever we are facing issues, whether they will be long term or temporary, by implementing the Mock Services we can bypass the faulty components that are not needed for our particular testing."
"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."
"Apache should have a graphic interface."
"Running JMeter in GUI mode uses a lot of memory, which means we need to switch to a non-GUI mode when using a heavy load."
"They should improve the solution on its UI front."
"The solution needs more metrics for reporting."
"We would like some reporting and analysis tools to be added to this solution."
"The tool should be made a bit more robust, and better support should be made available."
"If the solution was GUI based, I believe that it would be more versatile."
"Improving JMeter's sync time would be beneficial."
"The reporting capabilities could be improved."
"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."
"Scalability is an area of concern in BlazeMeter, where improvements are required."
"The product currently doesn't allow users to run parallel thread groups, making it an area that should be considered for improvement."
"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."
"Integration is one of the things lacking in BlazeMeter compared to some newer options."
"In terms of improvement, I would like to have the ability to customize reports."
"From a performance perspective, BlazeMeter needs to be improved...BlazeMeter has not found the extensions for WebSockets or Java Applet."
"The solution is quite immature, it is not in an optimal state."
"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 performance of the tool needs to improve."
