Browserstack: A Cross Browser Testing Platform
What do you like best about the product?
- Enables us test pages on variety of devices and browsers.
- Testing with browserstack provide better accuracy than emulators
- No setup required
What do you dislike about the product?
In terms of what we do fo rmanual testing, browser stack works great.
Their automated visual testing isn't great yet.
Percy is the tool that they have for automated visual testing. It is good for testing a few sets of pages, but not quite there yet in terms of easiness to integrate to our automated test jobs via jenkins/github actions.
What problems is the product solving and how is that benefiting you?
It solves the problem to us needing to test on multiple actual devices. People can test on multiple devices even when they are working from home (wasn't possible if we wanted actual devices). Also it helps us not rely on emulators anymore.
Thus, It saves a lot of time, and helps us release things with confidence.
Can be very helpful for testing but has some drawbacks
What do you like best about the product?
1. Wide selection of devices and OS.
2. Real device testing.
What do you dislike about the product?
1. Limited control over the testing env and devices.
2. Application tends to freeze a lot during testing and required reload that consumes a lot of time on restarting and retaking steps - probably the biggest downside during work for me.
3. Challenging to set up testing if you are on VPN.
4. Observed UI issues on BrowserStack devices but did not observed same UI issues on real devices with the same OS.
What problems is the product solving and how is that benefiting you?
Allowing access to multiple devices with different OS versions for testing across browsers and devices.
Effective App Accessibility Testing, Detailed Reports, at Times Poor Customer Support
What do you like best about the product?
App accessibility testing was a breeze, created nice and detailed reports that were easily presented to other teams. Showed problems, action items and descriptive outcomes.
It was very easy to start testing, using the virtual machines to replicate physical devices. Made using this for 4 testing sessions quite simple.
What do you dislike about the product?
Certain times the app testing would freeze, and I would lose an hour of work that I spent testing, there seemed to be no workaround for this, and when contacting support they were unhelpful. They claimed my account did not have access to a product I was using, even though I sent screenshots of me using the product.
What problems is the product solving and how is that benefiting you?
It gave us a detailed report in terms of our current app accessibility, which we could then take back to tech teams.
Easy-to-use and practical software
What do you like best about the product?
The simplicity and ease of use of the software
What do you dislike about the product?
Sometimes it seems that certain functions, such as localization, don't update automatically.
What problems is the product solving and how is that benefiting you?
I use browser Stack as a virtual machine, which is very useful for the cost.
Low code is very easy to manage and understand
What do you like best about the product?
Easy work flow to record and run test cases
What do you dislike about the product?
adding java scripts where the flow is not working
What problems is the product solving and how is that benefiting you?
Helps in maintaining low code automation and and regression test management
Browserstack is a good cloud provider for testing web and mobile applications
What do you like best about the product?
Browserstack is an easy to use cloud provider for testing web and mobile applications.
What do you dislike about the product?
Browserstack has limited mobile physical devices. Also it doesn't have Test Automation flow from the scratch even though it has device firm e.g. I have to upload a project to start Test Automation with appium but if I could start from scratch then I would start building it here already with my limited programming knowledge. Browserstack could also inlcude AI to assist with Automation flow.
What problems is the product solving and how is that benefiting you?
Currently I am just using physical mobile devices to test our mobile applications.
Streamlined testing experience with valuable features but high costs prompt a look into alternatives
What is our primary use case?
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.
What is most valuable?
Some of the best features with BrowserStack include the ability to inspect network traffic, and the device farm is nice. They offer using two devices at once, but it's a tier that we don't pay for.
Cross-browser compatibility testing is important for my organization and I think it's essential for all organizations since they don't necessarily control the platforms that their clients access their services from.
BrowserStack's wide array of real devices and browsers has helped us address the need for devices, but we don't use them for web testing. I have used BrowserStack for live interactive testing, and it has helped identify and resolve errors during development processes.
It gives me access to devices that I don't have to purchase, which is nice. Being able to manually use a real device, or alleged real device, becomes important because there's a huge difference between testing on a simulator, emulator, and testing on real devices due to how apps get packaged and how things get moved around during the packaging.
I don't really test the feature that simulates various network conditions too much, but it has definitely come in handy. I generally would use something more a proxy, such as Charles, if I'm doing something that. I have the ability to manually do that on the devices that I have locally, so I wouldn't really do latency tests with connectivity speeds across the wide array of devices that they have.
They have an API, which is super helpful, and it is integrated into our pipeline, which helps because that's where our automated tests run. The device farm is one of the positive impacts we have seen from using BrowserStack. We get to run our automation against their full suite of devices, which alleviates the uplift of manual testing. This speeds up regressions, which speeds up our deployment process, allowing us to get updates to customers faster.
What needs improvement?
In terms of improvements, they can make it snappier. Everything kind of works. They have locked down the phones, which is problematic because there are some test cases that require access to things that they don't give you access to, which is understandable. However, being able to have more granular access to the OS would be a good feature.
BrowserStack is very expensive and they keep increasing their cost, which is absolutely ridiculous, especially when someone like LambdaTest is coming through for literal thousands of dollars less, with the same services.
The amount of what LambdaTest has to offer for their price point seems to be a better financial choice for any company at this point. I haven't used LambdaTest yet; we are exploring options with other providers at this time, and LambdaTest has been the only one that's provided any kind of cost-saving benefit while not losing any of the functionality that we expect to have with these products.
BrowserStack is really expensive, which is super annoying. Anytime you want something new, it costs an exorbitant amount. We just attempted to increase our seats and they wanted almost double what we were paying, which was insane because it wasn't double the seats. Companies need to make money, but they also need to work with their customers because otherwise, they'll lose them to competitors like LambdaTest who offer similar services for significantly less.
How are customer service and support?
I haven't had any issues with their customer service, so I would rate them around a 7.5 or 8.
How would you rate customer service and support?
How was the initial setup?
The initial setup with BrowserStack is actually pretty straightforward. We use WDIO, which you can integrate the capabilities directly into your WDIO configuration file. We wrote some bespoke code that does some checking of BrowserStack threads and stuff that they open up via their CLIs, so it's pretty simple to integrate. I'm going to be exploring how these other services compare in terms of integration.
What was our ROI?
There is some return on investment because it saves us time during regressions and allows developers to access real devices without having to purchase them. However, I don't think the cost point and how much devices cost versus what we get out of BrowserStack is necessarily equal. I think its biggest benefit is how it integrates with our CI/CD, not necessarily giving access to developers for test devices.
I have recently pushed to allow our operations team to get access so when they talk to customers, they're able to access devices and try to recreate the scenario they're experiencing. This is beneficial, but I believe LambdaTest also offers similar features like App Live and App Automate.
Regarding time savings during regression, that's a tough question. It really depends on the regression. For instance, if 80% of the functionality is tested via automation, then I only have to do 20% manual testing. If a full regression takes a week, I only have to do 20% of that due to the automated tests. However, I still need to go manually verify when conducting a full regression because buttons can exist but still look really weird. It's not simple to do visual testing in line with functional testing, so I lose that benefit; hence, I must manually verify all the pages and navigation.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
A Reliable Cross-Browser Testing Companion
What do you like best about the product?
What I like best about BrowserStack is the instant access to real devices and browsers for reliable cross-platform testing. It integrates smoothly with CI/CD pipelines, speeds up our QA process, and eliminates the need for a physical device lab.
What do you dislike about the product?
What I dislike about BrowserStack is that performance can occasionally lag, especially during peak times. Also, some advanced debugging features are limited compared to local environments, which can slow down issue resolution.
What problems is the product solving and how is that benefiting you?
BrowserStack solves the challenge of cross-browser and cross-device testing by providing instant access to a wide range of real environments in the cloud. This eliminates the need to maintain our own device lab, saving time and resources. It also helps us catch bugs early across different platforms, speeds up our QA cycles, and ensures a more consistent user experience for all users.
Lean Applications Requiring Low Network Traffic, Testing with BrowserStack
What do you like best about the product?
I liked how there were plenty of options and OSs and browsers to work with
What do you dislike about the product?
Sometimes the system felt laggy or slow, but otherwise it was pretty good. The touchscreen features also struggled at times to work properly
What problems is the product solving and how is that benefiting you?
I like that I can see whether the application works on all different platforms. Our end users are often not using fully up-to-date browsers, so we want to make sure our app works across all platforms.
good experience in browsing with multiple android and apple devices
What do you like best about the product?
users have some many options of Android devices and apple devices.
What do you dislike about the product?
I ever try to do testing using browserStack to simulate operation in mobile devices. However, the effect is a little different from real devices.
In addition, not some options in some smart phone brands: oppo, vivo, xiaomi, huawei
What problems is the product solving and how is that benefiting you?
There is some difference in using between BrowserStack and real devices.
I could access to different devices and different size of viewport.