BrowserStack MCP Server
BrowserStackReviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
3,286 reviews
from
External reviews are not included in the AWS star rating for the product.
Instant Access to Real Devices Without the Hardware Hassle
What do you like best about the product?
Honestly, the best part is just not having to manage a drawer full of physical devices. I can jump into a real iPhone or an obscure Android version in seconds. The latency is low enough that it actually feels like you're using the device, which is a lifesaver for quick CSS fixes.
What do you dislike about the product?
It can be quite expensive for smaller teams. Also, the performance isn't always 1:1 with a local device—scrolling and animations can feel a bit choppy sometimes depending on the connection.
What problems is the product solving and how is that benefiting you?
It solves the massive headache of device fragmentation. We can't realistically buy every iPhone and Android model that comes out, let alone maintain them. BrowserStack gives us instant access to a huge cloud of real hardware, which means we can ship features confidently knowing they actually work on a customer’s specific phone, not just a simulator.
Intuitive Cross-Browser Testing with Some Lag
What do you like best about the product?
I like how BrowserStack makes testing easy by allowing me to spin up a new device seamlessly. The user experience is straightforward, making it easy for anyone to adapt. The intuitive interface allows me to switch from portrait to landscape quickly with just one click. I also appreciate that BrowserStack offers more features compared to the previous product I used, LambdaTest.
What do you dislike about the product?
Performance lag, pricing concerns, and session startup. The stream feels quite laggy during peak usage hours.
What problems is the product solving and how is that benefiting you?
I use BrowserStack for testing on actual devices, making it easy to check issues on specific models like Pixel 8. The seamless user experience and intuitive interface make switching modes and setting up new devices effortless.
Clean, User-Friendly UI
What do you like best about the product?
What I like most is how easy it is to implement, along with the wide variety of features it offers.
What do you dislike about the product?
It could use more features, and the customer support could be better.
What problems is the product solving and how is that benefiting you?
help us eliminate the need to maintain a large in house device lab by providing instant access to real devices and browsers
BrowserStack Makes Real Cross-Browser Testing Easy with Seamless CI/CD Integrations
What do you like best about the product?
Cross-browser and cross-device testing is a major strength: it gives access to a huge range of real browsers, operating systems, and devices without needing to maintain your own device lab, and that’s probably its biggest draw.
The real device cloud is another standout. Unlike emulators or simulators, BrowserStack offers testing on real devices, which leads to more accurate results and a better sense of how apps behave in the wild.
Its integration ecosystem is also solid. It integrates well with CI/CD pipelines and popular tools like Selenium, Cypress, Playwright, Jenkins, and others, so it’s easy to plug into existing workflows.
On top of that, it supports both live and automated testing. You can do interactive manual testing (Live) as well as automated test execution (Automate), which helps cover different testing needs.
Finally, the cloud-based setup adds a lot of accessibility and convenience, since teams can test from anywhere without the infrastructure overhead.
The real device cloud is another standout. Unlike emulators or simulators, BrowserStack offers testing on real devices, which leads to more accurate results and a better sense of how apps behave in the wild.
Its integration ecosystem is also solid. It integrates well with CI/CD pipelines and popular tools like Selenium, Cypress, Playwright, Jenkins, and others, so it’s easy to plug into existing workflows.
On top of that, it supports both live and automated testing. You can do interactive manual testing (Live) as well as automated test execution (Automate), which helps cover different testing needs.
Finally, the cloud-based setup adds a lot of accessibility and convenience, since teams can test from anywhere without the infrastructure overhead.
What do you dislike about the product?
Performance and latency: Live testing sessions can feel sluggish, especially when you’re working with remote devices. There’s often noticeable lag during interactions, which can slow down manual testing workflows.
Pricing: It’s one of the more expensive options in the space. The tiered pricing model can add up quickly, particularly for smaller teams or startups that need access to multiple products (Live, Automate, App Live, etc.).
Session stability: Some users report sessions dropping or timing out unexpectedly, which is especially frustrating during longer testing runs.
Limited device customization: Because you’re using shared cloud devices, there can be restrictions on what you can install or configure. As a result, it may not fully replicate a real user’s environment.
Queue times: During peak usage, there can be wait times to access popular device/browser combinations, which can slow down CI pipelines.
Learning curve for advanced features: While basic usage is straightforward, getting the most out of features like Percy (visual testing) or test observability tools can take some ramp-up time.
Debugging limitations: Troubleshooting failures on remote devices can sometimes be harder than working locally, even with the tools BrowserStack provides.
Pricing: It’s one of the more expensive options in the space. The tiered pricing model can add up quickly, particularly for smaller teams or startups that need access to multiple products (Live, Automate, App Live, etc.).
Session stability: Some users report sessions dropping or timing out unexpectedly, which is especially frustrating during longer testing runs.
Limited device customization: Because you’re using shared cloud devices, there can be restrictions on what you can install or configure. As a result, it may not fully replicate a real user’s environment.
Queue times: During peak usage, there can be wait times to access popular device/browser combinations, which can slow down CI pipelines.
Learning curve for advanced features: While basic usage is straightforward, getting the most out of features like Percy (visual testing) or test observability tools can take some ramp-up time.
Debugging limitations: Troubleshooting failures on remote devices can sometimes be harder than working locally, even with the tools BrowserStack provides.
What problems is the product solving and how is that benefiting you?
Device and browser fragmentation is a real challenge—the web and mobile ecosystem is incredibly fragmented, with thousands of combinations of browsers, browser versions, operating systems, and devices. Maintaining a physical lab to cover even a fraction of these combinations is expensive and impractical. BrowserStack addresses this by providing on-demand cloud access to a wide range of real devices and browsers.
Testing infrastructure overhead is another major pain point. Setting up and maintaining Selenium grids, device farms, and test environments can take significant engineering time and ongoing effort. BrowserStack abstracts much of that work away, so teams can focus on writing, running, and improving tests instead of managing infrastructure.
Slow release cycles are often the result of unreliable cross-browser and cross-device coverage. Without dependable testing, teams either ship with uncertainty or slow down releases to test manually. BrowserStack helps teams release faster and with more confidence by making comprehensive testing easier to integrate into CI/CD pipelines.
Geographic and team distribution also matters. When teams are distributed, everyone still needs access to the same testing environments, and a cloud platform makes that possible without shipping hardware around.
In practice, this translates into faster time to market, fewer bugs reaching production, reduced infrastructure costs compared to maintaining a device lab, and greater confidence that the product works across the environments users actually rely on.
Testing infrastructure overhead is another major pain point. Setting up and maintaining Selenium grids, device farms, and test environments can take significant engineering time and ongoing effort. BrowserStack abstracts much of that work away, so teams can focus on writing, running, and improving tests instead of managing infrastructure.
Slow release cycles are often the result of unreliable cross-browser and cross-device coverage. Without dependable testing, teams either ship with uncertainty or slow down releases to test manually. BrowserStack helps teams release faster and with more confidence by making comprehensive testing easier to integrate into CI/CD pipelines.
Geographic and team distribution also matters. When teams are distributed, everyone still needs access to the same testing environments, and a cloud platform makes that possible without shipping hardware around.
In practice, this translates into faster time to market, fewer bugs reaching production, reduced infrastructure costs compared to maintaining a device lab, and greater confidence that the product works across the environments users actually rely on.
Buffer-Free Execution Videos Make Debugging and Test Management Important Feedbacks
What do you like best about the product?
It’s easy for me to debug my automation failures because it records a buffer-free video of my automation execution. I use the test management feature, which helps me track bugs and execute cases easily. The test management tool also helps me configure my cases according to different platforms, and even adjust the same cases based on the platform requirements.
Migrating our manual cases is also very easy, which reduces the effort of writing cases again when they’re already present. I use test runs frequently, as I execute manual execution through BrowserStack. The customer support team also tries to provide the best solution possible.
Migrating our manual cases is also very easy, which reduces the effort of writing cases again when they’re already present. I use test runs frequently, as I execute manual execution through BrowserStack. The customer support team also tries to provide the best solution possible.
What do you dislike about the product?
- Integrating jira with our project for each user separately
- existing bugs in test management tool
- iframe of browserstack in the jira tool
- Bug raising to jira through browserstack
- existing bugs in test management tool
- iframe of browserstack in the jira tool
- Bug raising to jira through browserstack
What problems is the product solving and how is that benefiting you?
Earlier, our team used Google Sheets for manual test case execution, which came with a few drawbacks: we couldn’t easily track execution history, we had limited visibility into overall progress, and assigning different cases to different team members was not very smooth. Now, with the BrowserStack test management tool, we have configurations that make it feasible to assign different cases to different people, and we can also see the edit history of test case execution.
Another major improvement is around bug reporting. With Google Sheets-based execution, we had to raise bugs directly in Jira and then later map them back to the relevant cases again. With BrowserStack, Jira issues can be raised from the same tool, which saves significant time.
That said, I do have a few pieces of feedback from a QA perspective that I feel should be improved, since they are frequent, time-consuming areas and currently feel like gaps in an end-to-end QA execution journey.
Another major improvement is around bug reporting. With Google Sheets-based execution, we had to raise bugs directly in Jira and then later map them back to the relevant cases again. With BrowserStack, Jira issues can be raised from the same tool, which saves significant time.
That said, I do have a few pieces of feedback from a QA perspective that I feel should be improved, since they are frequent, time-consuming areas and currently feel like gaps in an end-to-end QA execution journey.
Fast, Reliable Cross-Browser Testing with Instant Real Device Access
What do you like best about the product?
BrowserStack makes cross-browser testing simple by giving instant access to real devices and browsers without setup. It’s fast, reliable, and easy to use, which saves a lot of time
What do you dislike about the product?
The visual quality of the website could be improved, especially on Mac, as it sometimes doesn’t appear as sharp or high-definition as expected.
What problems is the product solving and how is that benefiting you?
BrowserStack helps solve cross-browser testing issues by providing easy access to different environments. I initially faced a problem accessing browser testing on Mac, but their support team guided me step by step to resolve it. This helped me quickly get back on track and continue testing without delays.
Great for Cross-Browser & Mobile Testing
What do you like best about the product?
Great for cross-browser & mobile testing
What do you dislike about the product?
None of what I can think of, so far I like
What problems is the product solving and how is that benefiting you?
Catching early UI issues for our projects
Excellent Cross-Browser & Device Testing Experience
What do you like best about the product?
Cross browser testing and different devices emulators provided.
Test management is also better.
Test management is also better.
What do you dislike about the product?
Can provide more time for free plan to explore.
What problems is the product solving and how is that benefiting you?
Cross browser testing.
Test Management tool.
Test Management tool.
Essential for Comprehensive Browser Testing
What do you like best about the product?
I use BrowserStack for frontend testing and appreciate that it lets me test across different browsers and devices without needing to set them up locally, which helps me quickly catch compatibility issues. I like how easy it is to test across many devices and browser versions without much effort, making debugging ten times easier. I would say the initial setup was pretty straightforward and easy, and there's a lot of information available online about working with BrowserStack, making it much easier to set up and use. It's my go-to platform for different browser and mobile testing.
What do you dislike about the product?
One thing that didn't work well for me is the country selection during local testing and would like to see a solution for that.
What problems is the product solving and how is that benefiting you?
BrowserStack allows me to test my frontend across different browsers and devices without setting them up locally, helping me quickly catch compatibility issues.
Fast, Real-Device Testing That Simplifies QA
What do you like best about the product?
BrowserStack is most helpful for quickly testing across a wide range of real devices and browsers without needing to maintain that hardware internally. It saves time, makes cross-platform QA much easier, and helps us catch device-specific issues earlier in the development process. It is especially useful for verifying behavior on different OS and browser combinations in one place.
What do you dislike about the product?
Overall it is very useful, but performance and session setup speed is a bit slow compared to testing locally, however I'm not sure if anything can be done at this point.
What problems is the product solving and how is that benefiting you?
BrowserStack solves the problem of needing access to many different real devices and browser versions for testing. That benefits us by reducing the need to maintain a large internal device lab, making testing more scalable, and helping us identify compatibility issues before release. The variety of devices I can run tests on is one of the biggest advantages for our workflow.
showing 451 - 460