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-platform testing has accelerated releases and now needs smarter AI-driven test creation
What is our primary use case?
My main use case for BrowserStack is to test things on real devices, hosted real devices and also to run automated tests on these devices to support multi-platforms, multiple different browsers, different platforms, and different devices. That is the use case we have to run tests.
A quick specific example of using BrowserStack for this kind of testing is when a big automobile company had a configurator for their vehicles, and we were using BrowserStack to test that the configuration of these vehicles can be done by customers on smaller mobile devices, iPads, or different laptops and platforms which the user uses. We also have the dashboards of the tests that were run on these devices.
What is most valuable?
The best features that BrowserStack offers include the ability to run manual and automated tests on real devices. We can create bugs, integrate it with other platforms like Jira or Azure, and use self-healing scripts with Selenium. We also have the test runs for different versions or with different frameworks, not just Selenium but with Playwright as well. Additionally, there are real-time dashboards and notifications sent when tests fail or when we need screenshots or recordings of test executions, and we can easily integrate this into our pipelines.
BrowserStack has positively impacted my organization by providing an out-of-the-box solution for whole test executions across different projects for our automobile customers. We have worked on around twenty to thirty projects, and the need for a stable, customizable single test execution platform that supports different platforms has been met. It has helped manage the entire quality assurance of the product efficiently.
The measurable improvements due to BrowserStack include a significant efficiency gain, allowing the whole team to collaborate on testing and communicate faster. Also, the easier integration with project management tools has been beneficial. The documentation of findings has improved, which helps us share insights with different project stakeholders.
What needs improvement?
Going forward, one way BrowserStack could improve is by incorporating AI concepts to create tests automatically from provided URLs or user intentions, generating scripts without needing users to write automation scripts. This could include natural language prompting for both test creation and insights from results.
While pricing for BrowserStack is acceptable, usability could improve with easier onboarding and understanding of features. An AI-driven chat interface could simplify managing the entire product using natural language instead of manual settings adjustments in various sections.
For how long have I used the solution?
I have been using BrowserStack for approximately eight to nine years.
What do I think about the stability of the solution?
What do I think about the scalability of the solution?
BrowserStack's scalability is enhanced by its auto-scaling capabilities on AWS, allowing us to increase the number of parallel testing instances as needed.
How are customer service and support?
BrowserStack customer support is excellent, with knowledgeable staff assisting throughout onboarding, setup, and understanding our needs to provide tailored solutions. I would rate the customer support an eight on a scale of one to ten.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
Previously, we used LambdaTest but switched to BrowserStack for greater stability and performance, bolstered by excellent documentation and support.
How was the initial setup?
The process of getting started and managing licenses was straightforward. BrowserStack provided the number of parallel users we wanted, such as five or ten, along with the number of parallel executions possible. Their documentation also made it easy to set up.
What about the implementation team?
I have unique aspects about how I use BrowserStack because sometimes we had to use our own AWS deployment of it because we cannot use the deployed BrowserStack by itself. We used a closed API with AWS for that managed instance, having the CI/CD pipeline to run the tests on AWS pipelines. We hosted BrowserStack on AWS and auto-scaled as needed or managed images and observability, and everything is managed on AWS.
What was our ROI?
I have seen a return on investment with significant time savings. For instance, pipeline executions that used to take eight hours have been reduced to one hour, enhancing continuous deployment and providing quicker feedback cycles. This has proven vital for various projects needing parallel executions, making our deployment much faster and more reliable. Some measurable KPIs included the number of tests executed in parallel in one hour, the reduction of bugs, and managing hotfixes, which has decreased due to efficient testing and execution.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing was that it was a bit on the higher side, around three hundred dollars per user per month, and I hoped it could be reduced.
Which other solutions did I evaluate?
Before choosing BrowserStack, I evaluated alternatives including Selenium Grid, Selenium Box, Copado, and LambdaTest, and ultimately found BrowserStack to be superior to all these options.
What other advice do I have?
We also use AWS Code Pipelines to integrate BrowserStack, triggering Selenium tests with it and executing test cases in parallel. This was one of the most important features to execute tests faster, along with automatically saving screenshots, logs, and videos on an S3 bucket for later use or analysis.
For others considering using BrowserStack, I advise that if your project involves complexities requiring continuous deployments or if you have a large test team, BrowserStack is a good choice, especially if you face flakiness in tests. It is great for well-documented and communicated results.
I give BrowserStack a rating of seven on a scale of one to ten. I rate it a seven because I have used it extensively for the last seven to eight years and see it as a good product. However, there are competitors in the market offering similar features, and BrowserStack needs to highlight more unique selling points. Although it has a good market share and stability, I believe there are improvements and features that could elevate it to a nine or 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)
Quick Results but Pricing Could Be Better
What do you like best about the product?
I use BrowserStack primarily for testing, and I've found it to be incredibly valuable in automating our testing scenarios. The platform excels in delivering quick results, which is essential for keeping up with our fast-paced workflow. This efficiency improvement has been a standout feature, as it streamlines our testing process and saves valuable time. Additionally, integrating it with React has been smooth, complementing our existing development stack well.
What do you dislike about the product?
I think the pricing is an issue. Additionally, while we've experienced improvements in efficiency, this aspect also poses some challenges.
What problems is the product solving and how is that benefiting you?
I use BrowserStack to automate testing scenarios quickly, improving our team's efficiency significantly.
Great Testing Tools and Integrations, but Device Load Times and Pricing Need Work
What do you like best about the product?
BrowserStack lets us test on real browsers and real devices without buying anything ourselves. The Automate platform works great with our Selenium and Playwright tests. Also running tests in parallel saves a lot of build time. Percy is also helpful for catching small visual issues. The integrations with GitHub and Jenkins fit right into our CI pipeline. We were able to debug live sessions with built-in tools.
What do you dislike about the product?
Sometimes the real devices take a few seconds to load, especially during heavy traffic hours. The pricing is a bit high when scaling large automation suites.
What problems is the product solving and how is that benefiting you?
BrowserStack gives us experience across browsers and devices, something we could never recreate with physical hardware. It helps us catch cross-browser issues early and speeds up code shipping. Our testing team is more consistent and less dependent on local setups. Overall we ship faster than before.
Cross-Platform Testing Made Easy, Still Exploring Downsides
What do you like best about the product?
Testing accross platform, and automating testing
What do you dislike about the product?
I need to get back to you about his one :)
What problems is the product solving and how is that benefiting you?
Being able to run tests accross multple devices and platform from one place is very helpfull, saving lots of time of efforts.
Also, being able to test an app, ios or android, straight from the screen.
Promising AI Integration with refreshing perspective on AI
What do you like best about the product?
I like the understanding of AI as a bootstrapping tool, in contrast to a replacement of human intelligence. BrowserStack's AI Agents integrate well with their portfolio and offer help in very confined use cases. In my opinion, this is a better approach than for example Xray AI. They assume that AI can generate entire test cases with minimal user interaction or correction. BrowserStack's presentation reassured me that they do not follow this naive approach.
What do you dislike about the product?
Many of the features are still unavailable. I really hope this is not vaporware.
What problems is the product solving and how is that benefiting you?
Making test management manageable and integrating the different components of test management in a suite
Gets the job done
What do you like best about the product?
Intuitive interface, easy to use, flexible, customizable
The ability to track automated test cases
Dashboard is easy to read, high level stat graphs are very useful.
What do you dislike about the product?
Unable to export the entire test case base or selection of folders.
I'd like an option to order folders and test cases alphabetically
What problems is the product solving and how is that benefiting you?
BrowserStack is helping me track my testing efforts, store and organize test cases, provide reports and visibility to stakeholders. We work in sprints, and I use Test Runs to display which test cases were used in the current sprint. Active test runs data provides high visibility and status update to the team. It is also helping me track automation test coverage.
An essential tool for our QA and testing workflows
What do you like best about the product?
It has a wide coverage of real devices and browsers.
Its easy setup and use
Saves significant time and costs compared to managing test devices internally using existing methodologies
What do you dislike about the product?
Really expensive compared to other Saas we use and buy
What problems is the product solving and how is that benefiting you?
Helping us to accelerate testing on multiple devices and Operating systems and also around accessibility testing that is a long process
I would like to recommand but still some of the feature need add
What do you like best about the product?
testing multiple device with the multiple OS ensuring compatibility of the software
What do you dislike about the product?
Slowness and incinsistant issue in the browserstack
What problems is the product solving and how is that benefiting you?
Compatibility testing if Android and IOS Mobile
The functionality is valuable, but there is room for improvement in performance.
What do you like best about the product?
As an individual developer, BrowserStack Live allows me to perform real device debugging and style comparisons across multiple devices/browsers without the need for my own equipment. It's easy to use, has low implementation costs, and I use it before every regular regression test. The screenshot/recording evidence is also sufficient, and it really enhances my efficiency.
What do you dislike about the product?
The device loading and session switching are relatively slow during peak hours, with occasional lag, and some models (such as the SIM-equipped iPhone) have a long cold start waiting time, affecting the continuity of debugging experience. If the startup speed and stability can be further optimized, it would be more worthwhile for long-term use.
What problems is the product solving and how is that benefiting you?
It solved the difficulties I faced as an individual developer in multi-device compatibility and side-by-side comparison: it used to be very difficult to simultaneously check styles and interactions on the iPhone, Android, iPad, and desktop browsers, and it was also inconvenient to reproduce issues in an intranet environment.
