JMeter vs SonarQube

• 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

• Core competency of static analysis. This is why SonarQube exists and it does it exceedingly well.
• Customized quality settings let you tailor the tool for your specific needs.
• Support for many languages including C, C++, Python, and more.

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

• Have a way to ignore the issues that the team decides not to fix.

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

• It became easy to identify the bugs and issue generation.
• It is open source thus saving money.
• Enhances the code quality and standard.

Read full review