DevOps Engineer at a tech services company with 51-200 employees
Real User
Top 10
Dec 18, 2025
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.
Chief Executive Officer & Founder at a tech vendor with 201-500 employees
Real User
Top 10
Dec 2, 2025
My main use case for BrowserStack is automating some of the test cases. A quick specific example of a test case I automate with BrowserStack is some of the application URLs.
BrowserStack is used for mobile testing. I work in web technology for logistics with BrowserStack. The environment I work in with BrowserStack is enterprise level.
I use the solution in my company for business transformation, specifically for IT business transformation projects where a customer wants to transfer their legacy applications to the cloud and modernize them using mobile apps. My company takes enterprise-level applications to the cloud.
Sr QA Manager at a tech services company with 51-200 employees
Reseller
Top 20
Sep 7, 2023
Our clients provide us with the BrowserStack license to perform tests on certain devices. We perform mobile app testing on different devices since it is not possible for everyone to have all of the devices on hand.
This has been a short-term project. We're still testing it out. We're doing functional and integration testing. Right now, the scope is not there for the screen orientation, and we're not testing that right now. We're looking at speed and compatibility issues with different versions. We're able to find some of the UI issues and installation issues. We are able to capture admin app issues and UI issues.
Qa lead at a marketing services firm with 201-500 employees
Real User
Dec 11, 2021
We use BrowserStack for testing on different platforms. It's a platform that allows us to test on different devices and platforms. We're using it as a regression tool and for testing on different devices.
Automation Test Analyst at a tech services company with 201-500 employees
Real User
Dec 9, 2021
We are using BrowserStack for several use cases. In our first use case, we have automated testing on the server. When you have automated testing, it uses your local browsers and BrowserStack provides the ability to integrate it with your code. Instead of using your local browsers for executing the code, it'll be executed remotely, and the integration is very easy. Our second use case was for cross-browser testing for the same automation with the script that we have. In the third use case, we were having different platforms. In some of the test cases, we were using a different browser or a combination of a different browser and the different OSs that we have. For example, we had the combination of Windows with IE, and Apple and Mac, with Safari. We did tests on many devices, such as iPhone and iPad. All the devices are available. Once we have integrated it, we were easily able to switch our testing to any of the other devices that we wanted.
We're building two products at the same time. We're building web pages and building Android and iOS applications. After the building stage, we're going to translate it to automation. But right now, we're testing and proving tools to understand which one will work best in the future.
A lot of times we use BrowserStack because we provide QA services to our clients as part of a bigger solution. We do software consulting. We use it to test across mobile devices — actual mobile devices — so that we do not have to maintain our own collection of devices. Trying to do that would be just crazy for us because there are so many devices and so many potential combinations. We test against different combinations of operating systems, browsers, and versions of browsers. For example, we continue to test IE 11, even though that is painful for a lot of our development team. Unfortunately, we still have to support it for a lot of clients. We use BrowserStack for cross-browser testing to assure compatibility.
BrowserStack is a cloud-based cross-browser testing tool that enables developers to test their websites across various browserson different operating systems and mobile devices, without requiring users to install virtual machines, devices or emulators.
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.
My main use case for BrowserStack is automating some of the test cases. A quick specific example of a test case I automate with BrowserStack is some of the application URLs.
BrowserStack is used for mobile testing. I work in web technology for logistics with BrowserStack. The environment I work in with BrowserStack is enterprise level.
I use the solution in my company for business transformation, specifically for IT business transformation projects where a customer wants to transfer their legacy applications to the cloud and modernize them using mobile apps. My company takes enterprise-level applications to the cloud.
I use the solution for performance testing.
Our clients provide us with the BrowserStack license to perform tests on certain devices. We perform mobile app testing on different devices since it is not possible for everyone to have all of the devices on hand.
The user experience is really good. We can integrate other SaaS and other stuff, like the banking service SaaS.
We use the solution for the manual testing of mobile applications.
We decided to use BrowserStack to analyze how the device works.
This has been a short-term project. We're still testing it out. We're doing functional and integration testing. Right now, the scope is not there for the screen orientation, and we're not testing that right now. We're looking at speed and compatibility issues with different versions. We're able to find some of the UI issues and installation issues. We are able to capture admin app issues and UI issues.
I use BrowserStack for functional testing.
I use BrowerStack for performing automation tests.
We use BrowserStack for testing on different platforms. It's a platform that allows us to test on different devices and platforms. We're using it as a regression tool and for testing on different devices.
We are using BrowserStack for several use cases. In our first use case, we have automated testing on the server. When you have automated testing, it uses your local browsers and BrowserStack provides the ability to integrate it with your code. Instead of using your local browsers for executing the code, it'll be executed remotely, and the integration is very easy. Our second use case was for cross-browser testing for the same automation with the script that we have. In the third use case, we were having different platforms. In some of the test cases, we were using a different browser or a combination of a different browser and the different OSs that we have. For example, we had the combination of Windows with IE, and Apple and Mac, with Safari. We did tests on many devices, such as iPhone and iPad. All the devices are available. Once we have integrated it, we were easily able to switch our testing to any of the other devices that we wanted.
We were testing it as a user interface on various systems which we manage.
We're building two products at the same time. We're building web pages and building Android and iOS applications. After the building stage, we're going to translate it to automation. But right now, we're testing and proving tools to understand which one will work best in the future.
A lot of times we use BrowserStack because we provide QA services to our clients as part of a bigger solution. We do software consulting. We use it to test across mobile devices — actual mobile devices — so that we do not have to maintain our own collection of devices. Trying to do that would be just crazy for us because there are so many devices and so many potential combinations. We test against different combinations of operating systems, browsers, and versions of browsers. For example, we continue to test IE 11, even though that is painful for a lot of our development team. Unfortunately, we still have to support it for a lot of clients. We use BrowserStack for cross-browser testing to assure compatibility.
We switched to BrowserStack because we didn't have enough devices so we moved to a cloud-based solution.