BrowserStack MCP Server
BrowserStackReviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
3,219 reviews
from
External reviews are not included in the AWS star rating for the product.
Streamlined Testing with Intelligent Automation
What do you like best about the product?
I use BrowserStack to test our mobile app and website functionality. It helps us by allowing automated tests, which cuts down the time required by QA team members to run tests. I particularly like the benchmark/threshold marking feature, which alerts us if there are regular errors or issues with stability while ignoring expected failures in certain areas. It's quite intelligent in that way. The initial setup was really simple, and the trial period was useful.
What do you dislike about the product?
The management interface can be a bit sluggish. For mobile app testing certain model phones are only unlocked with more expensive plans.
What problems is the product solving and how is that benefiting you?
I use BrowserStack to test our app and website functionality, automating tests to cut down QA time. The benchmark feature helps by alerting us to unexpected issues while ignoring expected failures.
BrowserStack Makes Cross-Browser Testing Fast and Scalable
What do you like best about the product?
What I like most about BrowserStack is how it simplifies cross-browser and cross-device testing without requiring me to maintain physical devices. It offers a smooth, reliable way to test applications across a broad range of real devices and browsers, which saves a lot of time and effort. I also find it especially useful for catching compatibility issues early in the development cycle. On top of that, its integration with automation tools improves efficiency and makes it easier to scale testing for real-world projects.
What do you dislike about the product?
Latency during real-device testing can become a real bottleneck in fast-paced sprints. On top of that, the entry-level pricing feels quite steep for startups, and the automatic session timeouts can be disruptive—especially when I’m trying to debug more complex issues.
What problems is the product solving and how is that benefiting you?
It removes the huge overhead of maintaining an internal device lab. With BrowserStack, we can quickly verify cross-platform UI consistency, which has noticeably sped up our QA cycles.
Flagship Real Device Testing Made Easy with Reliable Network Simulation
What do you like best about the product?
Real device testing on the latest flagships (Galaxy S26 Ultra, iPhone 17 Pro) without having to maintain a physical device lab. The network simulation API lets us reliably test offline scenarios, and the debug mode plus network logs make it much easier to diagnose flaky tests. Jenkins CI integration is straightforward—our pipeline automatically spins up test instances on BrowserStack and runs our test suites end to end.
What do you dislike about the product?
You’d know this best—are there any pain points you’ve run into? For example: slow queuing, flaky sessions, pricing concerns, or issues with the dashboard UX?
What problems is the product solving and how is that benefiting you?
BrowserStack helps us test our mobile app on real iOS and Android devices without having to maintain a physical device lab. We can run E2E tests on the latest flagships (iPhone 17 Pro, Samsung Galaxy S26 Ultra), which would otherwise be expensive and time-consuming to manage in-house.
The key problems it solves for us are device availability and coverage. We get instant access to real devices running the latest OS versions (Android 16, iOS 26) without the procurement, setup, or ongoing maintenance overhead. It also improves cross-platform parity: we run the same Appium/WebdriverIO test suites on both platforms, which helps us confirm consistent behavior across Android and iOS.
Network condition testing is another big win. BrowserStack's network simulation API lets us reliably test offline/online scenarios, which is critical for our field-use mobile app. On the CI/CD side, our Jenkins pipeline triggers BrowserStack test runs automatically, so we get continuous feedback without tying up local infrastructure.
Finally, debugging in the cloud is genuinely useful. The built-in debug mode and network logs make it much easier to diagnose failures on remote devices, almost as if they were local. Overall, the main benefit is speed and confidence: we can validate every build on real devices in CI without maintaining any hardware.
The key problems it solves for us are device availability and coverage. We get instant access to real devices running the latest OS versions (Android 16, iOS 26) without the procurement, setup, or ongoing maintenance overhead. It also improves cross-platform parity: we run the same Appium/WebdriverIO test suites on both platforms, which helps us confirm consistent behavior across Android and iOS.
Network condition testing is another big win. BrowserStack's network simulation API lets us reliably test offline/online scenarios, which is critical for our field-use mobile app. On the CI/CD side, our Jenkins pipeline triggers BrowserStack test runs automatically, so we get continuous feedback without tying up local infrastructure.
Finally, debugging in the cloud is genuinely useful. The built-in debug mode and network logs make it much easier to diagnose failures on remote devices, almost as if they were local. Overall, the main benefit is speed and confidence: we can validate every build on real devices in CI without maintaining any hardware.
Essential for Comprehensive Cross-Platform Testing
What do you like best about the product?
I love that BrowserStack offers many devices to test on, which is crucial for when I lack real device support. The ability to rotate the device is handy, and the logging functionality is very useful. I also appreciate that I can use tablets in addition to regular mobile devices. These features significantly boost my testing activities as a QA at work.
What do you dislike about the product?
More devices, especially, not that popular. e.g., Amazon Fire tablets. As I mentioned, Amazon Fire tablets. Maybe also smart watches.
What problems is the product solving and how is that benefiting you?
I use BrowserStack for cross-platform testing, allowing me to test web apps on various devices and OS versions, enhancing my testing coverage for UI and cross-browser/platform scenarios.
Effortless Cross-Platform Testing
What do you like best about the product?
I use BrowserStack to test web and mobile applications on multiple browsers and devices without needing to have them physically, which speeds up the work. It allows me to detect compatibility errors, saving time and testing resources. I especially enjoy the speed of cloud testing and the ease of integration with automation tools. This saves time in testing and allows for delivering more reliable applications without having to set up multiple physical devices. The initial setup was simple.
What do you dislike about the product?
Some tests can be slow on specific devices and the interface could be more intuitive for beginners. Some advanced integrations required help from support. The interface could be improved in some sections.
What problems is the product solving and how is that benefiting you?
I use BrowserStack to test applications on various browsers and devices without having them physically, which detects compatibility errors, saves time and resources, and allows for delivering more reliable applications.
Essential tool for app testing.
What do you like best about the product?
Reliable real-device testing : Testing on actual devices gives much more accurate results compared to emulators, especially for performance and user interaction.
Execellent device and OS coverage : It's easy to test across multiple devices type and OS versions without maintaining physical hardware.
Smooth CI/CD integration: Integrates well into existing workflows, making automated testing and faster release much easier.
Efficient debugging experience: Quickly reproducing issues on specific devices helps save time and improves overall productivity.
Execellent device and OS coverage : It's easy to test across multiple devices type and OS versions without maintaining physical hardware.
Smooth CI/CD integration: Integrates well into existing workflows, making automated testing and faster release much easier.
Efficient debugging experience: Quickly reproducing issues on specific devices helps save time and improves overall productivity.
What do you dislike about the product?
- Sometimes performance can feel a bit slow.
- Pricing is slightly expensive for smaller teams.
- Session time limits can interrupt longer tests.
- Occasional connectivity or responsiveness issues.
- Pricing is slightly expensive for smaller teams.
- Session time limits can interrupt longer tests.
- Occasional connectivity or responsiveness issues.
What problems is the product solving and how is that benefiting you?
Browserstack solves the problem of testing applications across multiple devices and OS versions without needing to maintain a physical device lab. It makes it easy to access real devices anytime and run tests in different environments.
This benifits me by saving time, reducing infrastructure overhead and helping catch issues early. It also make debugging faster and ensures better app quality before release.
This benifits me by saving time, reducing infrastructure overhead and helping catch issues early. It also make debugging faster and ensures better app quality before release.
Essential for Efficient Cross-Browser Testing
What do you like best about the product?
I love using BrowserStack for manual QA testing across multiple client web projects. It lets me validate functionality, responsive design, and visual consistency across various real browsers, operating systems, and mobile devices without needing a physical device lab. This is especially helpful for comparing Figma designs against production builds and documenting cross-browser bugs for client reports. BrowserStack solves several critical pain points in my QA workflow, including eliminating the need for a physical device lab, catching bugs exclusive to certain environments, speeding up bug reproduction and verification, improving bug report quality, and enabling thorough responsive testing. What I like most is the combination of real device access and speed, allowing me to instantly launch devices like iPhone, Samsung, or MacBook without setup. Additionally, I really appreciate BrowserStack’s seamless session start-up, local testing support, native devtools integration, and the clean, intuitive interface. Each of these features directly solves a real problem in my daily QA work and together they transform how efficiently and professionally I can deliver results to clients. The initial setup was remarkably easy, one of the smoothest onboarding experiences I’ve had with any professional QA tool.
What do you dislike about the product?
While BrowserStack is an excellent platform overall, there are a few areas where I think the experience could be even better: Session time limits can feel restrictive; Copy-paste between local machine and remote device; File upload testing on mobile devices; screenshot annotation tools; mobile device availability during peak hours.
What problems is the product solving and how is that benefiting you?
I use BrowserStack for manual QA testing, eliminating the need for a physical device lab, catching environment-specific bugs, improving bug reports, speeding up bug verification, and enabling thorough responsive testing.
Ease of Use with Pricing Challenges
What do you like best about the product?
I like BrowserStack for its ease of use. It automates tests across devices and helps in manual testing by handling the hurdle of buying devices.
What do you dislike about the product?
The pricing of BrowserStack is something that could be improved. Also, while the initial setup was generally easy, I found the process of registering and confirming the email to be a bit of a hurdle.
What problems is the product solving and how is that benefiting you?
I use BrowserStack to automate tests across devices, solving the manual testing challenge and overcoming the hurdle of buying devices.
Easy and Intuitive with a Powerful Visualization
What do you like best about the product?
I definitely like the ease of use of BrowserStack, its intuitiveness, and how it displays the tests. I also appreciate how it integrates with AI, which makes the work much easier, requiring less time to write accurate test descriptions, saving valuable time. I find that the initial setup was very simple and intuitive, 100 percent.
What do you dislike about the product?
high prices and costly scalability
What problems is the product solving and how is that benefiting you?
We use BrowserStack to keep track of functional tests with user stories. It helps me organize and understand which tests have passed, have not passed, or need to be redone. It is intuitive, easy to use, and saves me valuable time.
Reliable Cross-Device Testing with Real User Simulation
What do you like best about the product?
What I like most about BrowserStack is how easy it makes real device testing without actually needing to maintain a physical device lab. In our day-to-day work, we have to verify features across different browsers, OS versions, and devices, and doing that manually would be a nightmare.
I can quickly open a session on a specific mobile device or browser version and reproduce issues that users might be facing in different regions or environments. This has helped us catch bugs that never showed up in local testing.
Another thing I really appreciate is how smoothly it fits into our workflow. We use it not just for manual testing but also during quick validations before releases. The ability to switch between devices, test responsiveness, and even check geo-specific behavior saves a lot of time.
I can quickly open a session on a specific mobile device or browser version and reproduce issues that users might be facing in different regions or environments. This has helped us catch bugs that never showed up in local testing.
Another thing I really appreciate is how smoothly it fits into our workflow. We use it not just for manual testing but also during quick validations before releases. The ability to switch between devices, test responsiveness, and even check geo-specific behavior saves a lot of time.
What do you dislike about the product?
One thing that can be a bit frustrating with BrowserStack is the occasional lag or performance delay, especially when using real devices for a longer session. Sometimes there’s a slight input delay or slower response compared to using a physical device, which can slow down debugging a bit.
Another issue I’ve noticed is session stability. There have been times when sessions disconnect unexpectedly, and you have to restart everything. It’s not very frequent, but when you’re in the middle of testing something critical, it can break your flow.
Another issue I’ve noticed is session stability. There have been times when sessions disconnect unexpectedly, and you have to restart everything. It’s not very frequent, but when you’re in the middle of testing something critical, it can break your flow.
What problems is the product solving and how is that benefiting you?
BrowserStack is mainly solving the problem of testing across multiple devices, browsers, and environments without the need to actually maintain all of them in-house. In a real-world scenario, users are accessing the application from different devices, OS versions, and even different locations, so just testing locally is never enough.
Before using BrowserStack, it was always a challenge to ensure consistent behavior everywhere. We either had limited devices or had to rely on assumptions, which sometimes led to issues slipping into production. Now, we can quickly test on a wide range of real devices and browsers, which gives a lot more confidence before releases.
It’s also helping us catch edge cases early. For example, we’ve seen UI issues on specific mobile devices or browser versions that never showed up during local testing. Being able to reproduce those issues easily has saved a lot of back-and-forth and debugging time.
Another big benefit is around geo-based testing. Since we support users from different regions, BrowserStack allows us to validate location-specific behavior without setting up complex environments. That’s been really useful for us.
Before using BrowserStack, it was always a challenge to ensure consistent behavior everywhere. We either had limited devices or had to rely on assumptions, which sometimes led to issues slipping into production. Now, we can quickly test on a wide range of real devices and browsers, which gives a lot more confidence before releases.
It’s also helping us catch edge cases early. For example, we’ve seen UI issues on specific mobile devices or browser versions that never showed up during local testing. Being able to reproduce those issues easily has saved a lot of back-and-forth and debugging time.
Another big benefit is around geo-based testing. Since we support users from different regions, BrowserStack allows us to validate location-specific behavior without setting up complex environments. That’s been really useful for us.
showing 41 - 50