Sauce Labs allows us to expand our coverage without having to run them separately against different browsers on your local machine. You can just spin up an instance and run against whatever browser and operating systems combinations you need.

Especially on the mobile side, things are improving. We had an on-premises lab, where we were managing the physical devices on a device cart. That's going away, as we are now able to use the public cloud offering, which has 2,000 plus devices.

For locking down devices that we prefer to use without registering with other clients, we use the private Cloud. We split up the distribution 50/50 between private and public.

Sauce Labs is what enables our different testing combinations. We run our different suites that include smoke tests, regression tests, and functionality testing. All of these types of testing need to be verified against different browsers and mobiles, and this is our solution to that problem.

This product helps us to increase test coverage by testing both functional and visual aspects of the UI. This is very important to us because we have different types of customers. Some are end consumers, whereas others are banking customers. We won't release software without validating all of our use cases.

Sauce Labs helps us to deliver new features and products to the market. It's part of the use cases that we have to validate, so we need tools to complement our test cases. We're trying to eliminate manual testing or how we kick off scripts. We want to be able to automate testing of our suite of use cases against our devices and operating systems.

From an automation standpoint, Sauce Labs enables us to have a fully functional CI/CD process while saving time and cutting down on the training required for individual testers. We can easily automate tests without training a whole bunch of people on Sauce Labs. There's a whole slew of quality and security testing tools that a tester typically needs to know. Automating and integrating with Sauce Labs reduced the number of things a tester needs to be trained on, and they don't need to use Sauce Labs daily. They just see the results.

It's one less aspect the testers need to worry about. They come in from time to time to review the results, but it's automated, so they don't need to connect to Sauce Labs, run the test, and get the results back. They don't even have to know that it's Sauce Labs behind the scenes. We take care of that for them, so it saves us time.

Automation allowed us to reduce the size of our team. When we initially got Sauce Labs, we had a full core development team with a lot of testers. There were 50 to 70 testers working 100 hours a week. That's around two hours each day per tester on the low end, so 50 multiplied by two is 100 hours per week. Multiply that by six to eight months of testing.

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.

Running 500 to 600 scripts in our local infrastructure takes 8 to 10 hours for the cycle to complete and get results, wherein when we use Sauce Labs and get parallel instances, we can run our test in parallel or concurrently. The execution time reduces from 8 hours to 2 or 3 hours based on the parallel instances procured from Sauce Labs. That's really good. The other thing is that it's very stable. We might face some network issues when we run tests in our local infrastructure, but I have never seen any such issues with Sauce Labs. Their infrastructure is good.

Sauce Labs is optimized for automation and integration with the major CI/CD platforms and developer tools. We've integrated it with Jenkins. There is a Jenkins plugin for Sauce Labs where you can just configure your job in such a way that it can automatically trigger on Sauce Labs. No manual intervention is required. They also support integration with Jira for defect tracking. They have a solution for raising a defect with one click, which is pretty cool. If you feel something has to be reported on Jira for developers to fix, you can just click on that, and it is reported directly on their Jira project. We've also integrated Sauce Labs results with Slack. Once the execution is completed, it notifies us on Slack that the execution is done, and we can also get our results over there quickly.

The testing environments we've used include Windows with Chrome, Firefox, and Edge. We've used Mac with Safari. On the mobile part, we've used Android and iOS. We've also used iPad on iOS. It's important to have multiple types of testing environments available in a single platform. We don't have to look at different solutions. Sauce Labs is a complete package. There are clients who request to execute their applications in N number of devices covering all the operating systems and mobile devices, and having such a solution to look at everything in a single package is very helpful.

Sauce Labs affects the execution cycle because the time taken for us to run the tests in a local setup is a lot more. Sauce Labs helps us with that part. Also, when the developers post any new code, we don't have to be there to run it manually. With the CI/CD and Sauce Labs integration, it automatically happens, and we can just go and get our results, which is very helpful.

The ability to test on additional testing environments has enabled us to make our product available to a larger user base. We also do functional testing for applications. In our inventory, we might not have the latest devices. For example, the device that we have with us might be of a certain version, and it might not extend beyond that, whereas Sauce Lab immediately launches the new version devices in the market, so we can quickly go, test, and report any defects in those versions. The coverage of testing has increased because of the availability of new versions, which has had an impact on the business. We can test and push the code to production after testing on new versions. Later on, if the users with the latest versions of devices report an issue, it will make sense to us.

Sauce Labs can run with every code commit and provide developers with immediate feedback. We have to arrange our architecture in such a way that it does that. If the architecture is right and you have the code in the right place, it definitely provides what you want. Previously, it used to take a lot of our time. We are an India-based team. If the deployment happened at midnight or 12:00 AM, when we logged in by 10:00 AM, we could see that there was a deployment. We would then do the testing, run the automation tests, and give the results back to the developer by 2:00 PM. By integrating CI/CD with Sauce Labs, the moment the development team commits the code for a different set of devices and browsers, it immediately triggers the Sauce Labs pipeline, and we can get the results at the same time when testers and developers log in.

The immediate feedback with every code commit affects the development processes. It depends on the file or script size that we have. For a small number of scripts, it takes one or two hours.

The immediate feedback helps to deliver software faster. When we do manual regression, it takes 40 hours of time. With Sauce Labs, the duration reduces to 20 hours, so the cycle of delivering the code is much faster.

We run our tests in parallel on Sauce Labs. When you have 50 scripts and you run them in series, if each script takes 10 minutes, then your execution time would be 500 minutes with one machine or one instance of a browser. If you have Sauce Labs with five parallel instances, you can run five tests at a time, which will save a lot of time.

Infrastructure provisioning is a big thing. The whole point of having this expensive license for Sauce Labs is so that we don't have to maintain multiple versions of Chrome, Safari, Firefox, or Edge. We don't have to maintain our own device farms or our own servers, and that means no security patching, compliance, or auditing. A whole bunch of infrastructure headaches are offloaded to Sauce Labs.

Using it every day, and having all the manual QAs get some experience working with it, has saved us multiple person-hours. Just having an automated testing solution, Sauce notwithstanding, means an army doesn't have to sit there and click, click, click, multiple times, every time we do a release, to test the same old things and make sure the same old features still work. Having Sauce Labs on our side, we can actually do all of that at scale with the automation.

The number of testing environments is definitely mission-critical because it plays a part in a release. We run these automations so that we are able to catch issues and so that a customer does not experience issues. And not having to do manual QA frees people up to do exploratory testing. It frees them up to use their intuition and domain knowledge to find bugs that have come in from new features and that might affect old features. It's absolutely essential that we have Sauce Labs. There's no way we could accomplish releases at our current rapid cadence without it.

We also run tests in parallel. It would take way too long to do it one by one. It saves us tens, hundreds, even thousands of hours. And Sauce Labs has reports on that, telling you if you're maximizing your concurrency and whether your licensing is affected by concurrency units, which is great. Knowing that we can run tests in parallel means we can focus on the tests themselves and the quality of the tests. We don't want to create duplicate tests because that would increase test maintenance. Running them in parallel means that we're getting the most for our CPU buck.

The cool thing about Sauce Labs is their love of metrics. I don't like keeping track of metrics. My management is constantly screaming about metrics, but when you finally give them metrics they don't check them. We have built out individual solutions to track the metrics for various vendors' solutions, including who's using what, what time they are using it, and how long they are using it. We might spend two months building something like that and giving it to management, and it then gets ignored. Sauce Labs Insights provides an easy platform where I can see that there are 85 teams running tests; 23 teams running tests right now; most of their tests are passing; and they're across these browsers.

The ease of access to that data is incredibly important because it means I don't have to build more metrics solutions that just don't get used. The fact Sauce Labs offers that kind of feature helps me in my job when it comes to responding to upper management and the requests that they sometimes make.

Also, the solution definitely helps to save on manpower. I'm a part of a team that has been managing a few Selenium bridges, smaller scale, on-premises "Sauce Labs," to help with smoke testing, and managing that is a living, breathing nightmare. Overall, before I joined the company, everything was done by manual testing. One team would have one web app, a development team, and anywhere from 50 to 100 manual testers who just sat and clicked on a website all day long. When automation came in, my wonderful job was essentially getting a whole bunch of people fired or having them moved over to automation. Based on my experience with managing a few different Selenium bridges, the amount of man-hours I've spent just debugging that, I could easily have a team of five to 10 people and still probably be running a bit behind in terms of managing that grid. The fact that I don't have to do that at all saves us nine people right away. It's a solution that has really helped, but I balk at giving a more exact number because it's hard to calculate.

The cost savings with Sauce Labs, on an annual basis are anywhere from $200,000 to $400,000, just for base level salaries for a small group of interns to provide the manpower it would take for us to manage something like Sauce Labs at a company level.

There are also savings on testing time. A lot of that comes from the ability to get teams on board fairly quickly. With the Sauce Labs documentation, everything is made so that it's very easy for a team to just jump in and start running tests. That saves us a ton of time.

We have different content spread across different regions and Sauce Labs also helps in enabling the testing that is required by that situation. The things that Sauce Labs helps with are things I don't want to do. I don't want to manage a giant stable of virtual machines. I also don't want to—and God bless them—but they've been managing Internet Explorer browsers. They're nightmares. The problems I have just trying to get an IE container or browser up and running, so a test can be automated against it, is insane. The fact that Sauce Labs has it down and working fairly well saves us a lot of work and headaches.

Sauce Labs helped us get ready to roll out our mobile apps for the first time. Before implementing Sauce Labs, we tested physical devices that team members had to share. It was more feasible when we were all located in one office, but we couldn't leverage our offshore capacity. With this solution, we can do everything remotely, which is essential now that most of us work from home. 

There's no need for other physical devices anymore because everyone's using Sauce Labs. It's efficient and it works. We still have some older devices, but nobody bothers with them anymore because Sauce Labs works just as well.
While it doesn't necessarily help us get the product out faster, it does make us more confident in the quality. Sauce Labs Visual also helps us catch bugs earlier in our development cycle.

In January of 2021, there were 515 automated tests that ran through Sauce Labs in the company. By October, we were just shy of 3,000 tests. That is a 600% increase.

In general, I know that there are different pockets of the business that build apps for different cases. For example, we have an iOS dev team in one part of the business. We have a Windows team in a different part of the business, and they are able to use the same platform without us having to try to support multiple different things. In that sense, the ability to test on additional browser, OS, and mobile device combinations has been a great help. 

All our automated tests run in parallel. This helps us to demonstrate value to other parts of the business who have not yet adopted the solution. For example, when there are groups who use Sauce Labs and we try to share learnings, that team presents, and says, "I have saved this many specific hours. Or, I can run 225 tests (or however many tests) in parallel. It saves us this much time and this many dollars to have our application go out that much faster."

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.

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.

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.

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.

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.

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. 

I use the mobile application. Whenever we get mobile builds through the CI/CD pipeline, we directly upload them to Sauce Labs. We usually test on various devices and versions. The solution helps us to identify any issues that we might face in different environments, devices, and versions.

We can run our tests in parallel. We have access to all the browsers and devices, where we can run our test haphazardly. They have video recordings as well for the tests that we run, which can easily be accessible and shared across different teams or management without them being actually logged in. 

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.

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. 

• It increases cross-browser testing and reduces cost in purchasing and managing devices
• Helped team to run test cases locally on OS and browsers
• Reduce device cost and handling, We lost many devices earlier
• Ran test cases through Jenkins and capture results in a cool format
• Easy to debug issues in all supported devices
• Running test cases on both production and QA
• Running image comparisons on different devices
• Sauce l=Lab analytics provide a better experience to analyze failures and get run timing of test cases 

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.

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.

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.

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.

Sauce Labs has been helping us a lot in reducing the number of manual testing. By moving most of our test to the cloud and not running on the EC2 instance, we not only save time for the service but also the maintenance for the external servers. Sauce Labs is the best out there. They beat their competitors because of its price, customer support, and an amazing forum where you can ask and get answered really quickly. They never stop expanding. Whenever we have a new update for any browser, devices, etc. they make sure it will be in their devices and browsers farm so users can use it immediately.

Test engineers can now run more tests without bogging down the power of their PC which enables them to multitask, getting more work done.

I use it to maintain my own VM (Virtual Machine) farm of 25 VMs. The admin time I had to spend on maintenance and upkeep was a few hours per week, coupled with the fact that the up-time on the VMs was probably somewhere around 75% due to issues coming up in off-hours when I wasn't available to due maintenance/fixes/repairs. When I finally moved over to Sauce Labs, all this burden of doing the management was uplifted off my shoulders, and the up-time is nearly 100% for Sauce Labs VMs. On top of that, we can specify from an abundance of device types, OS's, browser versions, etc. when running our tests. Furthermore, the analytics side of things within Sauce Labs has drastically improved over the years and you can dive into your test results (pass/fail) to get a better understanding of how things are working over a period of time. Overall, Sauce Labs has provided us with a VM farm that is virtually always up and running and has taken the burden off of us/myself of maintaining the VM farm.

Sauce Labs has improved the testing side of our organization in the following ways:

Sauce Labs runs a huge number of browser and operating system combinations it allows our teams to worry more about testing our applications than maintaining a combination of browser and os. Either through the Selenium grid or running the browsers locally. In essence, it allows our testers to concentrate on testing the application and not worrying about the infrastructure. It also allows us to target new browsers without the required setup of the new browser.

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

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

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

The ability to share the tests that failed with the developers improved the overall efficiency of the team since there was no ambiguity on why a test failed. In addition we used some of the recorded test runs with the business to clarify the functionality of some of the more complicated features.

Sauce Labs has been a saving grace for our company. More so in recent years if I'm going by my own personal experience.

When you consider the positive plus points relative to having multiple devices, especially with the recent pandemic being under lockdown as well as just a general work from home situation before. Having Sauce Labs farm has been greatly beneficial to many people within the organization and has helped keep the project turn around time on track.

Supplying devices to a testing team of possibly close to one thousand testers and developers is a great undertaking but Sauce Labs has made this very easy and a welcomed solution.

Prior to moving to a continuous delivery model, we were on a classic two week regression testing cycle, mostly conducted via manual testing and manually-executed automated tests scripts in a large integrated testing environment. Upon shifting our SDLC to be more continuous, and rearchitecting our delivery pipeline, we were able to very quickly shift that long testing cycle to be integrated into the delivery pipeline itself by left-shifting these deep functional/regression tests to be executed during build time on our CI servers, and the implementation of these automated tests scripts being integrated into the development effort itself. Sauce Labs allowed all of this to happen by supplying the service needed to execute automated browser tests in from a CI server without having to implement or maintain our own proprietary grid of virtual machines.

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

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

My company was doing manual testing, I came in and built a framework using Sauce Labs; now it takes less than an hour for regression testing. Easy integration, increased the amount of codes that go out. I used to have to write the tests and perform manual tests; Sauce Labs, has changed all that.

We now find most browser-specific breakages before they hit production. This lets us push code out knowing it won't break in specific browsers, letting us be bolder in making larger changes across our codebase, frontend to backend.

We are now getting our Sauce Labs tests integrated with our CircleCI tests using Sauce Connect, which should dramatically decrease the time-to-issue discovery and save us time tracking down bugs once our tests catch them.

For mobile testing, Sauce Labs platform is great for functional tests. But the option to run tests on real physical devices is missing right now, so it’s impossible to run performance stress tests which is also very important to test mobile apps. This feature is actually supported by some other mobile testing vendors like Appurify. Hopefully, Sauce Labs will add this feature soon.

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

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

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

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

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

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

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

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

2. Frontend and Backend testing are now more connected

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

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

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

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

It makes my life much easier. 

This service has enabled several employees here to schedule tests and shift left with CI, which offers reliability and minimizes variability.

Cross browser and cross platform testing on our test case scenarios.

Testing across multiple devices and environments is now possible to do quickly and effectively.

Fast automation.

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

A more clean, lean, and bug-free site! We know our site works on mobile. We know our site looks good on Safari 8 1280x1024. We know android phones display the website perfectly. It makes sure that the user doesn't get a bad experience which is crucial these days.

I was just surfing to know about monkey runner and selenium tools, I encountered this cool tool and boom. Thousands of events can be fired easily to your device. Purchasing it would be worth it.

Yes, it allowed us to scale mobile testing across the globe.

Our organization has improved by testing our website on more devices and browsers than we currently have. We were able to test on the newest browsers without installing them on our computers, and test the newest operating systems without updating our mobile devices.

Sauce Labs provided the capability to test our application on multiple browsers. It allows us to not have to worry about setup and cleanup every time we want to run the tests.

It's easy to implement and is time saver. Initially, there were some stability issues with IE9 combos but have since been resolved. They have excellent customer service.

Sauce Labs has been very important to our project. We have used Sauce Labs to run our builds for both mobile and desktop web applications, as well as for nightly regression builds. The only reason we have stopped using Sauce Labs is due to project budget and the removal of an automated QA resource. Still, we have hooked up a pretty spiffy Jenkins and Sauce Labs in conjunction with several third party web-metric systems (such as YSlow) to capture a nightly set of performance data.

We have better validations.

We can now run daily and on demand automated tests.

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

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

We have been able to successfully integrate Sauce Labs into our automated test environment. From that we are able to run our test suite across multiple browsers overnight. This gives us a level of confidence that we previously didn’t have.

The other huge benefit we get from this product is the manual testing powers. When a client tells us that they’re having issues on a particular browser. We’re able to fire up that exact version and reproduce the problem ourselves.

I am a novice web-designer really just producing for my own hypnotherapy business. However, Sauce Labs is incredibly easy to use and has enabled me to make some changes so that the sites are (almost) universal across the range of devices and versions.

Running WebDriver scripts in house for a single, or few browser combinations is easy but once we started to scale up both in terms of browsers and parallel execution maintaining the grid became a pain so we offloaded it to Sauce. Now we have more combinations that we had before and don't have to worry about scaling our script execution ourselves.

With Sauce Labs testing, manual plus automation is very easy. It reduces running test times.

Currently, it's being used to run tests after deployment of some of our services so we know the status of the services. We also use it to run tests on a schedule so we can check the status of the services (if it's passing/failing). Because we can start up more than one VM through it, we can also run the tests in parallel, meaning tests can be completed faster than running it locally on one machine.

Has freed up huge amounts of time managing integrations. We have been able to move to a two-week sprint schedule, which had been bottlenecked by manual QA.

It has made our end to end testing roughly 25 percent faster.

In the past, I would have to find all the devices I could to live test pages. But now, I can virtually test the devices I need, plus a lot more devices that I wouldn't be able to get my hands on.

We've been able to reduce the number of applications running on our server, and therefore reduce the processor costs.

Prior to implementation we had a three month release cycle. Using Sauce Labs we were able to move to daily releases. Due to stable remote environment, we started believing in the product and now we are in true CI and CD.

Sauce labs is an easy to use hosted infrastructure for managing/launch all browser versions, mobile web browsers, and native mobile applications for seamless integration testing. I have used them at Bleacher Report while I was working as a QA Engineer for 2 years now and their has not been a tool that provided the same feature set and ease of use.

The fact that they contribute back to the open source community is also another great reason to use them. The tools they help deliver (like Appium) have helped our team scale while keeping our QA department very lean.

Our primary use case is for cross-browser automation. 

One more improvement would be the cost. It would be great if we can get more competitive pricing especially in terms of Real devices. Apart from this, I don't see any drawbacks. I love the support team. The user interface is very easy to integrate. It has solved so many hurdles very easily and my company is very happy.

Automation test runs are faster now with Sauce Labs.

Helps us free up local environment space and has freed up time for more exploratory testing with QA engineers. It improved our organization by reducing escaped bugs.

PROS: All that I mentioned above + the super awesome tech support guys, who are really technical when it comes to SL's product.

We realize that when you make a decision to buy Test Management Software it’s important not only to see how experts evaluate it in their reviews, but also to find out if the real people and companies that buy it are actually satisfied with the product. That’s why we’ve created our behavior-based Customer Satisfaction Algorithm™ that gathers customer reviews, comments and Sauce Labs reviews across a wide range of social media sites.

The data is then presented in an easy to digest form showing how many people had positive and negative experience with Sauce Labs. With that information at hand you should be equipped to make an informed buying decision that you won’t regret.

Sub-accounts allow multiple teams to test concurrently.

As we desgin websites for clients, we needed to make sure that our websites are compatible with the major browsers and are also mobile-compatible.

We have paralleled the tests, drastically reducing testing time.

I've been able to help numerous companies get up and running with Selenium quickly thanks to Sauce Labs.

Using Sauce Labs testing, it is faster and more accurate. I can run multiple tests on multiple browsers with a different set of devices.

• Testing is now faster using Sauce Labs.
• More work in less time.
• It can run on the cloud, which is very useful for me.

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

A cross browser test platform is really important for a web designer, Sauce Lab providing a really fast, functional and with good quality service.

As an advertising agency, we need to see how our online ads would look like on different browsers. Before we used the Google Chrome developer emulation tool, but due to a difference between what we saw and what the client saw in a real browser, we realized that something is wrong.

Automation running is very easy and fast now with the help of Sauce Labs.

We now have faster and more furious testing with a better quality of testing.

Testing is very fast with this tool. Also, running automation is a very easy task now.

Can run more tests at one time.

No need to purchase more real devices.

Works great.

Fast execution.

Testing is now easier and faster.

We are saving a ton of the required lead time before starting any tests. Before, we would plan months ahead on browsers/platforms to determine the needed support, and keep them ready as development happened. Now, we can be much more efficient. Our feature design to the delivery timeline is not tied down by our ability to test anymore.

It helped to integrate our performance testing and UAT, which helped to deliver a bug free software for our customers.

It was difficult for us to test our automation cases of real hardware. There is big combination of OS versions and different screen sizes. Sauce Labs has helped us to resolve this issue.

It was difficult for us to test our automation cases of real hardware along with a big combination of OS versions and different screen sizes. Sauce Labs has helped us a lot in resolving these issues.

Reliable access to VMs with built-in recording and log tools have improved release reliability and confidence.

Previously we were unable to test on real devices.

It improved our organisation by reducing escaped bugs.

Faster access to different versions of browsers, without needing to worry about hardware or software limitations; 99% uptime.

Sauce Labs tool has improved my testing efficiency to allow me to include devices I may not have had time to test out before. As most QA people know we get pinched in the time we are given to test. This tool allows for more testing to be done in that limited amount of time increasing the number of found issues before it reaches the customer.