R
ReviewerVerified
1 month ago
BrowserStack covers our QA needs across Chrome, Safari and Edge plus a good spread of Android devices, and the Selenium integration slotted into our pipeline cleanly. Screenshots across browsers help us catch visual regressions quickly. The dashboard could be a little snappier, but it does the job well.
Clean Selenium integration, broad coverage
Dashboard could be faster
There's no question BrowserStack has the widest range of browser and device combinations I've used, and it caught layout bugs we'd never have found locally. The flip side is that for a small team the pricing is steep and parallel test seats get expensive fast. Useful, but we constantly weigh whether it's worth the spend.
Excellent device and browser matrix
Pricing is steep for small teams
We rely on BrowserStack for cross-browser automation, but lately remote sessions disconnect partway through test runs, forcing reruns and skewing our CI pipeline timing. Reproducing the exact device state afterwards is painful. When it works it's great, but the instability has cost us real hours.
Sessions disconnect during test runs
BrowserStack lets us test our web app across real browsers and actual mobile devices without buying and maintaining a single phone. The live debugging on real iOS and Android devices is a lifesaver for those bugs that only reproduce on specific versions. My only gripe is that sessions can feel a touch laggy on slower connections.
Huge real-device coverage, live debugging
Sessions lag on slow connections
The idea of testing on genuine devices through BrowserStack is exactly what we needed, but in practice spinning up a real device session often takes ages and occasionally times out. For quick exploratory checks that delay really breaks the flow. Good concept, disappointing day-to-day responsiveness.
Slow device session startup and timeouts