Sauce Labs Reviews

• Able to test in different OS and browsers

It improved our organisation by reducing escaped bugs.

• Provide an automation framework suite for basic websites

I have been using it for the last year.

Sauce Labs is valuable to my job for the multitude of devices and browser/OS combinations they provide for real device testing. I am able to eliminate the part where I have to find a human with that device or browser and have them test (potentially not even do that correct), and do the testing quickly at my desk. It also allows Selenium script testing which eliminates more human error.

It has improved our organization by testing our website on more devices and browsers that what our company currently owned. We were able to test on the newest browsers without installing them on our computer, or testing the newest OS without having to update our mobile devices.

It would be nice if they could ask for the URL and what browser/OS I want to test in, but not just one combination, I want the ability to start up 10 concurrently at a time. I would also like to put in a username and password before the launch of the test so it will auto put those in all on 10 instead of going into 10 tabs and having to put the same information over and over again.

Our company has been using SL for almost 2 years now in my department, and several more years in other departments.

Initially there was some stability issues with IE9 combos but have since been resolved. They have excellent customer service.

Customer service is top notch. When you report a bug or inquire about something they get back to you with a plan of action, not just "ok we will let our team know". It's refreshing having a company that wants to work better for its customers.

Previously we used BrowserStack, but since they couldn't comply to our legal terms we were able to find Sauce Labs and are better for it.

Sauce Labs was very easy to use for it's basic needs, but using Sauce Connect was very confusing. I am a technical person, but the documentation needs to be a little more "dummy" friendly for nonprogrammers. This sites documentation is really more geared for the software engineer rather than the Qa Engineer in my opinion.

Cross browser/OS testing and mobile testing.

We work on a complex SaaS web application which has lot of regression testing. If we were to run all our tests on different browsers/different OS combinations, we would need lot of new infrastructure and VM's. But with Sauce labs, we were able to use Remote WebDriver and connect to their VM's which have all the combinations we are looking for.

We still see simulators for a few mobiles in their VM's, we want to test on real devices. 

Wide variety of platform and browser configurations.

Sub-accounts allow multiple teams to test concurrently.

Documentation and speed.

With only a few months of service under our teams belt, it has been nothing but excellent. We joined during the web interface transition and it is a more enjoyable experience. Once tapped into their API, our testing suites contain reliable information we can validate across the platform, switching between Sauce results and our own. This obviously makes troubleshooting much less daunting. Their documentation system is much improved. We rely on their services for mobile iOS and web testing across several projects.

With the rebranding and a focus on providing physical device testing. Sauce seems capable of being a top service provider now and into the future.

We run eight virtual iOS simulators with our suite of over 280 feature tests. Parallel runs reduce our total execution runtime to a little over 2 hours. By adding some clever logic into our driver class for Sauce, we can send tests to random device configurations to achieve greater coverage without running the entire suite against every device. Interacting with the API makes this easily possible. We don't need to use Sauce Connect and perform each session configuration within our driver class.

The only caveat to mention, is the availability of the next release of iOS on their systems. Their adoption seems a bit slow. I understand Sauce is making an effort to enhance their current infrastructure to make updating to the latest iOS release easier in the future.

Been using Sauce Labs for a couple years now, and to say the least it's a lot better than managing my own farm of VM's.  Having the capability to run in parallel against various types of OS's/browsers/mobile-devices is great as well.  Looking forward to glancing at RDC (Real Device Cloud) and seeing if that provides a better solution as we run our mobile tests on slow emulators.

Sauce Labs, for the most part, has very little to no down time, so our tests are running in parallel all through out the day and night.  It's great to go back and view the videos of our browser tests to first see what is going on, and then search the log and output files provided to narrow down the issue even further.

I think their logging could be improved a bit, possibly to include the output that I see on my command line (print statements, etc.) which help pin-point the error (if one happens) more easily. 

Sauce Labs is great in that you can spin up a virtual machine of one of many different configurations and quickly get your test up and running.  After, you have a great report of the test status along with screenshots, video and other meta data about your test.  To do this in house would be way too time consuming and costly.

Quickly running multiple OS and browser combinations with ease.  What more needs to be said?

Not really sure.  Maybe a .NET test runner option?  This may or may not already be in place, but I know it wasn't the last time I checked on it.

Sauce Labs has a test runner available for Ruby or some other language other than .NET which allows users to execute their tests directly from it.  This would be nice to have for .NET, as well.  Currently, tests are started locally and then they are run on Sauce Labs.  It would be a nice option to have it all started and executed on Sauce Labs.

Being a cloud based testing grid is really the key feature. But inside the product the killer features for us was the new CI dashboard of test results, and the recording of bugs into JIRA.

We are small. Most small dev teams do not consider testing as much. But this is exactly why we needed sauce. Quality was priority from day one. And with only developers the only solution was automated testing, and a test grid we did not have to manage ourselves. We choose Sauce because of it's popularity, but also because they have a good relationship with the market and show their interest in helping the market get better with test automation.

I would like to see it work directly with Azure Web Apps so that we do not have to have a separate step to run tests, or setup complex flows in Jenkins.  

Because our application front-end runs one Azure Websites which is a PaaS solution, we do not have server access and this makes it challenging for use to work with some external tools. I would like to see sauce labs have a direct integration with Azure Web App slots. This way we would not have to make the test runs a manual step. Currently we initiate tests manually and if they pass we do a manual promotion from an Azure Web Slot. We could integrate Jenkins or other release automation tool, but this would be additional overhead on top of what Azure provides out of the box. Another way to do this, instead of a direct integration with Azure. Is if their was a way to run tests in Sauce upon ever commit of a specific branch in GitHub. This way we could have a branch just for automation, and would not need to involve Azure Web App slots at all.