Apache JMeter vs. BrowserStack

The key questions I would pose are: how high of a concurrent load do you need to generate against the system? How technically skilled are your personnel that will perform the load testing? How much programmable/scripting/code based control do you desire from the tool? Do you prefer more of a GUI based tool or a programmatic code/scripting based tool? JMeter will be for those that want a GUI, moderate to low scripting/code based control/programmability, moderate to low load generation, and for users experienced in the novice to expert range.

Multiple real devices available for testing across different OS, platform and browsers for both website and mobile application testing. Automate help to integrate existing project and testing suite to run across different devices. This reduce testing timeline and allow us to quickly release new features to users. Also provide automated accessibility report.

Incentivized

• Easy to construct Webservices script - You just need to add a sampler with the endpoint, payload and header information. And boom you can run a load test on the service with varying load and capture the response time and throughput. In a commercial tool like Loadrunner or Silkperformer, this process would take at least couple of hours, while with Jmeter we can do this in 10 minutes or less.
• Modularizing the scripts - Jmeter has a very good way of organizing the scripts and the reusability of the existing script (transactions) is also as easy as copy pasting the script.
• Jmeter tests can be run from anywhere, so you can run it from the idle webserver itself if you have some firewall restrictions to test it from your local or other environment.
• Jmeter distributed tests can be spawn from the AWS and results collated to see the performance from different regions in the world.

• UI testing on different Devices like iOS, Android, MacOS, and Windows OS.
• Automation testing with the help of Cypress gives automation access to different OS and devices.
• Comparison with two devices how UI will look a like.
• Bug Capture tool: Using this tool, a user can capture a bug while live recording it, and the tool captures action as well. This helps developers identify and fix the bug more easily.

• Even though it has very easy installation, you can run into issues easily. I was ab;e to trigger a test at browser level but couldn't stop the tests. I had to kill it from task manager and then had to reinstall from begining.
• There are so many things in JMeter you can do especially with the sampler for selenium for UI tests. More documentation/webinars etc.. would help the community better.
• The jmx files should have an easy way to be integrated with ci/cd tools and cloud.

Incentivized

• I wish it didn't time out so quickly. I often move back and forth between my native Mac OS system and browsers to BrowserStack for Windows browsers and it often times out so I have to start over.
• I am not sure why, but when I've been testing in BrowserStack for a long period of time - maybe over a couple of hours, it sometimes gets buggy and unresponsive or slow to respond. It makes it hard to tell if I'm experiencing an issue with the site I'm testing or if it's an issue with BrowserStack.
• If I'm wishing for the moon and stars, I'd ask for the ability to use BrowserStack to also test with JAWS screen reader. But I'm happy having NVDA.

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

It's simply a must-have tool. As a designer, I have to ensure my work is at least functional in older browsers. I also have to ensure that, when I design for mobile devices, any differences between platforms aren't problematic. BrowserStack allows me to test my work in a fraction of the time, with a whole lot more accuracy.

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.

It integrates directly in internal networks and local development. The point and click interface of choosing your device, pick the browser/version and you have a working emulation of that exact environment. What else could you ask for? I've set our least computer savvy users up with BrowserStack for testing in minutes. It feels like it's just part of your local environemnt.

Incentivized

I rated BrowserStack's availability a 10 because it is consistently reliable, with minimal to no downtime or unplanned outages. The platform is accessible whenever needed, ensuring uninterrupted testing. Its robust infrastructure and proactive monitoring ensure a seamless experience, allowing us to meet deadlines without delays caused by availability issues and all

The tests are fast considering the fact that they're Appium tests. I've seen tests reliably pass or fail when they're supposed to, with next to zero issues on the BrowserStack side of things. Tests launch only seconds after I kick off them off from my CLI.

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

I'm saying a 10 for support for BrowserStack only based on feedback from the development team. I myself have never had to reach out to support for any questions or issues, but others in the company have. From my conversations with them, the support was fantastic and had been a pleasure working with the BrowserStack team.

Incentivized

Yes, it was online training on meet, and trainer looks like skilled and technical strong, he has covered end to end all the features and he has answers all the queries. because of this trainings we are able to implement it by our own in the organization, thank you for support and training.

Incentivized

It was a quick training from the support of browserstack, it was nice and easy to understand, thanks again for the support given by the team. and regularly I used to receive mails for training from support for any new feature they launch, I was able to spread same training to all my team and dev.

Incentivized

I rated the implementation satisfaction an 8 because while it went smoothly overall, there were some challenges during the initial learning phase and integration with existing tools. Key insights include the importance of providing sufficient training upfront and ensuring seamless integration with other systems to minimize disruptions and improve adoption speed.

I have evaluated LOADUI (web free version) and it was a very unstable tool and I could not rely on those results completely as I was not sure how the tool was performing. It only generated the top 10 less transaction times and when Jmeter was in use, it was very effective in using plugins to accommodate more outputs.

Incentivized

N/A - BrowserStack was the first software I've tried to address these requirements. Previously we've been limited to testing on a handful of devices and browser combinations that our team has physical access to. We're also evaluating Litmus as a complementary service to BrowserStack for analysing our email templates and deliverability.

Incentivized

I may not be the best person to answer this as I am only using it for 1 department and at 1 site but will still try my best As far as Scalability for Devices for Mobile Automation is concerned, it gets a Solid 10, as the users can run cases on upto 10 device parallel and also have the best choices of devices to choose

Incentivized

• It helped to estimate resources required for a particular client requirement. For example if the client wants the application to be used by 500 users for 1 hour, based on the load test we perform for 500 users and 1 hour we recommend resources and their capabilities.
• Jmeter was used to identify bottleneck. This would lead to better performance.
• Jmeter was used to identify failures as well.

• It reduced the cost of buying multiple devices as we have multiple devices access in it
• Easily accessible from anywhere due to it cloud availability
• Introducing this to our client also helped us in building trust as well as winning their confidence during deliverables

Incentivized