Sauce Labs Reviews

We use the Sauce Labs test automation VMs to help our quality assurance engineers run automated tests concurrently, using a platform that we build in-house.

We use the browser VMs and we definitely use it for end-to-end testing. We may use it for performance testing, as well.

The way that we use it is pretty straightforward.

This product is a big time-saver, so by extension, it's a cost-savings.

It's helped us remove the need for extensive manual testing, which is how it's freed up a lot of time for quality assurance engineers to work on other things. They can work on the automation itself, for example, whereas otherwise, they'd be spending all of that time doing these tests manually and synchronously.

Sauce Labs is optimized for automation and intention with major CI/CD platforms and developer tools. In our case, we've plugged it into our pipelines quite easily. It's an integral tool in that regard, so it is very important to us that it is optimized for integration.

We run Sauce Labs with almost every code commit.

Although Sauce Labs is a cloud-based solution, latency has not been a concern for us. We haven't run into any situations where latency is causing any major issues.

The most valuable feature is the ability to run concurrent automated tests up to a specified value, depending on what we are currently paying for.

I am pretty satisfied with the options in terms of the number of browser and OS combinations they support, as well as the number of real devices, mobile emulators, and simulators. I haven't had any needs that they couldn't satisfy. This enables us to ensure the quality of our products, cross-platform.

A really nice feature would be a pay-as-you-use model, as opposed to a strict number of VMs that you pay for continuously.

I have been working with Sauce Labs for two years and nine months. It has been used by the company since before that.

This product is not super scalable, because you have a very specific number of VMs that you can use. If there was a pay-as-you-use-it model, I think that would really increase the scalability of the solution, but right now Sauce Labs is a bottleneck because you have a specified number of VMs.

We use, on average, 75 of their VMs per hour. Optimally, we're using as much of the VMs as we pay for. As such, the goal is to have our tests running often enough to maximize that usage.

I can't speak to how widespread this product is used in the company, although in my team, there are 10 of us using it. My team is serving between 30 and 40 quality assurance engineers. Other teams in the company are also using it.

I have not personally used Sauce Labs' technical expertise to assist us with integration or for implementing solutions, although, in the past few years, I've submitted a couple of trouble tickets based on some technical difficulties.

I found the technical support to be great and timely. I haven't had any complaints, and the issues have been resolved.

I don't have any experience with other similar technologies.

I was not with the company when it was first implemented.

We pay for a specific number of VMs. The licensing model should be changed to pay-as-you-use, which would make it more effective.

The biggest lesson that I have learned from using Sauce Labs is that concurrency and automation save a lot more time than you initially think.

I would rate this solution a nine out of ten.

We use Sauce Labs in our CI/CD pipeline for our mobile app.

I work on the team that develops the mobile application for Discover, and we run about a couple of thousand tests per day on Sauce Labs devices. Whenever our developers are contributing code to our application, we'll run a bunch of tests on Sauce Labs devices, and every night we run a full suite of 1,000-plus tests on those Sauce Labs devices.

It saves us a lot of time because Sauce Labs provides us with plenty of devices, enabling us to run 1,000-plus tests in parallel. As a result, we can get it done pretty quickly. Typically, testing would take six days, and we got it down to one day. That's how much we're saving.

Also, because Sauce Labs provides tons of different devices, instead of relying on a small number of devices on-premises, we can rely on Sauce Labs' cloud and run tests on all sorts of devices. That can include things like an old Galaxy S7 or a newer Galaxy S20, as well as different operating system versions. Sauce Labs has all of that and we can test all sorts of different combinations of devices and operating systems.

The most valuable part of Sauce Labs is its virtual devices, simulators and emulators. They can spin up hundreds of them as soon as we want them.

Something that needs improvement is the speed. Relatively speaking, it's slow, but that's because we are communicating with the Sauce Labs cloud service and, obviously, there are network delays. We're hoping that in the future it can just be a bit quicker.

Another aspect that could be improved is having the virtual devices boot up a little quicker. Sometimes we wait up to a minute before a device is available. It would be nice if that was 30 seconds or so.

I have been using Sauce Labs for about a year.

The availability of Sauce Labs is really good. There have only been two occasions that I recall it being down, and that was specifically for their Apple devices. Other than that, there has been almost 100 percent uptime.

We have no complaints about its scalability. We're able to scale to 100-plus devices, and I'm sure Sauce could provision 200 or 300 in the future. I don't see any issue.

At this point, we have about 40 people working with the solution, and they're primarily application engineers and quality assurance people.

Their support has been great. When I submit a new help ticket or a request, they usually respond on the same day, by the end of the day, or the next day. Sometimes tickets do linger a bit and they take some time to become resolved, but most of the time our issues do get addressed and resolved within the week, which is nice.

Positive

We used a service called SeeTest for a couple of years. We switched to Sauce Labs because it seems to be more up-to-date with the technology. They upgrade more often, which is something we wanted in a cloud service. In addition, we use a special testing tool called Appium, and Sauce Labs is actually an active contributor to that open-source program. We thought using Appium and Sauce Labs would be a good pairing of wine and cheese.

The initial setup of Sauce Labs was really straightforward. We only required credentials, and one or two other bits of data, and then we were able to connect and run our tests on their devices. There wasn't too much setup or configuration.

Our company has absolutely seen return on our investment in Sauce Labs. Whereas before, we were relying on physical devices we had at our headquarters, or we relied on SeeTest, which has limited devices, with Sauce Labs, we have a whole universe of devices: Galaxy, all the iPhones, and all the operating system versions. All our software developers are able to test on a multitude of different devices. That gives us more confidence that our Discover application works on old devices as well as new, obscure devices. And that is true for our quality assurance as well. My QA colleagues are able to test on way more devices than they were before we had Sauce Labs.

I'm not involved on the financial side too much. I forget the exact numbers, but being in the industry, Sauce Labs' price seemed high. I don't remember what our SeeTest contract cost, so it's really hard to compare.

When we switched over to Sauce Labs, we didn't really look too deeply at other cloud service providers. There were two or three others, but we never engaged with them or talked to them because we saw pretty early on that they weren't exactly right for us. We saw that Sauce Labs fit the bill.

The main differences between Sauce Labs and the others were the number of devices available to us and the user interface. Sauce Labs has a really nice interface. And the overall impression we got from Sauce Labs was that they're very up to date and that they keep up to date all the time. They don't fall behind. They always have new features coming out.

Don't expect tests to be quick. That's something that's not only applicable to Sauce Labs but to all cloud service providers. The testing is going to be a pretty slow process. That advice is specifically for developers who are developing solutions.

We have been using Sauce Labs to test various browsers and OS combinations as well as test our applications. Our existing automation scripts are written in various technologies, which could be Java, JavaScript, Selenium, Cypress, etc. Jenkins is the tool that we use to typically run our jobs. Through Jenkins, they get scheduled and run in Sauce Labs. This is where we choose to run them, through various browsers and OS combinations.

We use Sauce Labs core and whatever services that we choose to go with, like browsers and mobiles. From there, we can choose the browser and OS versions, etc.

Without Sauce Labs, we wouldn't be able to test as quickly or simultaneously on various browsers. That is the capability Sauce Labs has brought to us.

The automated functional testing, visual regression testing are pretty important to us, as those are the use cases for which we use Sauce Labs. Specifically because it is hosted in the cloud, we don't have to use as much capacity from our own servers. We don't have to maintain and install various versions of browsers nor do we have to maintain them. It is a good solution and works well for us.

Most of our teams who have solutions to test on mobiles are using the solution's mobile emulators and simulators. Having that availability is very important for a complete testing experience.

We use the solution's emulators, simulators, and different browser version combinations for all our testing. For every release, we validate across various browsers. If it is a mobile application, then we need to validate across various Android and iOS devices as well as the previous few versions of each of the operating systems.

The customer base that we typically serve is vast, diverse, and varied. This makes it very common to have our applications used across various applications, systems, and screen sizes. To test across all that, we needed a system in place. That is why we are using Sauce Labs. Without it, we would either develop something in-house or rely on possibly testing in only one particular system. For example, with Android, our entire customer base who is not Android wouldn't be able to validate and reproduce the user experience.

When we are doing releases, the releases happen across all teams and various services. This means all of them need to test for a particular release deployment in whatever environment simultaneously. Based on the number of concurrent VMs that Sauce Labs provides, we can add or reduce VMs as needed. The amount of concurrency that we have purchased is specifically to support our various teams to do deployments simultaneously. Doing these simultaneous tests has reduced our test execution time.

There are a lot of analytics that you can do and look at when you run your jobs. It also gives you how much throttling has been seen across various teams over the past month. It tells you which particular line of code has been failing for however many runs that you have done. 

The concurrent usage and VM availability are its strengths. We have found concurrent throttling very useful. So, we know exactly which job or team is using more than their capacity and might need additional capacity.

We have also found the code analysis that gets run on Sauce Labs very useful. It tells us the line of code that has been failing or not received a new command.

Sauce Labs is optimized for automation and integration with the major CI/CD platforms and developer tools. Most of our teams are creating CI/CD pipelines. Some of our teams do many deployments in a day. Without CI/CD, that pace is not possible. Having that capability, for whichever automation tool that we go with, is critically important for us.

Some of the trends that it shows. It only allows you to view the last month. Having it go beyond a month, e.g., yearly trends, would be good. While the yearly trends are available, they are available to Sauce Labs administrators, who are internal to Sauce Labs. I don't know if they are available for customers yet.

My teams use it. I have about eight or nine teams and most of them have been using it at least for a year. Since I joined the company a year ago, I have been watching it being used.

The stability is good. I haven't seen any issues with it. We haven't experienced any latency or downtime issues.

It has been pretty scalable. We are looking at increasing some of its concurrency capacity.

We are currently using about 40 to 50 current VMS.

One part-time resource is primarily needed to design the user groups where jobs will be run. Initially, we had all of our jobs run under a single user name, but then we decided to segregate that and divide it up amongst the teams. So, one part-time resource is needed just to analyze and manage how your jobs get run, then analyze the trends after that.

The technical support has been pretty good. We haven't seen a lot of technical issues in which to engage their technical resources. Occasionally, we used them when we couldn't see something, didn't have an admin account, or for account creation. All those things got resolved very quickly, maybe in a day or so. I would say the technical support is good and rate it as 10 out of 10.

Positive

It was implemented before I joined the company.

It was already set up when I joined the company.

From an infrastructure support perspective, the number of VMs, browsers installations and versions that we would be maintaining without Sauce Labs would be a lot. This includes not only the infrastructure costs, but also the maintenance costs and people's time. The labor cost associated with maintaining all of that would be considerably high. In terms of efficiency, having concurrent VMs with various browser combinations available has allowed us to run multiple executions by all our teams.

Typically, in a night, eight or nine teams have 40 to 50 jobs running simultaneously, which is amazing. Otherwise, if that was not concurrent, then it would have to be maintained in our own infrastructure. That would be a lot of money.

Sauce Labs has room for improvement with its price point. Using a real mobile device, and having that dedicated to your team, costs more than actually purchasing a mobile device. We haven't tried the real devices yet. This is because of their price point.

The number of concurrent VMs that Sauce Labs provides depends on your purchase license level.

Latency has not been a concern due to Sauce Labs being a cloud-based solution. This comes back to the number of VMs and licenses that you have purchased. For example, if I have a capacity of 70 VMs, but I am running 100 jobs, then 30 of them will be throttled and we will see the latency. However, if I were to up my licensing, then I wouldn't see that latency. That is why it just depends on the license tier that you have ordered.

I have not compared it with other solutions.

Plan for how you want to use it and how many teams will be using it as well as the types of accounts that it makes sense to have, different access levels, and who should have it on their team. If you plan ahead, then you don't have to fix it afterwards.

We haven't tried the front-end performance testing.

I would rate it as eight out of 10.

We use it for a lot of end-to-end UI test automation.

We really just use the visual test automation, not the performance, for our product teams.

There are a couple of products using this solution, so it has been nice having a visual result. We can step through the tests, if necessary, and showcasing to the business that we are doing automation has been very helpful.

I like the dashboard and seeing the test results. As a manager, I like to see the insights of the people using it, understanding the total path and run. I can see all of that as a manager. I also know team members love seeing the dashboard and seeing the test results in real-time.

Sauce Labs is optimized for automation and integration with the major CI/CD platforms and developer tools. That is just what they do. It is an easy, one-click solution versus having to manually run scripts.

The platform is easy to use. I can quickly navigate it.

Sauce Labs provide access to automated functional testing and visual regression testing from a single platform. It is very important to have one tool that can do this versus having multiple. Just integrating Sauce Labs within the application and seeing the pass-fail results right away is extremely helpful for teams. You don't have to go to some place else to find them.

Everything is so intuitive.

I can't remove team members that have left the organization. I can only set them as inactive. It would be really nice to clean up my data and delete them from the team management.

I have been using it for several years.

I haven't heard anything about stability. It has been pretty fantastic.

Latency has never been a concern with Sauce Labs. Being in the cloud is super fast for any application, and we take advantage of Sauce Labs being in the cloud. If there was any latency, then it would be on the coding of Selenium versus the Sauce Labs application.

We have about 60 products and only three or four are using it. We have started getting other team members' products to use and integrate Sauce Labs in their test automation, though I am 100% sure of what every single product is doing.

The support is fantastic. We have monthly meetings with Sauce Labs. Even if I have questions, I can just reach out to them. If I have any questions, then all I have to do is reach out to them for help, and they are very responsive. If I have any questions on training, they are willing to set up training calls and train the team on Sauce Labs.

The feedback is super fast. They are always there when I need help. I have never had an issue with their technical support.

I would rate their technical support as 10 out of 10. They are constantly reaching out to see if we have any problems or need anything, but we are perfectly integrated with the Sauce Labs application and don't have any issues.

If Sauce Labs doesn't suggest training, make sure that you ask for it, if needed. They are always willing to come out or even do virtual training. Whatever they can do to help with the process, they are always there. So, if you don't hear about the training, make sure you ask.

Positive

We did not use a different testing tool before Sauce Labs.

The initial setup was very straightforward. They make it so easy to be able to integrate Sauce Labs with Selenium. There were no issues at all, and if we ever had issues, the technical support would just help right away.

We partnered with Sauce Labs. They came to our office for a few days and gave a demo to a large group of people on how to use Sauce Labs, but also provided a little training on Selenium.

I liked the training. As a manager, some people hesitate using test automation because they just don't know how to start. By having some hands-on training with Sauce Labs team members, we were able to give that technical training to people so they understood, "Oh, I could do this. I can start this."

They saw how easy it was to integrate Sauce Labs within Selenium code. The training just helps make it possible because I can't make people do things, when it comes to test automation. By being able to train hands-on and seeing the results, that made it possible for us to do test automation.

We have definitely seen ROI. We are utilizing Sauce Labs specifically for one of our product teams with several more being integrated with Sauce Labs. Seeing the benefit from even one team continuously using it, we are happy with the results that they are getting and having them sharing that knowledge. That is really how we will get other products on it, when people see that it is working for teams who are getting positive results. 

I am not in charge of the licensing costs. They come and ask me, "Do we still need this?" Then, I tell the teams why we need XYZ and the licenses.

We did initially go with Sauce Labs because of the pricing and integration.

I didn't make the decision on Sauce Labs. It was recommended by some other team members that did the research. People were looking at, "Can it help us from a visual point of view? Can it add tests, see all the tests through portals in the cloud, and make testing go quickly?" It offered the possibility of being able to run on multiple browsers and operating systems as well as had integration with Selenium.

I have no complaints nor issues with Sauce Labs at the moment. It meets all of our expectations.

Teams are continually using the product. I would hear complaints if there were any issues. I am trying to get teams to spread the word to other teams. So, the teams are very happy with it and trying to get other people to use Sauce Labs as well, then integrate that into their product team.

Because our applications are not mobile, there are only certain browsers that we need to support. So, we are really not taking advantage of the number of browser/OS combinations, mobile emulators and simulators, and real mobile devices that it offers. I am just trying to get team members up and running with test automation and having some tools to be able to help them with that. I know that they are very competitive with other products in this regard, but that has not been an important factor for us.

I would rate the solution as 10 out of 10. I love the capabilities of it, the support, and the service. 

We have two kinds of applications using Sauce Labs in our company. One is the website, and we're using it to test across browsers, such as Chrome, Safari, Firefox, Edge, and mobile, to see that all the components we have in a web page work. 

The second product we use the solution for is our driver application. We make and deliver pizza. Every time an order is received, we dispatch a driver to bring it to the customer. We have an application for driver dispatch on iOS and Android, and we run test cases for those as well.

I cannot imagine our company without Sauce Labs. We are using it a lot. It gives us a provider in the cloud for running test cases, scenarios, and validation, and that is really important nowadays. You could always run testing locally or have your own environment, but it's difficult to scale and difficult to maintain. You need to dedicate a lot of resources to do that.

We ran, for example, 500 test cases in the last week for one specific team, and those test cases were running at 2:00 AM or 3:00 AM, for some specific scenarios. We could not do that without Sauce Labs. We are integrated for continuous integration using Jenkins and we're triggering all these tests nightly for different teams on different schedules. It would definitely not be possible to run that manually or in a different way. The cloud is the right environment to run it in, and for that, Sauce Labs is the best option in the market.

Also, the Failure Analysis helps us prioritize remediation. If we have a very high number of test cases failing for a given feature, we can analyze them, see the root cause, see the code in our repository, and create a Jira ticket to address those failures. That feature is very helpful for us. It's pretty straightforward and doesn't consume too much time. I generally spend about 15 minutes analyzing all the failures across the teams to see which three test cases are failing most.

Another benefit is that Sauce Labs saves us on manpower. We have manual testers, but it's not possible for them to cover all the different scenarios and all the different features before release. That means we need to rely on the automated test cases, and to do that, we need to run those test cases on a cloud platform. Sauce Labs saves us a lot of time doing those validations. It probably saves us from having to hire hundreds of people. Every team within our organization has one or two manual testers, but for every team we have hundreds of automated test cases that we run before release. It's good enough, for our operations, to have one or two manual testers. We are seeing good results with that, but to run hundreds of different scenarios I don't know how many people we would have to hire.

From my perspective, as an automation architect, the most helpful feature is the test history. I can easily go to the dashboard and see how many test cases we ran and how many failures and errors there were. I can segregate things by team and by specification. And I can tell a teammate, "You need to fix this test case, it is failing too much. The percentage of failure is too high." 

The most important historical data is for the last seven days. I don't go too much beyond that period of time because my feedback is about how we did in the previous week. In our environment, everything is changing all the time. We are testing different products and running different test cases. So for me, it's the recent data that is key.

The Failure Analysis feature is really important for us, one of the most important aspects. What is the root cause? Is it because we have a defect or is it that we have a test case that we need to fix or modify? The Failure Analysis is one of the main functionalities that I am exploring all the time in Sauce Labs. I can see a test case that is failing and on which particular platform or device it is failing. And the most important part is identifying the problem with the code. We can always go to the line of code and see the possible solution. The Failure Analysis helps us to discover which test cases we need to work on.

Before the test history became the most important feature, the most important part was the configuration that made it easy to connect test cases to the cloud. As a result, we can easily test different devices at once. 

And from a manual test perspective, testing in different browsers using the live test solution in Sauce Labs is very helpful.

Every time that we run scenarios where we need to discover the geolocation of our customers, by default it shows as Palo Alto, California. That's a problem for us and we need a workaround for those cases. It would be great if Sauce Labs didn't provide any geolocation by default, and we could provide the geolocation that we want. It would be helpful if we could enter a latitude and longitude into Sauce Labs configuration and say, "When you run a virtual Chrome device or an iPhone, make this your default location. Then, provide me that device so I can run my scenarios," because we have stores in different regions across the United States.

That is the only "ask" that I have for a feature, a geolocation that we can set by configuration. That would be awesome.

I have been using Sauce Labs since I started with this company, back in 2018, so that would be about three years and six months.

I am an automation architect and my work includes providing cloud testing to different teams. Sauce Labs is one important piece for us.

It's pretty stable. We don't have any problems with the solution. We probably need more virtual machines internally, but that's not related to the performance or availability of Sauce Labs. When it comes to stability, everything is going great.

The scalability is connected to our budget. The virtual machine concurrencies that we have are not great for our demand. I am talking with management about increasing the budget for 10 or 20 more virtual machines. But Sauce Labs itself provides the opportunity to scale very easily. For us, it's just a matter of budget.

Sauce Labs has a pretty reasonable price and is worth it for the solution and what we are doing with it.

There are a lot of other options on the market and I have tried some of them in the past. But Sauce Labs has a lot of advantages. For example, one feature that I really love is that when we are doing troubleshooting or have a problem with test cases, they answer every single question so quickly and are very helpful. The customer experience using Sauce Labs is great in terms of support. That is an aspect other companies don't really have.

I started with our company as an automation engineer and their support was able to help me with every single configuration, every single problem, and every single question. I cannot remember a single time that they were unable to help me. They are the best.

The usage of Sauce Labs was not as great, when I first started using it, as it is now. We have a great approach to testing using Sauce Labs. We test mobile and we do live testing and we are running automated testing. We're integrated with CI. Nowadays, it's better than three years ago and I look for it to improve even more in the next year.

At our company, Applause, we offer software testing as a service and we always get a lot of interesting, uncommon or challenging use cases from our clients. We sometimes get ones that require specific devices or browsers to work. For example, we have clients who want to mix testing on desktop browsers and apps or test on multiple apps to achieve some kind of scenario; perhaps you are at a restaurant, and you are ordering something on your personal phone/tablet, which shows up on the restaurant's tablet or desktop browser. 

Our clients are not only looking for executing the test cases manually, but their target is to automate all of them and be able to integrate that into their CI/CD pipeline and get faster feedback about the stability of the changes that the development team produces on a daily basis.

Sauce Labs covers all of our automation needs and also allow us to do manual testing in case we are verifying bugs or testing something else.

My main focus is on automation testing and Sauce Labs is an integral part in our success as a company as they offer 1000+ different combinations of desktop browsers, real devices & OS versions. This allows us to pretty much cover all the automation test scenarios we need. We've also integrated them in our internal SDKs and are using their platform on a daily-basis to test the quality of our clients' apps and websites.

The number of the real devices they offer is also very important to our business, because most clients want to support multiple devices & OS versions. We have clients who want us to run automation tests on Android 7, 8, 9, 10, 11 and sometimes even on Beta versions. Sauce Labs offers all of that, enabling us to support all of these versions, which is really nice. The same goes for their desktop browsers, although most of our clients usually use either the latest version or the one before that. I haven't seen a client who wants to use and old browser version like Firefox 50, but it's a great feature that Sauce Labs offers, in case it is needed for any reason.

In terms of delivering software faster by getting feedback with every commit, it depends on the client and the system under test (SUT); some of our clients are testing manually and that would take them days, others have a CI/CD pipeline and run some smoke tests after each commit. Part of our job at Applause is to enhance the overall testing process of our clients & automate it as much as possible. Instead of taking days to do a full regression, it might take a couple of hours to get the same results. 

Because we're working with Sauce Labs, and we're doing automation for our clients, they get a pretty fast cycle of feedback that allows them to make the right decisions at the right time.

Without Sauce Labs, it would be really hard to achieve the software quality standards or the automation coverage that our clients need.

Towards the beginning of this year, we had to constantly switch between Sauce Labs and their legacy solution for real device testing, TestObject. This was causing a lot of issues or confusion for our engineers & clients. Now, with the new unified platform, we get everything we need in one single place and it is so intuitive and straightforward. You can easily do manual testing, view running automation scripts or switch between data centers from one single place.

Overall, we're very happy with the combinations of browsers and devices they offer, especially because they always have multiple instances of the same device. If you want an iPhone 12 for your tests, you can get five of them for example and run your test scripts in parallel, which reduces the total execution time.

Sauce Labs also allows specifying the browser version as "latest", which means that they automatically pick the latest version they support and run the tests against it. Previously, we had to manually change the browser version in our scripts whenever a new one becomes available and it was wasting a lot of time (as it needed to be done for a lot of projects).

Their platform also offers some cool features if you're working with apps. You can just pass them a URL to an app build that is stored somewhere on your servers or on AWS, and they will install that on the phone/tablet and run tests against it on the spot. This has allowed for an easier integration with our SDK, as opposed to competitors who don't offer such feature.

The market is changing and we're seeing a lot of shift towards testing on OTT devices, like Apple TV, Fire TV Sticks, Chromecast and Roku. This is really an emerging market and has the potential to grow exponentially. We've been getting a lot of clients asking us to test on OTT devices, either manually or via automation. We have been able to automate testing on OTT devices, but it is done with local devices hosted on our premises, so we can't scale that fast or cover all of the huge demand we are seeing. We're looking for the ability to do this in the cloud, so if Sauce Labs offered such a feature, that would be really great. Working on OTT devices usually includes testing on desktop browsers or phones/tablets and having all of those supported in one platform would be ideal.

While Sauce Labs pretty much covers everything we need, another exception is HarmonyOS. I know it's a new thing and it's not supported by a lot of providers, but it is something that clients have started asking for. That is something we'd be really interested in seeing, for both manual and automated testing.

Also, latency, due to Sauce Labs being a cloud-based solution, has been a concern. We work in different continents and countries, but last time I checked, Sauce Labs was only offering two data centers, one in the EU and another in the US. If you're not in either of those two places, you would have latency and issues running your test scripts. However, I'm working with clients in different countries and we've seen some latency issues, depending on the country, although it's not huge. In comparison to other providers who have data centers in different places, there is some noticeable latency.

I've been using Sauce Labs for over five years.

Sauce Labs is pretty stable in comparison to other providers. We still get some issues every now and then or random failures, especially when there is a new OS or browser version, but it's not a big deal and we can easily contact Sauce Labs' support to get things fixed.

One of Sauce Labs' competitors does not force you to select the data center you want to run against. They just figure out which data center is closest to where you are executing your test scripts from. They offer a single, unified endpoint or URLs when it comes to automation and handle everything else internally. When we're writing automation scripts, we don't need to specify, "I want to run on the European data center," or "I want to run on the American data center." We can just say, "I want to run a test case," and depending on the location you come from, the platform is smart enough to direct it to the nearest data center to reduce latency.

This may not be directly related to scalability, but this kind of capability would make it easier for us to build our SDKs faster and focus on other features, which in return would allow us to scale faster as a company. The learning curve for newcomers would also be easier, because they wouldn't need to worry about figuring out which data center to run against.

While I love the fact that we can specify the data center ourselves, because it gives us more freedom, I would love to see more data centers in different places around the world, to reduce latency, and the selection of the data center implicitly done by the platform, so we don't need to worry about it.

We open support tickets, and they're pretty responsive, they get back to us on time. They're really good about fixing things and making their platform more stable.

I've run into a couple of situations where tickets have been left for weeks without feedback, but that has not happened often. When it does happen, I can go to our customer success manager and say, "We need some attention to these tickets." She can take care of it and that makes the support pretty good.

Positive

Pay attention to selecting the correct data center, otherwise you would run into some latency-related issues.

Although we are not using visual regression testing, that is something that would be really interesting, because a lot of our media clients want to test visual validations on their apps. If Sauce Labs is offering that out-of-the-box, it would be really interesting for us.

I'm on a team called the "Quadrant Three Mobile" team. Our focus is mobile testing and mobile browser testing. Sauce Labs provides iOS simulators and Android emulators that we use in our tests. It's running on our private cloud, and we have a Sauce tunnel set up to communicate between our environment and the Sauce Labs environment.

We don't often use the Sauce Labs UI to track the tests we need to do. We have a UI on our end to do that. However, we log in to the web interface to view the dashboards to see the test strength and what was triggered or to search for specific tests exact testing. The Sauce Labs dashboard has links to videos of the actual test runs, which helps us deal with debugging issues and test failures. 

Quality control engineers are the main users of Sauce Labs at the company, but developers also use it for making the CRM code base. They run tests on Sauce Labs mid-development to ensure their piece of work is going well.

Sauce Labs helps us identify the root causes of bugs. The solution offers a lot of flexibility by providing the latest iOS and Android emulator versions, and even the Appium updates when it comes out in the market. 

Those have been helpful because the apps we test on Sauce Labs are used by customers across the globe, and we want to be sure we're testing on the latest iOS and Android versions as well as older versions that our customers still use heavily. Sauce Labs has done a decent job of giving us all the versions we need. 

Sauce Labs' dashboards are a good supplement for our dashboards and UI. The web interface is useful when we want to triage a specific test run or overall across different jobs. It's also handy when we want to look at what results we get when we run a test across a whole account.

Sauce Labs' ability to test the visual aspects of our apps' UI has been crucial. At the end of the day, mobile testing is not only about functionality but also making sure your UI looks good in different languages and works well. Sauce Labs supports screenshots whenever test failures happen, giving us a good idea if something is broken on the visual side.

Sauce Labs' logging features could be improved. For example, when we run a mobile test on iOS, we want a way to capture the logs generated. It has some drawbacks there. Sauce Labs isn't able to give us everything we test for. 

Sauce Labs' dashboard could be improved by adding more filters and allowing more customization options. There was one instance where the dashboard on the Sauce Labs UI didn't meet our requirements, so we had to use the Sauce Labs API to create some apps and dashboards on our own. The API endpoints could be a little more robust and customizable. 

We have been using Sauce Labs for four to five years now.

Sauce Labs' reliability is one of the most important aspects of the platform. They have a status page to notify if there is any downtime. We rely on Sauce Labs because we have a continuous development process here, and we are testing code that comes out through Sauce Labs' emulators. 

However, we've had occasional performance issues. For example, there are times when devices need to be restarted or the UI takes longer to load and things like that. The virtual emulators and simulators have been good, and their hardware and infrastructure have been standing up well.

I think Sauce Labs has proven that their platform is pretty scalable because they give us a broad selection of versions available for iOS and Android. They also support their emulators with good virtual machines, so Sauce Labs can scale their infrastructure to their customers' needs quite well.

I don't know exactly how many users are currently working with Sauce Labs in my company, but it's in the hundreds. We'll certainly expand usage in the future because we're planning to offer new kinds of mobile apps, and when those come out, we'll need to test them using Sauce Labs. As the number of products we offer increases, the usage will too. We use it for nearly all of our functional testing.

I rate Sauce Labs' support at about seven out of 10. We put in certain requests with Sauce Labs, and sometimes it takes a while to get solutions implemented, depending on the priority.

My team didn't deploy Sauce Labs in our environment. A different team handled that. We did the initial installation back in 2016, and I don't recall it being very complex. 

They had some binaries and decent instructions on how to set up Sauce Labs' tunnels. They also give instructions on how to capture logs of those tunnels to see traffic between your environment and the Sauce environment. All of that is pretty well documented, and support teams have been quite helpful. Whenever we needed something out of the box, we've been in touch with them for it. 

I can't really quantify a return on investment, but testing on Sauce Labs has helped us catch issues and fix problems much sooner than we would have without it. That has saved us money.

I rate Sauce Labs eight out of 10. I recommend it for mobile testing. Sauce Labs is a reliable vendor, and you can trust their network. They have a good platform, with broad support for various mobile OS versions. Their availability is also high in the region, so we seldom see outages. The dashboards on their website for tracking your mobile testing strength are helpful. Overall, it's a good product for anyone wanting to do mobile testing. 

The main aspect I've learned from working with Sauce Labs is that it's not easy to maintain a range of devices or virtual environments and provide it for mobile customers. We have tried to do that at my company, and it's challenging. I definitely like what Sauce Labs is doing in terms of providing that reliable network for us. We're also learning more about our own product through testing on Sauce Labs. The sooner you test, the quicker you identify issues in your own application. 

We mainly use it to run our test cases for different platforms. We're able to run it for multiple browsers and multiple devices. We use it for about 90 percent of our CI/CD test cases.

We are using it for automated testing and not for visual testing or performance testing.

It's important that the solution gives us access to automated functional testing, as well as browser/OS combinations, mobile emulators and simulators, and real mobile devices, all in a single testing suite. That's particularly so for our client-facing applications so that our customers are able to access our products and offerings through any device and platform. For those types of applications, it is a huge help. The number of browser OS combinations, mobile emulators and simulators, and real mobile devices it offers is really good. There has not been a case where we say we want a given combination and we don't have it.

One of the most valuable features is that we do not have to have the cross-platform testing vehicles in-house. Sauce Labs gives us the ability to test across platforms and that really helps give us confidence in our products.

One of the challenging areas for us is the reporting and the matrix. It should be based on roles, but right now it is only available for the admin role. The admin role can really do a lot of stuff, but our infrastructure team, which holds the admin role, is not ready to hand it over to us on the testing team. If Sauce Labs had permissions associated with roles, where this role could do this activity and that role could do that activity, it would be easier for us.

We have raised this suggestion with our product manager and she has put it in the product backlog, but, of course, she cannot guarantee when that will be looked at.

I joined this company seven months ago, so I've been using Sauce Labs for that long. But the company has had it for about three years.

From a solution stability point of view, it's good.

We are able to run some of our tests in parallel on the solution, within the constraints of how many licenses we have. We have some 50 testing teams across our organization, and we use them. There has never been an issue with not being able to execute tests.

Latency, due to Sauce Labs being a cloud-based solution has not been a concern.

We did have downtime in late September last year, but it was because of our lack of knowledge in terms of the configuration. Sauce Labs support was really quick in responding and triaging and fixing it, which was really great.

With scalability, they are going in the right direction. I have attended some of their new product webinars on API testing, and I really found that to be cool. We may use it, or evaluate it at least, once we start going into that direction. That goes for visual testing as well. If they are able to deliver on some of their promises I really look forward to that and seeing how we can utilize them.

We could use Sauce Labs even more. While we are using it in our testing teams we are not yet there for things like API testing and visual regression.

Our next step, in terms of our exploration of the solution and how we want to use it as part of the CI/CD, is that we are moving into GitHub Actions. We were using Jenkins and it worked well with that. We are moving to GitHub Actions and trying to figure out how that will work.

Overall, technical support has been really good. They have responded to our questions and have triaged pretty quickly and followed up.

The reports that our account manager at Sauce Labs provides are helpful to us to see where our gaps are. She also helps us evaluate where we could be from an industry-standard perspective. She gives us an idea of what others are doing, what she's seeing out there, and in which areas we can improve.

In terms of using Sauce Labs’ technical expertise to help integrate automated testing into the CI/CD pipeline and DevOps toolchain, we have not done that yet. That is more due to the way our organization is structured. We, as the testing team, do not have access to how the tool is managed or how it was set up. There are probably gaps in terms of our understanding of how the tool can be used effectively. But we have discussed this with Mandy, our account manager, and she has offered to do a free session for our associates, which is scheduled for next Friday, and we are looking forward to that. It should help us understand what the best practices are and whether we are using it right.

From the perspective of our organization's roadmap, we are new to testing automation in general. Our focus is on automated functional testing. There are certain use cases for visual testing, and there have been talks about performance testing, and an evaluation will be going on for that. As part of the workshop next week, Sauce Labs will also be presenting some of their offerings, so we'll be looking at those as well.

Positive

Sauce Labs is a tool. It can fit the needs that you have, but you first have to figure out your needs. Once your team has been able to successfully use it, and things have stabilized, go to the next need you have. That's exactly what we are doing. Once we get our functional testing to be stable, we'll look into the next performance test case.

Don't try to do everything together. When you're going with a new solution, it takes time for people to adopt it.

The process could be different for a large company like ours, versus a smaller company where there are just a couple of products. They may be able to move faster. For a financial institution like us, there are so many roadblocks that we have to go through. I do understand that the licenses are expensive, and you do not want to get these licenses and have them sitting idle.

I would rate Sauce Labs a 10 out of 10 because I have not been able to find any use case that Sauce Labs does not provide.

Our healthcare company has a QA team who uses Sause Labs to review various metrics.

For me, as a software engineering manager, I am able to see who from my team is logging on, when are they logging on, and other things in regards to activity within the environment.

The platform is optimized for automation and integration with major CICD platforms and developer tools. This allows us to speed up our production without burning up all of our resources.

It also provides access to automated functional testing (this couples nicely with our other functional testing that we have), visual registration testing (which is as easy as a click of a button), and front end performance testing (which provides a clear understanding of our current state of performance).

Sauce Labs provides us with an all-in-one solution that saves us time, money, and human capital.

Since this is an all-in-one testing site, we are able to take advantage of the browser OS combinations, mobile emulators and simulators, and real mobile devices. This is important to us since we have a variety of users, browsers, OS, etc.

I would like for there to be more detail in regards to the quality of our code i.e. how many failures occurred, how many passed based on industry standard metrics, etc.

I have been using this solution for a few months.

This is a stable solution, I have not had any stability issues.

As told by our rep, this is a fairly scalable solution.

I was not a part of the initial setup though I have all the reason to believe that it was straightforward.

You will save a lot of time thanks to this solutions ability to run parallel testing. My team saves about a week and a half on our deployment schedule. Just be sure that you have settled on your design prior to implementation.

Our company has different divisions, like research and development, manufacturing, and research laboratories. There's also a department called Global Infrastructure Services. In total, we have five or six areas. In some cases, Sauce Labs is only used in a segment of a department. Take, for example, research and development. They might not use it in the laboratories, but they have a digital health section that works on apps or digital solutions for medical diagnostics.

In this example, the primary use case is developing different software applications for medical diagnostics. They use Sauce Labs for testing applications in different operating systems and environments. We do regression testing across various ways someone might use an application. Instead of securing physical machines, they use Sauce Labs to do that. Many of the applications are internal to the company, so we use Sauce Connect to link up to the internal network to test those applications.

We do a combination of parallel and sequential testing in Sauce Labs. Whenever you log in, you see all the tests on the dashboard. You have concurrent and parallel tests running, but some people will also use a sequential one.

Before we started using Sauce Labs, they needed to use physical machines to test applications. We required a Mac or Windows laptop to try different combinations, so it used to be a cumbersome process. Sauce Labs made testing more straightforward, so we could run more elaborate tests. 

Sauce Labs provides us with more combinations to test, so we can keep adding platforms and devices to our network. That's been a very seamless experience. If there's an iOS or a private device we need, Sauce Labs has helped get all those set up when needed.

As platform administrators, we get requests from different departments. Project teams using Sauce Labs come to us and say, "We have these three or four devices, but we might need another one that is private to us with this combination of operating systems and browsers." We get those spun up in Sauce Labs and have customer support. 

The ability to run tests in parallel has cut down our test execution time for every application we use. The more we can reduce testing time, the easier it is to deploy an application, so running parallel tests is obviously an excellent way to do that.

It offers a decent range of browser-OS combination simulators and mobile device emulators. Our company tries out lots of different applications and solutions. It's not just for product development but for any application we use internally. For example, we use JIRA for project management, but we tried many solutions before deciding on that particular one. 

We've been using Sauce Labs for a long time, even though there were other candidates we could have used. It's a robust platform that has met our needs, especially with Sauce Connect. We have internal applications that aren't available externally, and Sauce Connect makes that possible.

Nothing comes to mind right now, but this might be because I'm an administrator and not an end-user who is familiar with the application's use case. If we have teams asking for something that isn't already there, we communicate that back to Sauce Labs. That hasn't happened so far in the time that I've been in this role. 

I may not know what should be improved on the platform, but I think it could offer a greater variety of testing solutions. I know there might be competing solutions that cover more aspects that I'm unaware of, and it could expand a bit more. We've done a lot of automated testing scenarios, and that's all the rage these days, so I think Sauce Labs could look at potential ways to improve and cover other scenarios.

I work for the IT team of a pharmaceutical company, but different departments use Sauce Labs. I belong to the team that manages all applications the company uses, so we provide Sauce Labs for other users but don't use the product ourselves. I support it from the administrative side, but I've only been in this role for a few months. 

I haven't seen any downtime in the few months that I've been in this role, and we haven't heard any complaints about latency, but we've always used a cloud-based application. We wouldn't know the difference. We could compare if we had an on-premise version, but we've always used the cloud version, and it's the fast version.

We have purchased a consistent amount of licenses over the years, and we are looking to grow with a focus on automated testing this year.

Sauce Labs' support has been awesome. We have monthly support calls to catch up on any requests that we might have. When there is a new update or release, somebody from Sauce Labs comes to talk to us. It's not just us, but all users. It's like an open house. We have been planning that for some time now, but COVID has put a damper on those plans. When we meet monthly, we share any findings on our site, and they come up with best practices to share with us as well. We are satisfied with Sauce Labs' customer service.

A supply management team deals with pricing and licensing. We look at the utilization of licenses every month and see if we need to purchase new ones then shoot them an email saying we need more. We don't get into the inner workings of licensing and procurement.

I rate Sauce Labs eight out of 10. There are more and more different testing scenarios for various machines and environments we use every day. Sauce Labs provides a robust platform to test combinations of what a user might encounter when accessing any application.

Sauce Labs reduces the testing time and covers all the possible scenarios that could come up, so we don't have to worry about any scenario that we might not have missed testing manually. It's a great platform to cover all your bases.