JMeter, from Apache, is a load and performance testing tool.
N/A
OpenText UFT Digital Lab
Score 9.0 out of 10
N/A
Formerly from Micro Focus, a centralized lab of real mobile devices and emulators. With remote access, developers and testers can develop, debug, test, monitor, and optimize mobile apps from anywhere.
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.
UFT mobile works really well if/when you need physical devices under your management. Managing physical devices in any setup is an interesting undertaking due to the various considerations per device. There are really nice best practices, for example using managed USB switches like the one from Cambrionix, that can help make for a really good experience. For us, we only have 1 application at this time that has frequent updates/releases. We are able to test out these with confidence using our suite of real/on-campus devices managed and made available by the UFT Mobile product.
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.
Remote access to real devices within your organization network as compared to public devices library offering, where their is a risk of exposing pre-production builds outside the organization.
"Factory built like" integration with HP ALM, HP Sprinter, HP UFT and HP Network Virtualization.
Ability to mimic real world conditions in a controlled environment in the devices of your choice.
Removed the guess work out of using emulators
Able to extend automation to mobile testing using HP UFT.
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 tool continues to meet our expectations and has shown that they are continually evolving the product with new features that benefit us. The most recent new feature was the auto-signing/packaging of iOS apps from the server to allow native interaction of features like biometrics. Prior this was a lengthy exercise.
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.
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.
HP Mobile Center stacks well against solutions like Mobile Labs Device Connect, Perfecto Mobile and Device Anywhere. Its native integration with HP ALM and HP UFT makes it a clear choice for team already using those solutions. HP Mobile Center also provides extension to Amazon Device Library.
