AutomationHQ vs. BlazeMeter

The AutomationHQ tool is well suited for small to medium size projects, but sometimes there is difficulty in the case of complex elements which are present within multiple Iframes.

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

• The best thing I liked about AutomationHQ is that it intelligently identify web elements and track changes in real-time applications
• It supports Data driven testing from mainly three data sources from Excel/XML/JSON
• There are myriad pre-build test steps, which we can use to built our own scripts.

• 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

• AutomationHQ doesn’t have test cases version control, we have to currently manually do this by copying the test script and [renaming] with the version. I wish AHQ can implement the version control so I don’t have to keep test script copies
• Complex elements like within multiple iframes have difficulty at run time. It seems we have to run it multiple time until AHQ's AI algorithm "learn" what is the right way

• 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

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 have received gains for about 150% over a long period of time

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

Incentivized