Sauce Labs Reviews

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. 

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.

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 several healthcare products across the healthcare continuum, and we use the Sauce Labs platform to test our applications across different browser and OS combinations. We also use it to do mobile testing across different mobile devices that we may not have. It's not easy to set up these different configurations, so the cross-browser and cross-OS platform in the cloud gives us the ability to test across these different configurations without having to set them up or maintain them.

At this point, we are trying to focus on API testing.

My role is with a central team that helps other teams. If another team is struggling then we reach out to them and offer assistance. Because of this, I am familiar with how some teams are using the product. If on the other hand, a team is doing well and doesn't reach out, then I don't have any insight into how they are using the solution or how well things are going. 

We've had an event where I worked with the vendor to coordinate an automation day at my company. They worked with our QA engineers through a training process where we had a test repo that we were able to run across different browser and OS combinations using the platform.

Technical support is very important because it helps us get through issues faster. When we are trying to integrate with a new tool, as is the case now because we're trying to move to GCP, we have a dedicated solution engineer to work with us. The engineer is helping us as we ramp up with GCP, getting our automation to work.

We went through this a few years ago with Azure. Learning a new tool is challenging enough, and then trying to make it work with our existing processes is even more difficult. For example, we need to enable our test automation to run on the new platform and have everything work together. It can be challenging, not to mention that mobile testing is still evolving. This is why support is important. They have helped us with our questions and to get through any blockers.

For the most part, the product is optimized for automation and integration with the major CI/CD platforms and developer tools. That said, our constant complaint is that it is kind of slow. We are trying to figure out ways that we can work around the slowness, and what things we can do better.

We have a lot of products here in the company, and not everyone is leveraging the cross-browser testing platform that is available at Sauce Labs, but we have more and more teams adopting it in the last three years. We are trying to collect more insights into how our users are accessing our applications and using that insight to cover all those different testing configurations using the Sauce Labs platform, so we are trying to leverage the platform more in our internal testing.

For now, Sauce labs covers our needs with respect to the number of browser/OS combinations and mobile devices. However, having more availability and looking into different strategies for making things faster are important. Our goal is always to get faster feedback on a build, which means if it takes a long time to run an automation suite then it's less likely that we'll use it. We're always seeking ways to add capabilities and expedite things.

Having the ability to test our application on additional browser/OS/mobile device combinations opens up additional revenue streams for us because we have a larger user base. It gives us the confidence that the application we are putting out will generate a positive user experience because we've covered all of those testing combinations.

We've gone through a lot of OKRs and have had a general goal to reduce the time it takes for us to test applications. This product enables us to run tests in parallel, which helps to make things faster. I don't have any concrete or documented examples of how long it would take to complete our testing before using the tool because we've evolved the way we write automation.

There were times where it would take half a day to run an entire suite of tests, and through some of the improvements we've made, with and without the tool, our goal has been to be able to run a smoke test in 30 minutes. Some teams are able to achieve that, whereas others cannot.

There is really no one answer that fits because we have teams that are across the spectrum. Some are working with mature products and some are just getting started. I know of one of our teams that optimized their automation and with Sauce Labs, they have been able to take their automated test time down from three hours to approximately 30 minutes. This is only one team out of many but it demonstrates a significant change.

The most valuable feature is cross-browser, cross-OS, cross-mobile device testing.

The parallelization of automated tests is a best practice that I recommend. Some of the teams are able to do that, although some cannot because of the way the tests are formatted. If their configuration allows for it then it is definitely something that I recommend they take advantage of.

Running testing in parallel has worked well for some teams. In one instance, a team was able to split their tests so that they ran across two platforms. Running these two configurations, they initially cut the three-hour testing time in half. Within each of those configurations, we were able to parallelize even further within our test framework, and ultimately, we were able to get the test time down to 33 minutes.

The process can be a little slow to configure and get started. It's a cloud platform and you're trying to run automated tests. It first has to be configured, then the test downloaded, then you have to configure the environment that you're going to run on, then kick off the test based on what your needs are. All of this takes time.

We have faced challenges with the availability of mobile devices. There was once or twice where there were no mobile devices available. These instances may have been due to a service outage.

I have been using Sauce Labs for approximately five years.

We run our testing on a daily basis and I don't think we've run into any stability issues. Nothing that I am aware of has been a concern.

As we run into issues with anything that we are trying to do or integrating with to run our test automation, we reach out to their support team. Anytime that we need something and we need a quick answer, my first recommendation to anyone that reaches out to us for help is to call support and get it logged. This way, we can get someone to start responding.

Some of the support team members are better than others. Overall, I would rate the support between six and seven out of ten.

We did not use another similar solution prior to Sauce Labs.

Also, personally, I have not used any other cross-browser testing platforms.

I was not involved in the initial setup or getting it integrated with our automation test framework, but I think it was fairly easy.

The initial setup was done in-house.

As a SaaS product, it is always up to date.

The pricing is definitely on the higher end, and there are other options that are more cost-effective. One of our teams that was using Sauce Labs separately decided to go with a different solution that was less costly.

Prior to choosing Sauce Labs, the company evaluated BrowserStack. I was not part of the decision process but the differentiating factor may have been the support.

We have our internal framework and we basically use Sauce Labs for cross-browser capabilities and mobile device capabilities. Since we have our own framework, we have not explored any functional testing capabilities that the platform has.

The vendor has acquired API Fortress, and it is available within our account for free to try out. That is something we're going to have a demo next week to look into because, at this point, we want to start focusing on API testing. It's helpful that we are able to run our UI tests across different platforms but we would like to focus more on the other layers of the application. We would like to test under the hood, the business layer, more.

I would rate this solution an eight out of ten.

I am part of the QA team. I am implementing this solution. Right now, we are also trying to implement this solution in order to gather results in the testing process.

We have several stores around the world, more specifically around Latin America. We are trying to automate many tasks for the mobile applications that we are building. We are also trying to automate many web tasks in order to upload items to the tool.

The device level of the platform is the most valuable aspect for our team.

So far, the stability has proven to be quite good.

The solution seems to have interesting automation capabilities that we still need to understand. 

The testing process is difficult. I need to prove the complete competency of the tool, and I am finding that challenging. 

Right now, we are in the initial phases when it comes to actually using the product. We are testing some tools in order to implement them in the future. We are in a very early stage.

While we are still in the early testing phase, from what I have seen so far, I can say the solution is quite stable. There are no bugs or glitches. It doesn't crash or freeze. The performance appears to be very good.

That said, we still need more time to really dig into its capabilities. 

We've been in touch with technical support as we've run into some issues and we want to better understand how the product will work in practice. We've been in touch to try to get a hold of someone that can walk us through a customer journey so that we have the knowledge we need to use the full potential of the product. We're still working on making this happen.

The solution has not been implemented fully yet. We are still trying to uncover if this is the right solution for our company. We seem to need assistance with support and with the setup process before it will actually go live. We're not far enough into the process to really discuss the deployment and if it is difficult, or complex, or very straightforward. Those details are still to be determined. 

I'd rate the solution at an eigh tout of ten overall. 

We had an issue in the past and we're looking further into the issue.  

The primary use case for this solution is for automation testing on mobile and web on our testing environment so we can implement continuous integration and continuous delivery into the workplace. With the automation practice being used we are able to deliver more and possibly deliver daily after each build is created in theory. With the automation, we can now focus time testing the higher traffic areas or higher risk areas that could possibly crash or cause a bad experience for the end-user of either the web or mobile application. 

Sauce Labs has improved the organization with the ability to test more internet browser configuration, more mobile testing devices that are not a flagship phone, and more operating systems. With the internet browser testing, we are able to config multiple test scenarios and pinpoint which internet browser we want to test on and what operating system we want to run the test on. So with Sauce Labs, we are able to cover multiple Chrome, Firefox, and safari variations to support and test for all users. 

The feature that I have found most valuable is their device bank. With this, I am able to test more niche phones that is not a flagship and have the ability to support the end-user. This has been useful because when older devices from Android and iOS are running older OS and they experience a crash, it has been hard in the past to replicate their issues without purchasing that device and hoping it matches the phone specs. With the device bank, it seems like all a major of phones from android 5.0 are covered up to the current. 

A service that could be improved is some of their Wiki documents are either outdated or point to broken URLs; however when contacting the customer service they are able to respond in a quick manner with either an updated document or with the steps to fix the issue. 

Another feature that could still be improved on is more error clarity. Sometimes when running automated scripts the test will fail on the device side instead of the script and errors only show a 500 try again message instead of a detailed script that could of a been a timeout error from the code. 

The company has been using Sauce Labs for 8 months.

No we were not using a different solution. 

I think a longer trial period would be beneficial. Instead of 14 days look at 28 days due to in part the company that is on the trial period could be busy or possibly busy during the trial period. 

We looked at other options but found that Sauce Labs was the best option to support both Web and Mobile.

My company uses Sauce Labs to run all smoke and regression tests for our application.

We primarily run our tests on Chrome 83, but we occasionally run on other versions (81 or 84) to check to compatibility. Our smoke suite runs on a nightly build, and regression on a bi-weekly basis.

For building out new automation features, we have to have a passing Sauce Lab run before creating a pull request. Doing this ensures that our new automation features will run on other environments and not just locally.

The insights section provides a great overall state of the automation suite and can identify trends relatively quickly. If we see a dip in our passing rate over time, we can look at what changed when the test started failing to find the root cause rather than doing a quick fix to find that the test fails a short time later.

The visual data is helpful for all levels within the organization from the QE engineer level up to the director level.

The ability to change the browser version has also ensured that our application stays compatible with previous and updated browser versions.

One major feature that I like about Sauce Labs is the recording feature. I love the option to watch a video playback and command and view log when I'm trying to figure out why my test was passing locally but may fail on Sauce Labs. It's helped to make sure of my automation.

Another feature I find valuable is the ability to choose browser versions. This feature allows us to test on our minimum browser version but also check/verify that our application is working on the most recent browser version as well.

The insights tab is also very valuable, as I’ve discussed early; it provides a great deal of data and determines trends in our automation sooner.

From a company use standpoint - I have no complaints. The one issue I have is the 14-day trial that a new user gets for free. I understand the concept of the trial period; however, I think this could be revamped to a free 30-minute run time every few months or after a significant update once the trial period has ended. Personally speaking - I like to maintain my automation framework and would like to occasionally test that it continues to run on Sauce Labs after releases without stealing from Sauce Labs.

I've been using Sauce Labs consistently for a year now since I've started with my company.  After being introduced to Sauce Labs, I've incorporated it into my framework that I maintain.

A previous solution I had used was running a VM from a NAS server to run our automation scripts.

Be sure to plan out your solution before starting the free trial; 14-days goes by rather quickly.

Sauce Labs was already integrated into our framework and SDLC process when I started with the company.  After using it for a year now, I would highly recommend this to anyone.