Apache JMeter vs. LambdaTest

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

One day, I needed to test a specific issue that was occurring only on Pixel phones. I turned to LambdaTest, quickly identified the problem, and was able to fix it. There hasn't been a situation where I felt LambdaTest didn't help, it's my go-to solution for testing, as it solves many problems.

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.

• Very accessible as multiple users can be added in each subscription
• Very reliable as it is very close to the actual device when it comes to operating system and version behavior
• There are a lot of options for devices and browsers that users can choose from when it comes to emulating and testing

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

• More real devices should be added like I have Samsung mobile but it was not in the list
• It takes time in checking the link on LambdaTest if we compare with real mobiles
• Sometimes exact results are not matching as from real mobiles

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 reason i have given the 10 points becasue the problem LambdaTest solves is providing access to all devices in one place, allowing developers to identify the same errors they would encounter on real devices. This makes life much easier, especially for developers who regularly face cross-device functionality issues. It's a big plus point that positions LambdaTest as an all-in-one solution.

Incentivized

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.

Incentivized

Because of the ease of use of the platform, we just save a lot of time and effort with this as its a feature rich solution, we just need to upload app binary once and for everytime we need to test on a different device we can just directly install that binary on the device without the pain of reupload.

yes always available

Incentivized

haven't found any glitch while using this

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

The customer support team is very active and cooperative. Once, I contacted them in their off timings because of an issue, I got an instant reply from the executive and he resolved the issue very efficiently. This is why we have been using LambdaTest for more than two years. It is best suited for us.

Implementation of Lambdatest was very easy for different project requirements.

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.

While BrowserStack is also a well-established platform, we found LambdaTest to offer similar and even better features at reasonable pricing. LambdaTest is more cost-effective than BrowserStack. LambdaTest provides a free forever plan, while BrowserStack does not. Even manual testing plans are better priced than BrowserStack’s. In terms of UI and onboarding, we found LambdaTest more user-friendly as well.

not all department, but we're using for our clients

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

• Automation testing has a bit of a learning curve
• Lack of real device keep that bug in your head if not on the website.
• Need to wait for a while for a new OS or browser version on the contrary of immediate availability in case of owning a lab