BlazeMeter vs. Ghost Inspector

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

1. It's amazing for all kinds of browser testing. 2. Very easy to use and you can implement it to cover your tests in a short time. 3. You don't need to be a coding guru, many stuff are autogenerated or builtin and can be easily implemented without huge efforts 4. Reporting and UI is easy to understand and navigate through

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

• UI Integration tests
• Asynchronas execution of suites and tests
• Easy way to generate steps of the tests with Chrome plugin

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

• The number of available integrations is small, but I see more integrations are coming on the way
• Provide builtin alerting system in case of test failures
• Improve provide more roles not only user and administrator. A viewer role for example

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

1. Faster in terms of time when building the integration browser tests 2. No or minimum development skills needed. 3. No server management is needed on our end. 4. Covers a lot of browsers and cases 5. Builtin integrations for different stuff like slack and PD 6. Fast and provides asynchronous executions

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 saved a lot of money by using this tool instead of purchasing expensive ones
• The implementation of integrations test was supposed to take 6 months of development. With GI it took 2 months only
• Training QA to build integration tests using GI is much less that any other tool that might need development skills

Incentivized