Sauce Labs Reviews

The most valuable feature is the ability to easily test multiple browsers and versions, as well as off-loading our local environments using the SauceCloud.

We're able to utilize the local server space more efficiently now that we utilize the SauceCloud for regression runs that have typically been resource-intensive.

Running tests in the SauceCloud can take longer than running in a local environment.

I have been using it for six months or so.

We have not encountered any deployment issues.

We have not encountered any stability issues. SauceCloud is great.

We have not encountered any scalability issues. SauceCloud handles all of this for us!

I have not directly communicated with customer service.

I haven't had to use technical support; documentation is great. I can usually find an answer online if needed.

We previously used a locally scaled Selenium stack.

There were some issues with our firewall and the tunnel for the SauceCloud. But we were able to overcome the hurdles fairly quickly.

An in-house team implemented it.

Currently, the biggest return has been in the ability to re-purpose local environments, previously dedicated to regression testing. Also, freeing up the engineers to work on other tasks while Sauce handles the regression across multiple browsers.

We have an enterprise account; it has worked great for our needs.

We didn't find anything that directly compared to Sauce Labs.

It's a great tool!

• Video recording / screencasts
• Very fast response from customer service
• Mobile Web, and Native Mobile Support
• Can handle massive amounts of parallel tests
• Manual testing sessions
• In-browser unit tests 

• No longer have to manage VMs for testing. No more browser upgrading and dismissing dialogs and windows that stack up.

2 years

I find that the multitude of browser and OS versions are very helpful for broadening testing scope.

Helps us free up local environment space and has freed up time for more exploratory testing with QA engineers.

I don't feel there are any real areas for improvement. As long as you follow best practices for programming automated tests and running them via Sauce Labs, then things tend to go smoothly.

I have used it for one year.

There were no real issues with deployment that weren't easily solved by reviewing documentation or having another pair of fresh eyes on the issues.

We encountered minor issues with stability from time to time but Sauce Labs continues to make improvements. Following best practices in our automated code also helps minimize stability issues.

We haven't had any scalability issues so far. We have built a fairly scalable automated framework to handle expansion.

Customer service is 10/10. Sauce Labs is quick to help and easy to reach out to for information or troubleshooting. They even make an effort to keep in touch and reach out preemptively.

Technical support is 10/10; plenty of resources to research before reaching out to tech support. As I've stated, Sauce Labs is very approachable and makes the effort to check in on you.

I’m satisfied with the services that SauceLabs provides. For me personally, as someone just learning all about implementation and exploring the tool, I have no valid complaints about the service itself. Any blockers I come across are easily solved by reviewing documentation, contacting a representative, or sitting down with someone locally who is more familiar with SauceLabs to solve any issues.

We did not previously use another solution

Setup was straightforward because we had help from employees that had previous experience. Additionally, documentation was helpful and it is easy to reach out to a Sauce Labs representative for hands-on help.

We implemented through an in-house team.

Sauce Labs helps us free up local environments, free up time for more exploratory testing, and assists in getting releases certified and pushed to production.

Try the free trial and work with a Sauce Labs representative to see what package works best for your application(s). They are definitely worth looking into and will most likely be the way to go.

Sauce Labs was implemented as a solution before I joined the company so I'm unaware of what other tools, if any, were evaluated.

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.

Sauce Labs is an amazing product for the work that I do, and there are many different solutions for testing out there. Sauce Labs in particular, I have used on many occasions within different roles and I found it to be a good alternative to options such as Browserstack. 

The most important and valuable feature is the ability to select multiple browsers and environments to test and configure how your site runs and works. This process eliminates the need for any virtual machines taking up disk space on servers, and now Sauce Labs streamlines the testing process by being able to have these virtual instances of OS and Browsers right on-demand. 

I particularly found the tabbed view of Sauce Labs useful, allowing me to have multiple browser sessions open (one for, say, each operating system as well as different browser brands) along with its clean and minimal interface. These are features which aren't found in other testing suites and are definite bonus! 

As a newbie to automation testing and having experience in using a wide range of on-demand tools, my main aspect of Sauce Labs involves using the 'Manual Testing' option, which is brilliant. You simply selected the URL and choose the browser and environment, and within minutes you'll simply have a virtual environment to play with, and it is really that simple.

Another useful aspect of Sauce Labs' product is that you can allow it to take screenshots, videos and logs, which are really, really handy. Having dealt with many issues that end users see whilst a website is being developed on, often is the case that issues are hard to replicate. Knowing Sauce Labs is there to record this (in case I can't replicate it), makes this a tool which you can share the experience with other users. 

The configuration and options within Sauce Labs are endless, which makes it an excellent product. A well-designed and minimal interface has also helped me to stay productive and keep focused on the main tasks which I use it for (manual on-demand testing and using different environments to see expected behavior for our platform).

Over time, I aim to expand into the automation area which looks great from the outset and be able to automate some tedious tests which could reduce the amount of time that I spend testing, and ensure I can continue to capture bugs and issues more effectively.

This hasn't necessarily changed the way in which the organization functions, but has added to my skill set. Currently, Sauce Labs fits very well within the other services (Ghost Inspector, Browserstack) which I currently use and it's a tool that is there for me to be able to have the flexibility to test on demand and use whichever configuration is right for me. For example, our user base will mainly be clients using Internet Explorer 10, 11 and Edge on Windows 10 or IE and, therefore, having these environments at my disposal is really handy. 

As a QA person, it is ultimately my responsibility to ensure that our product is tested on as wide a range of devices as possible and Sauce Labs helps to achieve this through the multiple environments that it offers and being able to multitask is an added benefit. 

For me, it has improved the way I function as I don't require the use of virtual machines and the headache of setting them up, and running tests on local computers meaning adding to the myriad of devices already on my desk! Streamlined, easy access to testing when I need to - that's already the benefit to me of Sauce Labs.

The main interface, although clean, is sometimes very slow to load on slower connections and selecting a machine and waiting for it to boot up the environment takes a lot longer than other products I have used. This sluggishness also increases when the user tries to navigate the environment and interact with it. Selecting Microsoft Edge on Windows 10 gave me a really slow response time and took a while to boot up. All virtual environments are expected to be slow, however the interaction between the user and keyboard presses / mouse clicks wasn't very synchronized, and often the lag that is caused distracts away from the full experience. 

Manual testing also opens up in a separate browser tab, which I'm not sure why, but should ideally load over the main dashboard. 

We use SauceLabs for Mobile, Browser and Backend testing.

Our QA requirement is to test our apps against all major browser platforms including Safari, Firefox, Chrome and Internet Explorer.

Apart  of visual and functional testing of the application components, we also collect network traffic produced by the apps for further analysis. With latest update, accessing har files got supported natively by the SauceLabs.

For mobile testing we leverage Sauce Connect tunnels as we need to connect the application under test to the corporate network and collect the produced traffic as well.

1. Achieved better cross platform test coverage for both Browser and Mobile testing

2. Frontend and Backend testing are now more connected

3. With Sauce Analytics we now use resources in more optimal way and too extensive cloud resources usage is no longer a concern

4. We no longer need to support a huge farm of mobile devices - SauceLabs Real Device Cloud works pretty well for us.

5. In some cases, like peak real device usage, SauceLabs Real Device Cloud doesn't work as well due to the delay required to release devices after testing sessions end

1. Easy scaling to multiple web platforms -> SauceLabs was the cheapest option for us

2. Support of tunneling traffic from the cloud to the enterprise network -> that is just essential for our testing

3. Video recording of tests execution process -> shortened root cause analysis time for use by 30%

4. User groups management and cloud resources consumption control -> now each group of users under our organization has dedicated pool of devices/emulators and concurrent resources access is no longer an issue

1. They still have very slow support and ask many excessive questions before starting to fix the issue.

When we submit tickets in their reporting system, we expect them to start tracking down the problem as soon as possible. Instead, it looks like they ask standard questions just to delay work to a few days. E.g. 
1st day: "Could you confirm you use the latest version" - "Yes, we do"

2nd day: "Ok. Can you then try to run that with extra flag Y and grab the log for us" - "Yes, please, take the log"

<2 days of silence>

5th day: ... - "Guys, is there any progress on that?"

and so on...

Sometimes questions are really unrelated and take time like "Have you read the Getting Started guide?"

2. They still have platform-specific issues, especially on Mobile platforms. They wouldn't affect trivial tests though.

E.g. they have issues related to SauceConnect traffic routing specific to iOS 9 and Android 4.

This affect tests that want to sniff the traffic only though. Please, let me know if you want more technical details.

3. Sometimes they change configuration options (e.g. rename...

E.g. recently they changed desired capability for iPhone Simulator in a way like "iPhone 6 simulator" > "iPhone 6"

That affected multiple tests suddenly. They haven't made any notification about that though.

I believe, for more than 7 years already

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.