User-Friendly Platform with Room for Faster Device Previews
What do you like best about the product?
Intuitive, responsive platform. Easy to navigate. Lots of different devices to test on.
What do you dislike about the product?
Occasionally takes a long time to swap between device types when previewing content.
What problems is the product solving and how is that benefiting you?
I can see what my content will look like on devices I don't physically have access to, so I can see what content is responsible all screen sizes and what isn't.
Effortless Cross-Browser Testing with Seamless Automation Integration
What do you like best about the product?
It saves a lot of time because everything runs online and setup is easy. The interface is simple, and it works well with automation tools like Selenium and CI/CD pipelines. It’s very helpful for teams that need cross-browser testing. However, it can feel expensive, sometimes the sessions are slow or laggy, and device availability can be an issue during busy times. Overall, BrowserStack is a good and reliable testing platform, but the price and performance issues may not suit everyone.
What do you dislike about the product?
well nothing as of now but sometime session disconnects alot but its not usual.
What problems is the product solving and how is that benefiting you?
t removes the hassle of setting up multiple environments and saves a lot of time by providing instant access to real devices in the cloud. This helps me quickly catch cross-browser and device-specific issues, improves test coverage, and speeds up both manual and automated testing.
Effortless Parallel Testing and Seamless Integrations
What do you like best about the product?
Parallel execution actually works reliably. When we run our full suite across multiple OS-browser combinations, the time savings are huge. The integration with popular frameworks (Selenium, Appium, Playwright, Cypress) is straightforward, you don’t waste time wrestling with configs. The session dashboard is clean: logs, video, network timelines, console output - all in one place. Debugging flakiness becomes much easier. Being able to run tests on real mobile + desktop devices without maintaining hardware is a massive operational relief. Build insights (pass/fail trends, flaky test detection, failure clustering) help identify problem tests faster.
What do you dislike about the product?
Occasional device allocation delays during peak hours can slow down CI pipelines. Video playback during debugging sometimes feels slightly laggy for animation-heavy flows. Network logs are useful but could be more detailed for deep investigation. If the suite has many retries, the dashboard can get cluttered without proper naming conventions.
What problems is the product solving and how is that benefiting you?
It eliminates the need to manage Selenium grids, Appium servers, or physical device racks, zero time wasted on infra. Makes cross-platform testing scalable. We can validate the same feature across Chrome, Safari, Firefox, Edge, and multiple OS versions in parallel. Reduces investigation time dramatically because every failure comes with video, logs, screenshots, and environment details. Fits cleanly into CI pipelines, our automated suite runs on every pull request, which improves code quality before merging. Helps catch environment-specific bugs early (especially WebKit/Safari quirks and Android OEM inconsistencies). Increases release confidence because automation coverage becomes both broader and more stable.
Cross-device UI testing has improved reliability and still needs better integration with team tools
What is our primary use case?
My main use case for BrowserStack is testing different browsers and different devices such as Android, iOS, tablet, and phone, as well as Firefox and Chromium devices.
A specific example of how I use BrowserStack in my day-to-day work is whenever we create a new landing page in any of our projects. Currently, we have an agreement with an insurance company called Acris, so I use BrowserStack to test the UI elements first to see if they are appropriate for all device sizes, starting from the big screens down to the smaller screens, then the phones and tablets. After that, I start working on whether these UI elements are functioning correctly, and after the design testing is finished, I start working on the functional part.
BrowserStack provides an opportunity for testers to be able to test scenarios on a lot of different devices, which makes it valuable to use.
What is most valuable?
The best features that BrowserStack offers include the fact that, unlike Sauce Labs which I used previously and had some non-real devices, BrowserStack allows us to test on real devices, and you can see all the devices are real as you do your testing.
Using real devices on BrowserStack makes a difference for my testing compared to emulators or simulators because with emulators, sometimes it is not the real case, but I am sure of how the web element or my hook is going to work on a real device in BrowserStack.
BrowserStack has positively impacted my organization by ensuring that we don't have any surprises, especially on smaller devices. I test the UI elements first in BrowserStack, and most web applications are created by using big screen sizes, but in real life, most people are using smaller screens, so we need to be sure that everything in our application works as expected on smaller screens as well.
What needs improvement?
I need to think about how BrowserStack can be improved. If your application is more adapted to tools like Jira, Trello, or Monday, it will be more widely used by testers in my opinion.
For how long have I used the solution?
I have been using BrowserStack for more than five years.
What do I think about the stability of the solution?
What do I think about the scalability of the solution?
Whenever I find anything in BrowserStack, I tell the developer, and then the developer goes into BrowserStack. We only have one account which is shared by all the development team, and they reproduce the same scenario, and then we create the bug ticket for them to fix.
How are customer service and support?
I never used the customer support for BrowserStack. I always use it by myself since I know the crucial parts.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
In my previous company, we used Sauce Labs, and here we are using BrowserStack because it is the company's choice, not mine.
How was the initial setup?
I am not sure which cloud provider we use for BrowserStack because I did not do the setup, but in our company, we are using GCP servers, so most probably it could be Google Cloud.
What about the implementation team?
My company does not have a business relationship with this vendor other than being a customer.
What was our ROI?
I have seen fewer bug reports since using BrowserStack because I have created the bug reports by using it. We use Jira for bug reporting, and I am using it very quickly, testing first the UI part and the design to see if it fits every screen size, and also using different devices such as Windows, Android, and iOS. If I don't find anything, I give it a go and we release the product.
What's my experience with pricing, setup cost, and licensing?
I don't handle the pricing, setup cost, or licensing for BrowserStack, as I'm just using it as a tester and I don't have the permission or authority to set up or purchase licenses.
What other advice do I have?
I advise others looking into using BrowserStack to use it for cross-browser testing and multi-dimensional testing, and they can also use it for different devices because it is better than using emulators or simulators since these are real devices. My review rating for BrowserStack is seven out of ten.
Real Device Testing Made Effortless and Reliable
What do you like best about the product?
As a QA engineer, being able to test on real hardware instead of just some fake simulator is the best thing, because those simulators always lie, right? It just means when I find a bug, I know its a real bug the customer will actually hit. And the ability to fire up a test on some obscure old browser in like, two seconds? So smooth. It just makes the whole testing process way less painful.
What do you dislike about the product?
The main thing is that it can get real slow and laggy sometimes. You're trying to quickly check an animation on an old Android, but the mouse movements and screen updates are delayed, and it throws off the whole test.
What problems is the product solving and how is that benefiting you?
BrowserStack basically solves the nightmare of device fragmentation. Before this, we had to either buy a giant rack of test phones and computers, or just kinda cross our fingers that the site would not break on some obscure browser. Now, We just use BrowserStack and know for sure it works on literally everything.
Continuous cross-browser testing has reduced production defects and improves team collaboration
What is our primary use case?
The main use case for me using BrowserStack, which I have been doing for four years, is mostly around testing solutions supported for older devices and operating systems, such as iPhone 8 or iOS 12, especially for applications used by customers who do not have the most recent devices in the market and are still using Internet Explorer or earlier versions of Edge. This helps provide us devices and browsers for those legacy solutions.
When using BrowserStack for those legacy devices and browsers, the process typically involves using it for both manual and automation testing, allowing us to utilize APM as well as Selenium in both ways.
What is most valuable?
The best features BrowserStack offers for us include App Live, which has really helped us; the quick availability of real-time devices as soon as new ones are launched, such as when iPhone 17 was released; integration with project management tools including Jira and Slack, which is very handy; and access to network logs, something we have made good use of.
From a productivity standpoint, the integration with the wider ecosystem of project management tools has the biggest impact for us, specifically with Jira and Slack, as it helps us log tickets and bugs directly, providing evidence for the tickets we are logging. This was much slower before, especially when dealing with flaky applications or newly live releases that have numerous problems. The integration helps us quickly log bugs using the evidence provided by BrowserStack.
BrowserStack has positively impacted our organization by improving collaboration and showing quality improvements in releases, with the number of defects leaking into production significantly reduced.
We track two metrics: the number of bugs leaking to production per application and the number of customer support issues reported. We have seen a reduction of close to 20 to 25% in defects compared to past releases. When we started using BrowserStack, release four had about 150 bugs reported compared to 200 in release three. Incidents reported by end customers have also seen a reduction.
What needs improvement?
I think false positives are an area where BrowserStack can improve, as I have often seen things working fine on actual devices, but on BrowserStack devices, issues arise due to network slowness or AWS region connectivity problems that cause lag.
In addition to false positives and network slowness, feature improvements could include monitoring dashboards or consolidated dashboards for multiple releases across different domains, allowing us to see runs scheduled and link us to reports of passed and failed cases.
For how long have I used the solution?
I have been using BrowserStack for a total period of close to four years across two organizations.
What do I think about the stability of the solution?
BrowserStack is mostly stable for our needs, though sometimes there is slowness in the network, especially when working with AWS-based hosting.
What do I think about the scalability of the solution?
Currently, BrowserStack's scalability for our organization meets our needs as we have relatively limited use cases, and so far what we have scaled has worked fine for us.
How are customer service and support?
I have not had to interact with BrowserStack's customer support team, as most issues were addressed locally.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
Before using BrowserStack, we had used LambdaTest and physical devices as our prior solutions.
What was our ROI?
We have definitely seen a return on investment with BrowserStack, particularly in tracking the value realized per automated test case and time savings in testing apps across multiple clouds, browsers, and operating systems, leading to money savings since we previously had many resources engaged in that.
What's my experience with pricing, setup cost, and licensing?
The setup cost and licensing were handled at the enterprise level, as our bank is a large organization, and these central negotiations were managed by the finance team, so I have limited exposure to that.
Which other solutions did I evaluate?
Before choosing BrowserStack, we mostly evaluated LambdaTest as an option.
What other advice do I have?
We have a local version of BrowserStack for direct access, and we also access BrowserStack from AWS EC2 machines, providing us with both kinds of interactions available.
My advice for others looking into using BrowserStack is to evaluate options, perform an ROI calculation beforehand, and identify the specific use cases BrowserStack excels at, as this will lead to a much higher ROI return for your organization rather than using it for everything, including manual testing. I would rate my overall experience with BrowserStack an 8 out of 10.
Which deployment model are you using for this solution?
Hybrid Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Highly Efficient Testing Tool for Web and Mobile Apps
What do you like best about the product?
Looking from my eyes browserstack seems very efficient software for testing website as well as mobile applications.
I also refer to my friend who are working in IT industry
What do you dislike about the product?
Nothing seems to be dislike. As it is very efficient tools they are providing
What problems is the product solving and how is that benefiting you?
Testing our mobile applications and helping hands in friends group
User-Friendly Cross-Browser Testing with Excellent Support
What do you like best about the product?
I appreciate BrowserStack for its user-friendly interface and the convenience it offers for cross-browser testing. It provides a wide range of features, such as live testing, mobile testing, and debugging, which I find very useful. Integrating it into our system was straightforward, and it also connects easily with CI/CD pipelines. The customer support is excellent, and I find myself using it frequently.
What do you dislike about the product?
I like most of the features, but there are a few common issues I haven't liked about BrowserStack. It is expensive, and the debugging capabilities are limited on some devices. Additionally, the performance feels slower compared to using a real device.
What problems is the product solving and how is that benefiting you?
Sometimes, we encounter situations where real devices are not available. In those cases, we use BrowserStack instead, which helps us save both time and costs. Additionally, there is no need for in-house maintenance.
Comprehensive Testing Tools for All Devices
What do you like best about the product?
A range of testing tools is available, allowing us to perform tests on a variety of different devices.
What do you dislike about the product?
At this moment, I have nothing to dislike.
What problems is the product solving and how is that benefiting you?
There is a wide range of devices available for us to test on, which makes things much more convenient since we don't have to rely on having any physical devices ourselves.
Essential Tool for Cross-Browser and Device Testing
What do you like best about the product?
As a tester, I find it very useful. For manual testing, if I want to do cross browser testing or multiple device testing, I prefer browser stack. Now in addition to this, we have AI tools also. Would like to proceed further with this,
What do you dislike about the product?
Whenever I user this platform, I find this helpful
What problems is the product solving and how is that benefiting you?
Primarily testing the features in multiple device and platforms
