BlazeMeter vs. SoapUI Open Source, supported by SmartBear

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

Good for simple requests, simple scripts, assertions, and small workflows. Also not bad with the Open Source version if savvy with code as you can do a lot with custom functionality.Free version has limited compatibility with scripts/projects created from the Pro version, but functionality-wise can probably be made up with coding. As such, the free version may not be too suitable for complex scripts or for those who are not familiar with coding as functionality/usability may be limited.

Incentivized

• Results are easy to read
• Tests can be run easily
• Tests can ben imported easily from jMeter

Incentivized

• Ease of implementation
• Ease of use
• User friendly interface

Incentivized

• BlazeMeter should not require the purchase of 2 dedicated IPs for each suite of performance tests.
• BlazeMeter should make custom packages cheaper than they are today when purchased for an enterprise and should include dedicated IPs in the package.
• BlazeMerer should have integration with Jenkins Pipeline 2.0.

Incentivized

• I actually like SoapUI as it is, I have not found things to improve, except for the speed of response is very complex services.

Incentivized

Personally, I prefer using JMeter + Redline13, however we had some business folks that wanted to be able to run a few of their own tests. The non-technical individuals preferred to use Blazemeter because of its simple and intuitive UI.

Incentivized

Compared to SoapUI, we have been using "light" tools like RestClient extension in Firefox, or Postman. Compared to Postman, SoapUI is more simple for WSDL / SOAP webservices, as SoapUI generate all envelop, but Postman does not. For Rest API, I think that Postman is a little above SoapUI, but not too far away.

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

• Testing resolves most of the issues in the development phases.
• User friendliness of the app makes it good.
• Overall client happiness depends on the clean project, which is possible by testing.

Incentivized