BrowserStack Reviews

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 haven't seen AI in BrowserStack, making it in an area where improvements are required in the product. Accessibility testing is an area of concern where improvements are required.

For my project, we utilize a VPN and BrowserStack for testing. This allows me to test our website across various browsers and platforms, including different versions of iOS, Android, and web browsers. It ensures that our website functions correctly across different environments and devices.

BrowserStack has been incredibly useful for our mobile testing needs. One scenario where it proved its value was when I needed to test a new feature across different devices and platforms. I utilized BrowserStack's emulator with real devices feature, selecting specific devices such as iOS devices like the iPhone 14 with different versions like 16 or 17. I could easily switch between devices and versions to simulate real-world usage scenarios. This flexibility allowed me to thoroughly test our UI and ensure compatibility across various devices and browsers, providing a reliable testing environment even when facing connectivity issues.

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.  

It allows us to test our development against a huge range of product combinations that we could not realistically maintain in house. It really adds to our core capabilities.   

I use the solution for performance testing.

The issue with the product stems from the fact that when we try to do a single or multiple login on multiple browsers for simulation in scenarios where users use Chrome, Mozilla, and Edge, all browsers are open at the same time, and login has to be done separately. My company has added a minimum of two and a maximum of five users to the license. In my company, when all of us start device testing at the same time, one of the devices stops working, or some slowness or lag happens. There is some stability issue in the product, making it in areas where improvements are required.

We use the solution for the manual testing of mobile applications.

The most valuable feature is the variety the solution offers around the different types of devices, especially mobile devices. 

The solution's UI is intuitive.

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.

The integration is very good. 

Support is very helpful. They'll even let you extend your test license.

It has been issue-free throughout the POC phase. 

Access has been very seamless. You can access it from all kinds of devices. 

It offers very good performance.

The stability is excellent. 

It's stable.

The solution isn't too costly.

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.

The solution has many benefits, we are not worried about maintaining devices locally in our organization. This is one of the biggest benefits. Any device that is new in the market, or any phone or OS that is launched the new version is always available. We are never worried about having access to those. In the real world, you have to buy those new devices and you have to go through a lot of processes to maintain them.

Mmaintaining the devices is the largest task. All the devices have to be checked physically for many things, such as charging. While someone else might need a device but not be able to have access when it is a physical device, there are limitations. With virtual devices, everyone can have access right away, they can log in and start using the device.

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 have some requests from our users telling us that something's not working with their device and it's easy to find the bug if the user is going to provide us the OS version and the device that they have. We can go to the specific device and OS version and check it out on our end. Without BrowserStack, it could be difficult to do.