Apache JMeter vs. Parasoft SOAtest

JMeter is well suited for Java applications where the user can script the scenario once and make changes to accommodate for as many numbers of users for load test execution. The image and selection of any files or exporting files scenario is handled well.

It is less appropriate to test Ajax applications where it is required to script click per use.

Incentivized

This is the go to tool for all the web service testing needs. You can do functional testing, regression testing, automate the testing and drive the data from external sources like a Excel spread sheet or an xml document and finally performance testing. It can get better in scenarios where the response is to be compared with UI, with more automation. The license cost needs to be considered when there are many open source tools out there in the market.

Incentivized

• 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.

• Organized test suites.
• Fast and efficient execution of automated testing.
• Built in Javascript that can be used to run test cases with a repository tool such as HP Quality Center. This will show the test results and allow the QA engineer to pass, fail, or set a test case to N/A.

Incentivized

• 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.

• As always, this is not a free tool and you have to pay for license. There are many open source tools which can perform similar job with no cost albeit with less functionality and more head work.
• There is still some more room for improving the automation which can include more UI level components to make life lot easier when comparing the response vs UI.

Incentivized

Price, Wiki and user sharing. Having access to the information provided by the developers and other open source providers is key for me. The ability to share information and get answers directly is very important to success in software testing. And the price of this product currently is amazing. Too many companies charge way too much money for products that are far behind in their value and pertinence

I have used the tool at a previous company and I love it.

Incentivized

I can jump right into a new test plan and start building from scratch. The natural progression from test plan to thread group and then designing the basic format of the process is very streamlined and smooth. With only slight modifications I can build out a very complex model from a very basic beginning.

never had any issues

Incentivized

I have been using JMeter for the last year. By using this tool, you can make sure the system will work under varied loads. It helps us to simulate real time scenarios by creating required virtual users and make sure the application will work under load. Perform load, stress, and stability testing using JMeter.

Incentivized

anytime I had a question, I received feedback the same day from a representative at Parasoft SOAtest.

Incentivized

Yes, I would like to know if there is any action to have Parasoft SOAtest integrated with Microsoft TFS

Incentivized

I have used LoadRunner and Silkperformer, and so far Jmeter turns out be the easiest to use of all these. While each of them have their own ROI, Jmeter can be picked by anyone in hours and start testing within a day. While with other tools, we need to get license, install them (takes a while) and setup tests and firewalls, etc.

Parasoft SOAtest stands out among all the other tools.

Incentivized

• Good ROI on improving the performance of the application.
• Finding issues in the performance.
• Benchmark the performance results.
• CON: Need skillset to create and maintain the scripts in Java.
• Scripts are reusable and it is executed by any user.
• Need Client and Server setup to execute the scripts.

Incentivized

• It has been of tremendous help as the ONE STOP TOOL to test the APIs end to end. Ease of use is great and their support staff is excellent. They always conduct brown bag sessions for us to learn about new features. Overall it has given us a great ROI considering how fast we can test and deliver to market.

Incentivized