BrowserStack review
Rating: 10 out of 10
January 28, 2025
Vetted Review
Verified User
3 years of experience
We use App Live and app automate for cross browser testing. It is the wonderful product for cross browser testing. Though there are various challenges that needs to be addressed. We have been using it for a while now like may be 5 years or so. I would happy to see AI integration as well to these tools now.
- Cross Browser Testing
- Cross Device Testing
- Local Testing
- Geolocalized Testing
Cons
- Very slow, speed can be improved
- Bug fixed needs to be incorporated and new updated software should be launched
- There are lags at several places
- less user friendly
- Cross Browser Testing
- Cross Device testing
- Test Quality
- Time to Market
We have a product that is used by students worldwide and we recieve high traffic on web and mobile. Testing on single browser and device wasn't helpful when we are concerned about UI and CSS of different devices along with functionality. BrowserStack app live is single platform for testing variety of devices.
BrowserStack's comprehensive coverage has transformed our development process by enabling thorough testing across various browsers, devices, and operating systems. It ensures high-quality, bug-free releases, reduces manual effort, and speeds up testing cycles. This has improved team efficiency, enhanced user experience, and helped us deliver reliable, seamless software products to our customers.
- App Automate
BrowserStack App Automate perfectly met our needs by enabling automated testing for mobile apps across real devices. It supports diverse frameworks, ensures compatibility across platforms, and identifies bugs early. With seamless integration into our CI/CD pipeline, it improved test coverage, reduced manual effort, and accelerated our app development and release cycles.
BrowserStack outshines LambdaTest with its vast real device cloud, faster performance, and reliable support. It offers superior browser and device coverage, seamless integrations, and unmatched scalability. We chose BrowserStack for its robust features, proven reliability, and ability to deliver flawless testing experiences, ensuring high-quality software releases tailored to our users' needs.
200
In my organization, 200+ people use BrowserStack, representing various business functions such as:Quality Assurance (QA): For manual and automated testing.Development: For cross-browser and cross-platform debugging.DevOps: For integrating testing within CI/CD pipelines.Product Management: For ensuring seamless user experiences.Support Teams: For replicating and resolving customer-reported issues.
5
We have 5 in-house professionals supporting BrowserStack on an ongoing basis. They include:Automation Engineers: Skilled in frameworks like Selenium, Playwright, and Appium for automated testing.DevOps Specialists: Experienced in integrating BrowserStack with CI/CD tools like Jenkins or GitLab.QA Leads: Overseeing test strategies and BrowserStack usage.Support Engineers: Handling user queries and troubleshooting.Training Specialists: Educating teams on effective BrowserStack utilization.
- Cross Browser Testing
- App Automate
- Localization Testing
- Simulating Real-World Scenarios
- Custom Device Pools
- On-Demand Customer Issue Replication
- AI-Powered Test Case Generation
- Performance Testing
- End-to-End Workflow Testing
No
- Ease of Use
The most important factors in our decision to purchase BrowserStack were cloud solutions and ease of use.Cloud Solutions: BrowserStack’s cloud-based platform eliminated the need for maintaining physical devices or complex infrastructure, offering on-demand access to real devices and browsers for testing. This flexibility is key for our globally distributed team.
Ease of Use: The intuitive interface and simple setup process made it easy for our teams to get started with minimal training. This ensured quick adoption across departments and allowed us to focus on testing without getting bogged down in technical complexities.
Ease of Use: The intuitive interface and simple setup process made it easy for our teams to get started with minimal training. This ensured quick adoption across departments and allowed us to focus on testing without getting bogged down in technical complexities.
If we had to do it again, I would focus more on the following aspects during the evaluation and selection process:Expanded Performance Testing Capabilities: I would ensure that the platform’s performance and load testing features meet our future scalability requirements.Enhanced Customization Options: Exploring more granular control over device configurations and testing environments to better match our specific needs.Cross-Team Collaboration: Involving more teams, like support and product management, early on to better understand their use cases and ensure alignment.More Pilot Testing: Running longer pilot phases with specific workflows to test integration with our internal tools and get real-world feedback.This approach would ensure we maximize BrowserStack’s potential and address any gaps earlier in the decision-making process.
- Implemented in-house
Change management was a big part of the implementation and was well-handled
Implementing BrowserStack involved clear communication, regular training, and phased rollout. We focused on providing strong support, gathering feedback from teams, and addressing concerns early. This helped smooth the transition and ensured the tool met everyone’s needs. The experience taught us the importance of continuous improvement in change management and control.
- Initial Learning Curve for Users
- Integration Challenges with Existing Tools
- Device and Browser Compatibility Configurations
- Online Training
For configuring BrowserStack, create custom device groups for critical devices, automate tests across different browsers, and organize test data for reuse. Integrate with your CI/CD pipeline for continuous testing, use parallel testing to save time, and regularly analyze test results to improve and adjust configurations as needed and when needed.
No - we have not done any customization to the interface
No - we have not done any custom code
In addition to the standard configurations, we customized BrowserStack by setting up specific device pools for high-priority projects and integrating it with our internal test management tools for better tracking. We also optimized parallel testing to speed up execution and ensured seamless data flow between our CI/CD pipeline and BrowserStack.
I'm not sure if we purchased premium support for BrowserStack. I would recommend checking with our procurement or IT team for clarification. Premium support typically offers quicker response times and more in-depth technical assistance, which can be valuable for handling complex issues. But again I am unsure of the fact that we have premium support or not.
Yes
Yes, I reported a bug with BrowserStack regarding device compatibility during testing. While the resolution took slightly longer than anticipated, the support team was responsive and proactive. They thoroughly investigated the issue, provided regular updates, and once the fix was implemented, it resolved the problem effectively, meeting our expectations. The overall experience was positive, even though the timeline could have been faster.
One instance of exceptional support from BrowserStack was when we faced an issue with cross-browser compatibility that was affecting our critical release timeline. The support team immediately escalated the issue and worked closely with our team to reproduce the bug in their environment. They provided a patch and regular updates throughout the process. Not only was the issue resolved quickly, but they also offered additional suggestions to optimize our testing setup. Their responsiveness and dedication ensured we met our release deadline without compromising on quality.
- Cross-browser Testing
- Mobile app testing
- Automated Testing Integration
- Complex Test Configuration
- Handling Large Test Suites
- Advanced Debugging
Yes
Yes, BrowserStack does provide a mobile interface. The mobile interface works well for performing real-time testing on real devices, allowing easy access to various mobile browsers and operating systems. However, it can sometimes feel less intuitive compared to the desktop interface, and navigation could be smoother for users who are new to the platform. Despite this, it is functional and effective for most mobile testing needs.
- Test Management Tools (Jira, TestRail)
- CI/CD Tools (Jenkins, GitLab)
- Version Control (GitHub)
We integrated BrowserStack with tools like Jenkins, GitLab, Jira, and TestRail to automate testing and track results. The integration was mostly straightforward, especially with pre-built plugins, but required some customization for our workflows. Overall, it wasn’t too difficult, though a bit of setup was needed for seamless use.
- AWS Device Farm
We would like to integrate BrowserStack with additional systems like Slack for real-time notifications and AWS Device Farm for enhanced device testing coverage.As of now, we are not certain if these specific integrations are fully supported by BrowserStack. However, based on their frequent updates and support for popular tools, it’s likely that they may provide support or have plans to do so in the future. We will monitor for updates or check with their support team for further details.
- API (e.g. SOAP or REST)
- Javascript widgets
We have used the following integration technologies with BrowserStack:API (e.g., REST): We’ve integrated BrowserStack with our CI/CD pipeline and test management tools using BrowserStack's REST APIs to automate test execution and capture results.File Import/Export: We’ve used file import/export for uploading test scripts and results, which simplifies the process of running and tracking tests.Single Sign-On (SSO): We’ve configured SSO to make it easier for our teams to access BrowserStack without managing multiple credentials.We have not used the other integration technologies like JavaScript widgets, ETL tools, or AppExchange, but we are open to exploring them in the future.
