IBM DevOps Test Performance vs. WebLOAD

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

WebLOAD is an imperative tool for our web manager and developers team. We rely heavily on this in our daily activities, mainly to run script testing (in record time) of new code prior to our build releases. This product helps us identify potential gaps and issues with the user flow and allows us to make adjustments and fix problems before they make it into the live production site. Our team also depends on this software to run multiple load testing of each server in preparation for heavy timeframes of the year, such as Cyber Monday, Black Friday, etc. Our team members brought up that they would love to see more scripting examples of how to use WebLOAD, which would make their job easier.

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

• Load testing of increased traffic during peak hours
• Reporting of script runs before new code releases
• Identifies issues and problems with the code before this makes it into the live site

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

• The load time of running a testing script can be long at times
• It would be helpful to have multiple users/ devices to run under one membership

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

There are many similar comparable products on the market, but with WebLOAD, the price point was reasonable. Their sales and engineering teams and very friendly and helpful and make our implementation a breeze. I would definitely renew our contract and recommend this to anyone out there looking for the best load-testing tool!

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

• Increased ROI by discovering any performance issues ahead of time, and allowing us to fix them before making it into production.
• Improved efficiencies with DevOps.
• Increased productivity through the automated reports feature.

Incentivized