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.
Blue Prism Cloud is an ideal cloud automation solution for organizations with a significant number of remote workers or geographically disparate teams since its accessible from any web browser. It is also beneficial for organizations that need to quickly outsource part of their process automation without having to purchase additional software licenses and equipment.
However, Blue Prism Cloud is less suited for companies that have large volume data processing needs as its base cost may quickly become prohibitive in those situations. Additionally, this solution may not be suitable for organizations that need more complex solution-specific configurations since its integration options are limited.
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.
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.
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
The purpose related to performance and load testing through Apache JMeter works fine but the usability of the tool should be improved quite a lot. If someone starts with the Jmeter fresh without prior experience, they need to put more efforts in understanding the tool. The UI is not that great which is the main reason not to give high rating on usability.
Usability wise the Blue Prism tool can be utilized to its 100% which include the control room, schedulers, work queues, Release managers, studio for process and object development, we use all the features in blue prism and is well suitable for the development and deployment, All the system are wisely controlled and connected the same SQL database and all the data can be accessed with ease and all the things can achieve in the systematic order.
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.
Support is good and now with time online support in other forums is becoming available as well. Blue Prism support in itself is also good. Documents and blogs can help to find the solution. Since it's relatively new, sometimes if I'm stuck it can take time to find the solution or connect to their team.
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.
Better User Interface.Better customer service.Easier to learn and use. But has greater risk compliances. Less preloaded automation. Less editing features and a big no while working on big projects. Fluidmesh is better in pricing and better management of multiple projects but I believe Blue Prism is perfect for beginners and small-scale companies.
For a level of medium projects, Blue Prism performs well, and the speed of execution is good. In our organization, we are applying for medium projects, where we can increase the workforce of our employees.
Blue Prism's Client Server Architecture is good, because we need such a feature to implement automation.
When it comes to pricing, I personally feel that it is costlier.
