BlazeMeter vs. mabl

It is well suited for applications that are mission-critical or applications that can receive high traffic/transactions at unscheduled time periods. Using the load testing feature of BlazeMeter, we can test and ascertain the capacity of the application without the drawbacks of the usual Apache JMeter load testing which depends heavily on the host system from where the load testing is performed.

Incentivized

We haven't found a scenario yet where it hasn't been appropriate. We did have one function on our application that mabl couldn't do, but they solved it and got back to us very quickly. Our application is web-based and mabl is able to handle this very easily. We use the command line runner a lot. Being able to easily and quickly change from a cloud based run to a local run has been fantastic. Setting up flows and environments is a wonderful feature

Incentivized

• BlazeMeter takes the .jmx script that teams had written for JMeter. The transition from JMeter to BlazeMeter was seamless.
• BlazeMeter offers its own cloud and hence we did not have to set it up on-premise.
• BlazeMeter hits our application from various geographic locations that simulates real life users.

Incentivized

• mabl trainer - record and play back test cases
• Organization - labels and flows make this easy
• Customer support!

Incentivized

• Blazemeter reporting is very basic and shallow. There is no way to drill down or correlate. I can get better reports by using JMeter for free.
• Blazemeter is very costly. Testing with volumes of more than 1K cu is expensive, and can be done for much cheaper if a company/team is willing to invest a bit of time to figure out how to use cloud instances and jmeter slaves, and to write a basic script to collect resulting xml output.

Incentivized

• Asserts could be easier to add, but they aren't terribly hard

Incentivized

Easy to setup to do API Performance Testing. Dashboard to showcase results Capability to showcase runtime results

Incentivized

In comparison with Blazemeter the closes competitor is JMeter but it has disadvantages like it is not a tool that can be use as a collaborative tool and works locally in a computer, Blazemeter is in the web so different people can access and run tests or collaborate do add, edit or delete the existent scripts.

Incentivized

We ultimately selected mabl cause it most met our needs and our budget. We needed a low code UI automation test tool. We also have a suite of existing testing tools and other tools that it needed to be able to integrate with. Price was the only thing that ruled out some of the above tools, we are a small start up, and don't have a huge budget. Some tools listed didn't have the same functionality or ease of use with the record and playback. mabl works on our machines and integrates with our existing tools

Incentivized

• It helped positively by helping to identify the maximum capacity needed for high traffic periods
• Saved revenue by eliminating unwanted duplication of systems

Incentivized

• We are able to more quickly automate UI tests

Incentivized