BlazeMeter vs. XCTest

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

It is very useful to add it mainly at the beginning of the app when each feature is finished and if the greatest importance of the app is its stability and a quick way to fix errors that are made during the changes. Do it when the app is finished; it's going to be quite time-consuming; however, applying it will go a long way in making sure the code hasn't been broken by changes and improvements.

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

• Basic unit level testing of iOS apps/games and functionalities
• Xcode Test Recorder - mostly a feature for UI tests but as XCTest is related with XCUITest the UI recording is possible with Xcode environment.

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

• Occasionally confusing
• Fails with automated builds without giving a good reason
• Not super flexible

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

I haven't test any

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

• Faster way to know which issues appeared and fixed it.
• Easy way to install and teach to the programmers.
• More time invested on the project to implement.

Incentivized