JMeter vs IBM Rational Quality Manager

• Easy of use - in generate load like HTTP requests, and processing/analyzing the responses. No coding is necessary at the basic level, just need to understand load testing and the infrastructure being tested.
• Automatic management of things like cookies to help with session state support - so you don't specifically have to worry about it or handle it
• Lots of testing/configuration options to suit your needs in making the right load generation (sampling requests), and analyzing the results, including any pre and post processing of the results first. Things like the Beanshell/BSF pre/post processors, response assertion, regular expression extractor, XPath extractor, CSV data set config
• There is a JMeter cloud service called BlazeMeter that I think would be useful for those that need to scale up high load without provisioning their own systems. I've not personally tried it though, but I recently attended a meetup presentation that highlighted nice useful features that BlazeMeter provides. One should evaluate the service if they are considering JMeter and need to expand beyond existing hardware resources.

Read full review

• It's part of Rational CLM suite so provides seamless integration with the Change Management module (RTC) and Requirement Management module (Rational DOORS).
• It can be integrated with IBM Rational automation, performance and security testing tools which provides an easy way to schedule or execute the scripts from RQM console. Results are linked with test plans
• Provides Lab management facility, which helps to maintain, allocate and monitor your testing assets like test servers, devices etc.
• It provides good way to manage multiple test execution cycles. all execution cycles are linked with test plans.

Read full review

• Jmeter requires many tweaks with respect to its configuration file and thread properties. users need to edit theses files themselves. There could be some interface where we can edit this fields.
• Jmeter cannot handle more threads and hangs up when we increase the number of threads. This causes lot of inconvenience. In these situations, user can be notified that such change would be lead to slow performance so that user can do as required. The same appears when we try to view huge files on graph listener.
• Jmeter should optimize the read and write access to output csv since it acts as overhead to the I/O performance. This affects our test results for the application which we are testing.

Read full review

• It does not provide any functionality for defect logging. For defects, you will have to have Rational Team Concert. So it's useful if you have the complete suite.
• Similar to defects it also does not provide builtin functionality for requirements. Requirement module needs to be purchased separately .
• It does not have query builder like in RTC, where a user could define its criteria and see the results easily. There is some mechanism to filter the results while you browse test plans and test cases but it's not very user-friendly and sufficient.

Read full review

• Gives liberty to developers and testers to perform testing. Easy to set up and run load tests, stress tests has improved testing.
• Enhances the performance testing which ensures the delivery of well-suited applications.
• The Enterprise messaging system, it's a great tool which helps in testing JMS based messages.

Read full review

• As a part of Rational CLM suite, it provides end to end traceability.
• It offers coverage report to managers and test leads so that they can identify the gaps in testing.
• If testers are familiar writing test cases in Excel sheets, it can be a little challenging to ask them to write all their testing artifacts in the tool, because they have to write a test plan, test cases and test scripts separately and then combine according to need. This requires some level of enforcement.

Read full review