Save time save money move over to cloud using Sauce Labs from Selenium grid
Updated November 17, 2017
Save time save money move over to cloud using Sauce Labs from Selenium grid
Score 9 out of 10
Vetted Review
Verified User
Overall Satisfaction with Sauce Labs
We heavily use Sauce Labs as our testing platform for running our automated tests in QA department. Also, we have extended the usage of this for the development team to run their unit tests/bug fixes on multiple browsers and platform before pushing it to our QA environment. Prior to this, we were maintaining our own grid for running automated tests, the less knowledge and more efforts/cost of the resources made it hard to scale and maintain our own infrastructure. Moving to a cloud service like Sauce Labs we are quickly able to run the tests and scale our testing on multiple platforms.
- Good support
- Recommendations for fixes/bugs are heard and they come up with the fixes very quickly
- Better resolution of the AHA requests, their portal for handling feature requests and experience
- More integration with open source tools/projects like JIRA on cloud
- Need lower price options on usage vs. number of VMs
The exceptional good customer support really made us go to Sauce labs vs. BrowserStack.
Evaluating Sauce Labs and Competitors
- Price
- Product Features
- Product Usability
- Vendor Reputation
In order to move to any new platform or services it is important to have good support from the vendor, and i had a faster support service to support my decision of buying the service
I will go ahead and evaluate the needs for the business and then lay down the pros and cons of each service provider to see which one gives the maximum benefit with minimum expenditure, also the key thing is to make sure how the future of the product/service you are buying going to be, maybe talk to the vendor about their vision the next things they are going to implement for future and getting the feedback from the users will be important
Using Sauce Labs
8 - Test automation engineers
- Ability to quickly run the automated tests on multiple browser and platform
- Easily integrated with CI builds
- run the tests earlier in lower environments behind firewall using sauce connect rather than waiting to deploy on public facing domain
- By embedding the sauce labs results into Jenkins build job to easily troubleshoot the failing tests
- Executing the script which kicks off the sauce connect for an account that can easily be used by the manual testers or anyone on the product side who wants to access the web application behind firewall without setting up sauce connect on their machine
- Running the tests on real device over emulators manually + automated fashion
- Ability to setup the device/platform before kicking off tests for eg. downloading the flash or more extensions
- Performance testing of the front end
Sauce Labs Support
| Pros | Cons |
|---|---|
Quick Resolution Knowledgeable team Problems get solved Kept well informed Quick Initial Response | Difficult to get immediate help |
Yes - Sometimes yes sometimes not
Using Sauce Labs
| Pros | Cons |
|---|---|
Like to use Relatively simple Easy to use Technical support not required Well integrated Quick to learn Convenient Feel confident using Familiar | None |
- Reporting, its easy to integrate the reporting of results using Sauce REST API and there is good documentation on their wiki site
- CI integration is pretty easy
- Easy to setup sauce connect proxy using their new FF extension
- For initial setup of running the sauce connect to run applications behind firewall when running the tests from local using command line is a problem, and also without support of FF extension(to create sauce connect proxy) not available on all versions its tricky
- Sending the pass/fail status for the test executed on Sauce is little bit challenging when initially using the Sauce labs
Yes, but I don't use it