IBM DevOps Test Performance vs. SoapUI Open Source, supported by SmartBear

Go for IBM RPT if: 1. You're testing a Java-based Web application with HTTP protocol 2. You wanted to distribute the load across machines easily 3. Your team is in learning phase/not really introduced to a wide range of performance testing tools Do not go for IBM RPT if: 1. You wanted to test REST or any other advanced protocols 2. Your system under test demands a very high user load 3. Your application is written in .NET or any other platform except Java.

Incentivized

If you are making system upgrade project and you have existing system working and you want to imitate messages that are going in production but without making any data loads or switch it’s very suitable and convenient software. It serves well in manual test scenarios but wouldn’t be as good in case of mass tests.

Incentivized

• Data Parameterisation/ Data Correlation is made simpler compared to its competitors
• Distributed Load Testing is easier to set up
• Performance metric gathering while a test is in progress
• Th look and Feel really helps a beginner to understand and work with.

Incentivized

• SOAP
• REST
• Authentication

Incentivized

• Memory utilization could have been improved.(Eats up system's RAM)! It may crash if a test is conducted with the heavy load if adequate RAM is not available in the VM/host machine.
• Licensing could have been made simpler. IBM's licensing method is difficult to follow.
• Support for protocols other than HTTP. Not really up to the current trend.

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

Cost/Licensing: While JMeter is an opensource testing tool from Apache, compared to IBM RPT and HP LoadRunner, RPT is much cheaper than Loadrunner. Functionality: JMeter provides basic functionalities which are adequate for performance testing, however advanced features are not available (such as load testing with GUI, reporting is very basic etc.). But when it comes to Loadrunner, it offers very broad features and supports a variety of protocols. So in this category, Loadrunner is a winner, but RPT is better than JMeter. Ease of operating: JMeter is easy compared to LoadRunner, but it has old GUI and look and feel is not that great to understand. Also, most of the things are to be done in a command line, non-GUI mode. While LoadRunner is very advanced with many options, which also confusing sometimes. But RPT, on the other hand, maintains a balance between simplicity and offering of different features. So winner: RPT.

Incentivized

SoapUI Open Source is free, which is good for light use or simple things here and there. There is a Pro version that makes things more user-friendly. I also like that custom code can also be used for doing more complicated tasks. I like that SoapUI can have a process/flow (conditional/loop/waits/etc.) set up for scripting purposes, which is good for beginners and light users. However, I think the user interface has room for improvement.

Incentivized

• Accuracy in metrics, thus improving system's performance
• Costs less compared to competitor like HP LoadRunner
• Helped the team of beginners learn things quickly

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