Essential Tool for Easy Test Management and Mobile Automation
What do you like best about the product?
At our company, we use it as Agent AI, for test management, and for App Live to support mobile automation. We rely on it often, and it is straightforward to implement.
What do you dislike about the product?
During our testing of the Generate AI feature, we noticed that it lacks an option to continue the chat and further refine the conversation.
What problems is the product solving and how is that benefiting you?
No Physical Infrastructure Required - Cloud-based testing eliminates the cost and maintenance of physical device labs
Faster Issue Resolution - Quick access to specific device/OS combinations speeds up bug triage and resolution
Improved Test Coverage - Ability to test across a wider range of devices and browsers than would be practical with physical devices
Consistency - Standardized testing environment across teams
Corporate Contract - Q2 has a corporate account, making it accessible to teams (with manager approval via IT Help-desk)
Effortless App Testing Across Devices, Minor Pricing Clarity Needed
What do you like best about the product?
I use BrowserStack to test Android applications on different devices and Android versions. I appreciate that it helps me test applications across a wide range of Android versions, including older and newer releases, without needing physical devices. I really like the ease of uploading local Android applications, testing apps directly from the app store, and accessing detailed logs, which helps a lot with debugging and troubleshooting. Additionally, I found the initial setup to be pretty easy and intuitive.
What do you dislike about the product?
The pricing plans could be clearer. Clearly outlining what is included in each plan, specifying the available devices, and clearly explaining the differences between app testing and web testing.
What problems is the product solving and how is that benefiting you?
I use BrowserStack to test Android applications across different devices and versions without physical devices. It allows testing of apps from the app store and provides detailed logs for debugging.
Testing your apps for all browsers
What do you like best about the product?
Very helpful in testing web and mobile apps in different browsers for compatibility
What do you dislike about the product?
what ever limited use of Browser stack we have done, it looks good
What problems is the product solving and how is that benefiting you?
web and mobile apps in different browsers for compatibility
Effortless Testing with Real Devices
What do you like best about the product?
I really appreciate BrowserStack for offering a full range of real devices, which is essential for us as a service company with customers who are very particular about application compatibility. The ease of use when it comes to installing APK or IPA files is a big plus, especially when I want to upgrade the APK with new features or test a web app on multiple browsers. I'm also starting to like the AI features. The initial setup is easy, and it fits well with our needs.
What do you dislike about the product?
I find the iOS app installation slower than I'd like. When installing an app after selecting the device, it takes a good amount of time.
What problems is the product solving and how is that benefiting you?
BrowserStack provides a full range of real devices for testing, which is crucial for our service company. It's easy to install APK or IPA files and test web apps across multiple browsers. I also enjoy the new AI features.
Essential Tool for Effortless UI Testing and Debugging
What do you like best about the product?
As a frontend/React developer, it really saves time when validating UI, date/time issues, responsiveness, and browser-specific bugs without needing multiple physical devices.
What do you dislike about the product?
Occasional slowness or session lag, especially during peak hours or when using real mobile devices.
Session timeouts / disconnections can interrupt longer debugging sessions
What problems is the product solving and how is that benefiting you?
I can quickly test my React UI on real browsers and real mobile devices from one place.
It helps me catch layout, date/time, and CSS issues early before release.
I can reproduce client issues accurately, even if they occur only on specific browser versions.
It speeds up QA and release cycles by integrating easily with automation tools like Cypress or Playwright
Overall, it saves time, reduces risk, and increases confidence in production releases.
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.
Cross-device UX testing has become seamless and now supports faster, higher-quality releases
What is our primary use case?
My main use case for BrowserStack involves working on campaign testing for a healthcare product, where the application supports both Android and iOS devices for responsiveness and also supports the iPad device. We generally test three devices: for Android, we consider the Samsung S23, for iPhone, we choose iPhone 12, and for the iPad, we test on the latest iPad available on BrowserStack with both landscape and portrait views.
What is most valuable?
BrowserStack helps me handle challenges with device fragmentation or OS updates in my workflow through installation and uninstallation features. Whenever new updates come from Okta, we just update that. Additionally, when the application crashes or devices crash, BrowserStack provides multi-device testing; I just have to paste the URL in different devices, start different sessions, and it will be handled, allowing us to test everything simultaneously, which is really useful. The OS updates are automatically managed from Okta, so these things are well-handled.
In my day-to-day work, we generally do manual testing with BrowserStack, checking all UI components for responsiveness. The main purpose is to verify the responsiveness of our application, which includes checking the UI, mainly the fonts, alignment, margins, and all aspects to see how the content looks on different devices and how it fits within various screen sizes.
The best features that BrowserStack offers include both manual and automation testing; live devices reduce our real device availability. For automation, we utilize the Bellatrix framework integrated with BrowserStack, allowing it to run automatically on BrowserStack Android devices. I am mostly impressed with the automation because when I run everything, they provide logs and screenshots for each and every step, which is very helpful.
We are also using the AWS pipeline for generating reports on the automation side, where we set up AWS to easily get reports from BrowserStack and share them with all stakeholders automatically.
BrowserStack has positively impacted my organization primarily through time savings because it is very easy to use and replicates physical devices for testing, which is crucial since we usually do not have physical devices. This saves us time, and when we test the application's UI and UX, it helps identify more bugs with different devices and sizes, improving the overall quality of the software.
What needs improvement?
One improvement I observe is that iOS automation is not feasible due to some configuration issues, although it serves as a great tool for cross-browser testing. However, specific iPad or iOS automation requires a lot of setup, and we need to find a way to simplify the configuration for iOS automation using BrowserStack.
Regarding needed improvements, I sometimes notice speed concerns where BrowserStack can be delayed in response, and from a security standpoint, some URLs are inaccessible, leading to potential security issues. While BrowserStack has almost everything, integrating a feature for test case execution would be beneficial, as it would reduce our manual test execution time.
For how long have I used the solution?
I have been using BrowserStack for six years, since 2017. I continuously use BrowserStack for cross-browser testing, as the company provides a license for that, and we are using BrowserStack for all of our cross-browser testing.
What other advice do I have?
My advice for others looking into using BrowserStack is to prefer it over physical device availability, as we mostly have two or three devices at most. BrowserStack offers numerous devices with different versions, allowing us to test our UI and perform responsive testing easily without manual setups on real devices and version updates.
I believe BrowserStack is a great tool that minimizes manual efforts, and I recommend it to everyone as it effectively addresses challenges associated with real devices. I would rate this product an eight out of ten.
Which deployment model are you using for this solution?
Private Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
