Excellent for Testing Across Multiple Mobile OS
What do you like best about the product?
testing with different mobile OS for android and ios
What do you dislike about the product?
Tests can time out or some devices may take longer to load
What problems is the product solving and how is that benefiting you?
we don't need physical device for testing our changes.
Cross-browser testing has boosted my automation and makes sharing QA evidence much faster
What is our primary use case?
In the start of my career, I performed functional testing on mobile devices and web applications, and I used BrowserStack for testing web applications and mobile applications for one year.
My main use case for BrowserStack was cross-browser testing and integrating it with Selenium to test my functional test cases on web applications and mobile apps.
For example, in a test case to log in to a web application, using BrowserStack allowed me to identify local elements in my UI, making it very easy to automate those elements, considering the login tests for a basic web application. I recorded that test and integrated it with Selenium in my local environment to automate that overall test on both the web application and mobile application.
I mostly integrated Selenium with GitHub Actions, so whenever a new commit occurs, I can rerun all the tests I have written using BrowserStack on the Selenium framework in my IDE.
Most of my use cases involve manual plus automated testing, and BrowserStack provides real cloud devices, which is very useful when someone does not have a real device or mobile device. It allows us to test our web applications and mobile applications virtually, and the features for creating screenshots and videos are very beneficial for creating manual test cases. I can record those test cases in my browser and easily upload them to Jira for others to automate them or review them quickly.
The ability to record and share those screenshots and videos definitely makes the tickets and use cases clearer. For instance, in a scenario to log in to a web application and perform functional testing, I can take screenshots or record video, which simplifies report generation and saves time for both developers and QA.
What is most valuable?
BrowserStack positively impacts my organization by saving time in the QA testing process and clarifying the mission, which is important.
I don't have exact numbers, but it's clear that when someone new joins my team, handing over a Jira ticket with video recordings and screenshots significantly clarifies the mission and saves a lot of time for the new developer or a product manager wanting to review the overall functionalities of our web application.
What needs improvement?
Improvements for BrowserStack could include better usability when working under a private network or a VPN, since it can be challenging to access restricted URLs. There are times when running an automation test that the loaded elements aren't reliable, which can lead to frustrations stemming from inconsistent results.
Apart from restricted URL access under VPN and inconsistent results, I don't recall exact numbers on pricing, but it varies depending on the use case and could definitely be better.
The suggestions for BrowserStack improvements I have highlighted mainly concern integrations.
For how long have I used the solution?
I have been working for the last five years as a DevOps Engineer.
What do I think about the stability of the solution?
From my experience, BrowserStack has been mostly stable. I did not encounter any reliability or downtime issues during the time I used it.
What do I think about the scalability of the solution?
As for scalability, I have not tested it at that level, as our usage has been confined to automating manual test cases for our internal team without facing significant scalability concerns.
How are customer service and support?
I have not reached out to customer support, so I have not experienced any issues from their side.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
I wasn't using any other solution related to BrowserStack as it was the first tool I used for automating browser and mobile testing.
Before choosing BrowserStack, I did not evaluate other options. I had been using Selenium for a long time and came across BrowserStack, saw some functionalities, and decided to use it directly.
How was the initial setup?
Regarding pricing, setup costs, and licensing, I don't remember exact pricing, but due to the size of my organization, it was not a significant issue. The setup cost is not substantial, as subscribing directly through AWS Marketplace is quite seamless and licensing is also handled smoothly through AWS.
What was our ROI?
While I don't have precise metrics, I can say that with our QA team of five members, we were able to record functional tests much faster, accomplishing what sometimes took five days within one to two days, effectively reducing our time by around fifty percent for recording manual test cases.
What's my experience with pricing, setup cost, and licensing?
I purchased BrowserStack through the AWS Marketplace.
What other advice do I have?
For anyone looking into using BrowserStack, I would advise that if you are a QA wanting to automate tests or record some tests, make reports or videos, or if you are a product manager providing QA with Jira tickets, BrowserStack is a solid choice for your work.
Overall, BrowserStack is a great product that I have utilized a lot during my early years as a QA.
I think this interview format is very good, and I have no suggestions for change.
I would appreciate a short poem or haiku that summarizes my review. My review rating for this product is 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)
Effortless Cross-Browser Testing with Seamless Automation
What do you like best about the product?
As a QA Automation Tester, I like that BrowserStack makes it easy to run automated tests on many real devices and browsers. It saves time on setup, works smoothly with tools like Selenium, and helps ensure our application works well for all users.
What do you dislike about the product?
Sometimes test sessions on BrowserStack can be a bit slow, especially
What problems is the product solving and how is that benefiting you?
BrowserStack solves the problem of testing across many different devices and browsers without needing to maintain our own device lab. This lets me quickly check how our application works for all users, catch bugs early, and deliver higher quality releases with less effort. It saves time, reduces costs, and makes cross-browser/device testing much easier for our team.
Great for Automation, But Slow Cloud Device Loading
What do you like best about the product?
I really like the automation testing on mobile devices with BrowserStack. It helps us identify a lot of UI bugs, which is super helpful in our testing processes. Setting up BrowserStack was also quite easy for our team.
What do you dislike about the product?
I would say, the cloud device loads very slow.
What problems is the product solving and how is that benefiting you?
BrowserStack helps me with device matrix, cross-browser testing, and automation testing on mobile devices, helping us identify lots of UI bugs.
Effortless Mobile Testing with Robust Feature Set
What do you like best about the product?
I use BrowserStack for manual and automation testing of mobile applications, particularly appreciating the easy access and good user interface. It allows us to test our mobile app on a wide range of Android and iOS devices and run our automation tests using Appium, which helps us deliver applications with top quality. The reporting and SDK benefits are also valuable, providing easy access to configure executions, along with reports of overall execution in projects that help track progress and status of app builds. The SDK allows changes to any device version and properties with a single file change. The initial setup was easy with the documentation provided by BrowserStack.
What do you dislike about the product?
Nothing
What problems is the product solving and how is that benefiting you?
I use BrowserStack for testing our mobile apps on a wide range of devices, ensuring top quality. It offers an easy UI, reporting for tracking progress, and SDK for changing device settings easily. This all gives me quick configuration and a smooth testing process.
Powerful Testing Tool with Some Setup Challenges
What do you like best about the product?
I really like the local browser testing feature in BrowserStack because it allows me to test everything that is yet to go live. It definitely adds value by making my work easier and helps in troubleshooting as it is easy to identify issues. The initial setup was also easy.
What do you dislike about the product?
Sometimes it crashes and there's slowness. Also, the BrowserStack local setup can be complicated and doesn't always work.
What problems is the product solving and how is that benefiting you?
BrowserStack eliminates the need to purchase real devices for testing. It simplifies location-based and local environment testing, making our work easier and troubleshooting more straightforward.
Remote devices have enabled accurate mobile regression testing and crash verification across platforms
What is our primary use case?
My main use case for BrowserStack is to verify or develop features and then verify how they will work on different platforms, specifically iOS and Android, including versions 14, 13, and Android 16, with different screen resolutions.
For example, I run the application on a device in BrowserStack, then open the log files to verify if crashes will occur, so I understand how the application or my feature performs well on specific devices.
For instance, if I fix issues and need to verify, or if I receive a specific issue from customers, I try to install the application on the same device with a similar iOS version and attempt to replicate the issue.
What is most valuable?
BrowserStack offers many devices with different platforms. For example, if there is an available beta version for Android or iOS, you already have access to such platforms, and you can verify how it will work for future releases.
I use the feature of testing on beta versions in my workflow all the time, checking how the application works on the pre-release build, and our QA people also verify and perform regression testing using the pre-release build on specific devices through BrowserStack.
BrowserStack has positively impacted my organization by saving money that would be spent on buying new devices. For instance, if there are many developers in the company, buying each new device costs more than subscribing to BrowserStack where you get access to many devices.
What needs improvement?
I think a possible improvement for BrowserStack could be adding features such as sending SMS or making FaceTime calls because, as far as I know, those features are not available at the moment. Additionally, it could be useful to attach some virtual phone numbers for specific devices and also consider integrating Apple Pay payments to verify how the application works on those platforms.
I would see such features on BrowserStack. I know there are many options such as virtual credit cards, virtual phone numbers, or virtual Apple Pay or Google Pay, and it is possible, but I do not know why BrowserStack still has not implemented them.
For how long have I used the solution?
I have been using BrowserStack for more than ten years.
What do I think about the stability of the solution?
BrowserStack is quite stable for me because it offers many different devices, is always up to date, and has a nice user interface with good user experience.
Which other solutions did I evaluate?
Before choosing BrowserStack, I evaluated another platform called Device Anywhere and also one more service, but I cannot recall the name of that service.
What other advice do I have?
As I mentioned before, some of our customers use specific devices with specific iOS versions, for example, iOS 16. Currently, I do not use this iOS 16, and if I need to replicate an issue, I install the build on this iOS version and verify the issue.
I do not know what device to suggest for others looking into using BrowserStack, but I think an iPhone 17 could be an option.
I chose nine out of ten because, as I said, if BrowserStack could enable making FaceTime calls and sending virtual SMS or facilitating Apple Pay payments, that would make it a perfect ten for me. I gave this review a rating of nine out of ten.
Excellent Live Testing, But AI Features Need Refinement
What do you like best about the product?
What I like best about BrowserStack is the Live testing experience, especially App Live and Web Live. Being able to test on real devices without depending on physical hardware is extremely valuable, particularly for validating issues that only appear on specific devices, operating systems, or screen sizes. This capability helps the team identify and reproduce bugs more accurately and faster. I also found the Bug Capture feature useful, as it provides detailed technical information that is helpful for developers during analysis and debugging, improving communication between QA and development.
What do you dislike about the product?
What I dislike about BrowserStack is that some of the AI-driven features, especially test case generation, are still too immature for practical use. While the tool generates a large number of test cases quickly, many of them are duplicated, irrelevant, or lack proper alignment with the actual business rules, which creates significant rework. In practice, reviewing and fixing the generated scenarios often takes as much time as writing them manually. Additionally, several features overlap with tools we already use effectively, making it hard to justify the full platform cost when only a few modules clearly add value.
What problems is the product solving and how is that benefiting you?
BrowserStack solves the problem of limited access to real devices and environments for testing. It allows me to validate issues directly on real browsers and mobile devices without relying on personal or shared physical hardware, which is especially beneficial for reproducing device-specific and OS-specific bugs. This improves confidence in test results, speeds up validation, and reduces friction when diagnosing issues that are hard to reproduce locally. Additionally, features like Bug Capture help centralize technical evidence, making it easier to communicate issues clearly to developers and streamline the debugging process.
Excellent Products and Outstanding Customer Service
What do you like best about the product?
Greats product and features, great customer service
What do you dislike about the product?
Products are licensed at a high price. Better pricing is what i would hope for
What problems is the product solving and how is that benefiting you?
Helping align our software testing needs with high-quality products.
Seamless Multi-Device Testing with Efficient Automation Features
What do you like best about the product?
It supports multiple devices and now includes a parallel feature, allowing me to test scenarios on different devices with various operating systems simultaneously. There is also support for local BrowserStack. I also appreciate the App Live and Live Platform features, which make the Appium setup more efficient, enabling easier automation of mobile applications.
What do you dislike about the product?
Sometimes the device is not available, and the latest updated version is not up to date. For example, while most physical devices now have Android 16, BrowserStack still only shows the older version, Android 15.
What problems is the product solving and how is that benefiting you?
The most important aspect for me is being able to check APIs using the network tab. This feature is crucial because, on a physical device running a mobile platform, we don't have that capability. It makes it much easier to debug issues on mobile platforms.
