BrowserStack
BrowserStackExternal reviews
3,231 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Streamlined Automation Testing with Intuitive Interface
What do you like best about the product?
I find BrowserStack incredibly user-friendly with its interface that allows easy access to devices and user permissions, as well as single-click reporting. It's great that I can manage costs and licenses with ease using the RBAC feature. The single-window reporting of automation is efficient and saves me from the hassle of installing multiple software. I also appreciate how smooth the self-learning curve is with BrowserStack.
What do you dislike about the product?
We can introduce self-heal approaches to make AI flavored software. Like automate the pipeline and analyze results. Then some agents run and fix those bugs and notify it is working to save time.
What problems is the product solving and how is that benefiting you?
I use BrowserStack for complete automation, reducing device costs and ensuring compatibility without needing additional infrastructure. It allows easy device access, one-click reporting, and smooth self-learning. Role-based access control simplifies permission management, and single-window reporting eliminates the need for multiple software installations.
Eliminated Our Device Lab with Instant Access to Devices, Browsers and OSs
What do you like best about the product?
It completely killed our device lab. No more keeping old version of phone, browsers and OS to test and reproduce bugs. Also, we have access to more devices and operative systems that I can access in seconds.
The local testing is fantastic. Being able to securely tunnel my localhost directly to an device environment accelerates the development and catches many quirks early.
The local testing is fantastic. Being able to securely tunnel my localhost directly to an device environment accelerates the development and catches many quirks early.
What do you dislike about the product?
The biggest annoyance is the latency. The input lag between clicking and the screen actually updating can be frustrating. It makes debugging fast UI animations painful.
What problems is the product solving and how is that benefiting you?
BrowserStack basically solves the absolute nightmare of device and browser fragmentation. Trying to ensure a web app works perfectly across every single iPhone, random Android, and obscure Windows browser version is incredibly tedious. It completely eliminates the need for us to buy and maintain a physical "device lab" at the office.
For me personally, the biggest benefit is how much faster I can debug. Thanks to their local testing tunnel, I can test my localhost code on a real, cloud-hosted device or browser before I even open a PR. I don’t have to push to staging just to reproduce a weird Safari-only bug.
For me personally, the biggest benefit is how much faster I can debug. Thanks to their local testing tunnel, I can test my localhost code on a real, cloud-hosted device or browser before I even open a PR. I don’t have to push to staging just to reproduce a weird Safari-only bug.
Fast, Reliable Cross-Browser and Real Device Testing Made Easy
What do you like best about the product?
Easy cross-browser and real device testing with fast and reliable performance.
What do you dislike about the product?
Can be slow at times, and pricing is on the higher side.
What problems is the product solving and how is that benefiting you?
Solves cross-browser and device compatibility issues, ensuring consistent performance across platforms.
Reliable Cross-Browser Testing Made Easy
What do you like best about the product?
We use BrowserStack for cross-browser testing and debugging. BrowserStack has been a reliable tool for testing across multiple browsers and devices without the hassle of maintaining physical infrastructure. The platform makes it easy to validate and understand how our sites perform in different environments. It significantly speeds up the QA process. Setting up BrowserStack was easy for our team, and we adapted quickly. Everything is good for us, and we don't feel any challenges using BrowserStack.
What do you dislike about the product?
There are occasional performance lags during peak usage, improving session stability might resolve this problem.
What problems is the product solving and how is that benefiting you?
I use BrowserStack for cross-browser testing and debugging, making it easy to validate applications across multiple browsers and devices without maintaining physical infrastructure, significantly speeding up the QA process.
Excellent Coverage of Device and Browser Combinations
What do you like best about the product?
Access to lots of device and browser coombinations
What do you dislike about the product?
Sometimes it’s hard to press the buttons on mobile.
What problems is the product solving and how is that benefiting you?
It gives us access to devices we simply don’t have on hand for testing. Safari testing is essential, so being able to use iPhones and iPads is crucial when carrying out QA.
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.
showing 381 - 390