Sauce Labs Reviews

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.

In my previous company, we used Sauce Labs to enable the team to test with various operating systems and browsers without having to own each of them. 

Their product gave us the ability to run multiple teams of testers across the various platforms that would be used by our customers without having to physically have the infrastructure in place. This drive our movement into continuous integration and the ability to test earlier in the cycle.

No

over a year

No. It was very easy to install and implement from day one. 

No

No

Customer service from the initial query to sauce labs to the product evaluation to contract negotiations to purchase and installation was seamless. They are so accommodating and easy to work with and this allowed us to go from initial discussion to implementation in what I would consider one of the shortest timeframes I've seen with a new product. And I have seen many products in my 21+ year career.

No

It was very easy and we were up and running the product the same day.

Purchased and implemented directly through Sauce Labs.

High but I cannot disclose value.

Very low but cannot disclose amount.

No

No

My primary use case is for cross browsing testing of the largest eCommerce site in Latin America.

Sauce Labs gives us the availability to use any browser and OS combination whenever we want, with only a few clicks. This is very useful for our IT department. It is also used by our customer experience and marketing departments to reproduce some issues detected by our customers.

• Real devices (Test Object): It is very important to test everything on real devices, not only in simulators.
• Analytics: It is important to know what, when, and where tests are falling, then improve them and the application.

An image comparison would be a nice feature to include in the Sauce Labs product. 

It's ability to test on multiple browsers and OS combinations is invaluable as a QA tool. However, it's CI integration with Jenkins is why we were able to make a case to include this product in our ATDD process.

This has helped greatly as our organization switches from a waterfall method to an Agile method of software development. The transition is difficult and hectic at times, as it requires a big change in the way we think about, and treat the development process. Sauce Labs, which blends seamlessly into Agile and ATDD processes, has made the process much smoother from a QA perspective.

Rarely, some tests fail, seemingly without cause, and will succeed again the next time we run the tests. This isn't a behavior we saw when testing locally.

I've been working in QA for about 6 months now, and began using Sauce Labs about 3 months ago.

We have not deployed yet, but we see no signs of issues in the future.

None so far.

I have yet to engage their customer service directly, but the support pages are full of valuable information. Maybe it could use better organization, but it's there..

We have a Sauce Labs admin at my company who deals with tech support, I have had no experience with them. However, after an initial hiccup when they were setting up tunnels so that we could test internal apps, I have seen no technical problems.

I am new to this QA position and after doing research, Sauce Labs was my first choice.

As a brand new hire, I cannot speak to how easily a seasoned QA role would see initial setup. I was learning Selenium while trying to setup Sauce Labs, and the materials were not so straight forward as to make the process easy for someone so new. It took me a few weeks to really get the hang of things, but I'm confident initial setup on a new project would be simple the next time.

I am a user in my company, I had no interaction with the vender.

The on-demand provisioning, the multiple operating system and browser choices (including multiple versions), as well as the really nice screenshots and videos, as well, are key.

Having full logs, with videos and screenshots, has really helped us work more closely within our own team, as well as, more importantly, being able to show developers (automatically!) what the precise problem is.

Since around August of 2011

Integration with Sauce has been a breeze for us here at Mozilla.

At various times, there are high-latency launches, or outright timeouts, but the Sauce Ops team has been pretty good about both 1) acknowledging the issue/investigation 2) working steadily to resolve it.

At times, the brief outages or slow service responses have temporarily hampered our fairly large (in terms of concurrency) test-automation runs, but that's not very often.

Sauce support has been very helpful -- always friendly, pretty prompt, and thorough, too -- even when it's not always a direct problem with their service or our usage of it.

For our needs, the customer service and technical support come through the same channel, and we've been very happy with the level and quality of responsive support we receive.

Being an open-source organization, we wrote our own custom plugin to handle integration of both our in-house Selenium Grid as well as Sauce Labs (https://github.com/mozilla/pytest-mozwebqa), and although I didn't personally do any of that coding work, can attest that the APIs Sauce provides have made it pretty easy for us to do that integration and setup work.

We are lucky to enjoy Sauce Labs's "Open Sauce" program, as an open-source, not-for-profit organization: https://saucelabs.com/opensauce

We did look (back in 2001) at other vendors, but found the business side and open-source/project relationships fit well with us.

As a disclaimer, I have done a number of Selenium Meetups with Sauce Labs, as well as a few blog posts which have covered our usage of the service, as well as, finally, authored a Featured Customer case study, in which I expound on nearly all the points I've made here:

https://saucelabs.com/customers

• Running tests in parallel
• Sauce Connect Proxy tunnel
• JIRA/Bamboo plugins

Enables faster execution of regression tests without having to support/maintain the software needed to validate regressions against different devices, OS, and browsers.

Speeds up the time it takes to run end-to-end user interface (UI) tests inside their virtual machines (VMs).

Less than a year.

None yet.

Not yet.

Not yet.

Excellent, so far.

Excellent, so far.

Yes. We built and managed all of our testing infrastructure in-house.

Pretty straightforward, except when you begin working within an enterprise organization that operates nearly all of its web applications behind a firewall. To get our automation running inside Sauce Labs's infrastructure, we first have to install and configure the Sauce Connect Proxy server. The complexity of setting up the tunnel comes mainly from the protocols our organization has for getting the approval to implement Sauce Labs behind our firewall. Explaining the details of the tunnel, why we need Sauce Labs for regression testing, and facilitating the connection between our Server's team with a Sauce Labs technical resource were all fairly complex.

In-house.

It is difficult to estimate at this time.

Start small, even if you are a large-to-enterprise level organization. The setup cost, if you're an enterprise-sized organization, is negligible. Establish a few quick and easy "wins" for one or two product teams. Hold a post-Sauce review with all the stakeholders within each team with the goal of reaching a consensus on whether the product is a good long-term fit. If the answer is yes, then calculate ROI, and if it makes sense, scale up and spend the money so every product that should use Sauce has access and the correct bandwidth.

SmartBear, Perfecto, and Ranorex.

The session duration is too short; it's only about 3 hours long.

We haven't had any issues with deployment.

We haven't had any issues with stability.

We haven't had any issues with scalability.

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.