Apache JMeter vs. Micro Focus Business Process Testing (discontinued)

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

You may want to consider this solution if you are already using HP ALM and HP UFT. It's a nice add on and encourages the team to think more on building small component based tests and promote lot of reuse. Also, if your team want business analysts or any non technical people build tests based on the flows, its probably the best solution available now. On the down side, the execution times if you have too many components are not great and on top of that you have to pay extra for the licensing. You can also build such frameworks using more open source solutions like bdd solutions.

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.

• Biggest advantage is - you can use the same components created for manual as well as automated testing
• It has a nice little feature called extended capabilities where you can easily automate tests SAP and oracle type architectures.
• Easy access library lets you create highly reusable and shareable components and the integrations is not that difficult

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.

• If you are using components for automation testing, the time it takes to load a new component is too high and it sucks off the benefit of component based testing.
• You want to have many components in a test and so a BA can also create automated tests easily but too many components takes too long to executed .
• It comes with a cost. You can simply build a modular framework even without this framework and probably more efficiently.

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

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

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.

The idea for building a component based modular test framework is great and it would be great add-on to HP tools if the add-on efficiency is made high and the cost is low.

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

• As the tool itself promotes re usability, we were able to cut down development and maintenance costs by good %.
• More than cost savings, out no technical folks started building automated tests based on user flows very easily.

Incentivized