Sauce Labs Reviews

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.

Our primary use case for Sauce Labs involves running automated test cases for our web application. It works as a remote testing environment to execute these test cases efficiently and effectively.

The product's most valuable feature is the ability to provide an option to view test cases running live. Unlike traditional setups where you have to wait for test execution to complete before viewing the results, it allows you to monitor the progress of your test cases in real-time.

They could improve the platform's customer support services. Many users, including myself, have experienced significant delays in response times and unsatisfactory resolutions when reaching out for assistance. The support team often provides generic recommendations that do not address the specific issues raised, leading to prolonged downtime. Additionally, there needs to be more proactive communication and follow-up on reported problems.

Another area for improvement is keeping pace with updates to the latest libraries and technologies. For example, Sauce Labs' proprietary driver and Saucectl need to be updated more frequently to support the latest versions of popular testing frameworks like Playwright. This lag in compatibility means that users may miss out on critical features and improvements available in newer versions, necessitating workarounds or compromises in their testing workflows.

The solution is stable. However, due to the mentioned downtime, I've used BrowserStack and AWS devices before. In comparison, BrowserStack stands out as the top choice.

I rate the stability as seven out of ten.

Since Sauce Labs does not support certain features from other platforms like Playwright, scalability might be limited until those features are implemented.

I rate the scalability six out of ten.

The technical support services are not satisfactory.

Negative

The deployment typically occurs during scheduled downtimes, which are communicated to users about 15 days to a month in advance. To minimize disruption, these downtimes usually occur during non-US time zones. While we haven't experienced significant issues during deployments, occasional errors resulted in temporary blocks lasting two to five days.

It is an expensive tool. I am not sure about the exact pricing, but from what I know, it might range from $24,000 to $70,000. We have more than 60 to 70 VMs, so the cost is on the higher side.

For those exploring alternatives, options like Augment or setting up test cases on AWS machines using tools like Harness could offer more cost-effective options.

Cross-browser testing capabilities provided by Sauce Labs have significantly impacted our development process. This feature allows us to test our application across various browsers and platforms, ensuring compatibility and consistency for our diverse user base. We can access remote mobile devices, which is invaluable for testing different types of devices our customers use. When customers report issues related to specific devices, it enables us to replicate the environment, load our application onto the remote device, and investigate the problem efficiently. This capability accelerates our debugging process and helps us identify and resolve issues promptly.

It has significantly enhanced our testing accuracy by approximately 50%. Previously, we relied on server setups to reproduce bugs, which was time-consuming and often led to delays in bug resolution. However, we now experience a much quicker turnaround time in bug reproduction. It is crucial because before developers can address a reported bug, they must first reproduce it to understand its root cause, whether it's related to the device or the operating system.

The analytics and reporting features have greatly assisted us in identifying and addressing issues within our testing process. One of the main reasons we chose Sauce Labs was its recording feature. Previously, we ran our test cases in headless mode, where the browser operates in the background without opening on the screen. This made it difficult to pinpoint the exact location of test failures. However, after integrating Sauce Labs, we could view recordings of failed test cases, allowing us to easily identify the cause of failure directly from the user interface.

I wouldn't recommend it to someone because I think the pricing is exactly the same as other tools available providing better support and scalability. I would prefer them to go with other tools first.

I rate it a five out of ten.

We use it for automation testing of our e-commerce product. We also have some apps that use React Native and they deploy to mobile devices. We also do responsive mobile testing. That means we test anything that hits a website with a browser, or on a phone through React Native, through Sauce Labs.

We also use their VMs and their video recordings.

We use the automation testing and the ability to run it against many device configurations. It's very convenient.

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.

We send over a configuration object in JSON and it's very convenient to be able to do it that way.

Also, Sauce Labs is optimized for automation and integration with the major CI/CD platforms and developer tools. We have an integration with App Center that we're working on. They have a storage API that lets us retrieve APK and IPA, iOS and Android builds, install them on the phone, so that we can continue testing. They integrate well with Jenkins.

It's super-important that the solution is optimized for integrating with these major CI/CD platforms and tools because at the manager level, they want integrations out-of-the-box. They want to reduce internal tooling or internal custom stuff.

We use the browser/OS combinations, mobile emulators, and real mobile devices. It's huge having multiple types of testing available in a single platform. It's definitely a competitive differentiator. For example, Microsoft has its own test automation through App Center and there's also BrowserStack and other competitors. It's very important to be able to tell the decision-maker, "Hey, Sauce Labs already has it, so don't worry about it."

They also have a huge number of browser OS combinations, mobile emulators, and real mobile devices. The solution covers a ton of combinations, probably almost any combination you would encounter when a custom reports a bug. That is great for QA to be able to reproduce that issue on that exact same device. 

Sauce Labs maintains physical devices in their data center. They go out and buy the device and provision it for you when you have a real-device contract and licensing, and that's also huge. You're on a physical device.

And for the mobile emulation, which is great as well, they not only have Apple devices, but different iOS versions, which is a huge feature, including different Safari versions on different macOS versions and different Windows versions. More often, you only have a subset of what Sauce Labs offers because people will be mostly using cutting-edge stuff or people might be using mostly legacy. But Sauce Labs runs the gamut and they have all kinds of devices. You'll run out of combinations that are relevant to you before you run every single combination that Sauce Labs has.

I'm pretty happy with the areas of the product that I've been using. The Appium part, even though Appium feels pretty new, is still supported. They support Selenium 4 as well as several other test frameworks, such as Cypress, XCUITest, Puppeteer, and Espresso. Sauce Labs also has artificial intelligence, the AutonomIQ test framework. With AutonomIQ you can have manual QA where you submit an Excel file and then it just automatically creates a test. That's a killer feature.

They offer so many things that we haven't even tried yet, like performance testing and courtesy Docker containers. They are continually updating the documentation. They have performance testing and visual testing. They even acquired Backtrace, which is some sort of error monitoring solution.

I've been using the Sauce Labs solution for about a year and a half. Our company has been using it since 2016.

We haven't had any issues. Sauce Labs has been more reliable than we have.

Scalability is connected to the pricing. The solution is scalable if you have the money to scale. It's based on what they call concurrency units, and they can get expensive.

We have about a dozen users of the solution. They are mostly involved in test automation, SDET.

Support is great, including the support ticketing. Every time I've had a support ticket, they have replied. If they need to, they escalate it. They'll answer technical questions about things like IP whitelisting, and they'll take a look at the screenshots we provide or links to tests that are failing. Their support is empowered to really probe and ask questions.

We haven't used their expertise to help integrate automated testing into our CI/CD pipeline. We have generally solved every issue that we've encountered so far, but they do offer software architecture assistance. It's good to have someone at the software level, and not just sales or product support. If I say I'm having a development issue, it's good to be able to talk at that level, using the jargon.

Positive

When I came in, the solution was already set up. Tweaking it has been easy.

One of the great things about it is that there's no maintenance. We just throw a JSON content object over and then they take over from there.

I can't speak about metrics, but we're able to run automation tests in parallel and that helps with releases. It's definitely a critical part of the whole process. And even moving forward to cloud, it's definitely a big part.

They could improve on the pricing because it seems pretty expensive. I'm sure it's justified, but it's expensive.

For some of the features we aren't using yet, I believe we do need to add new licenses, but for others, we just need to try them out. We just need to have the bandwidth and time.

We use other products for front-end testing but there's no significant reason we couldn't do it with Sauce Labs. It's not lacking in that solution. We use other tools mostly due to dev team mindset. They prefer something more local to their use and something they're familiar with. If we were to push the QA side to do performance testing through Sauce Labs, they'd be open to it. 

It's not only Sauce Labs, as a vendor, that offers automation, but there's BrowserStack and others that also offer it. But using Sauce Labs has been great.

Definitely try it out. They are very friendly about giving you trials and then following up with monthly syncs. They'll connect you with a sales rep, an engineering-type salesperson, and you can have monthly chats with them. They'll keep you updated about their product updates. It's free to try it. Once you try it, I think you'll see the benefits.

Latency due to Sauce Labs being a cloud-based solution hasn't been a concern at all. It runs automatically and sometimes it runs during off-hours, so any latency is not a big deal for us. For flaky tests we use Ruby, which has a rescue retry pattern that we use a lot and that's really helped. Test flakiness is just a reality of test automation and we have good workarounds for it. So cloud latency in Sauce Labs hasn't been an issue.

We've been pretty happy with Sauce Labs. I'd probably have to think pretty hard about what it is lacking. It's been working for us and whatever we throw at it, including Appium, mobile device simulation testing, and being able to support multiple apps. The automation testing has been great. The SC (Sauce Connect) Proxy is pretty friendly. There are the VMs and the video recording. Overall, we've been pretty happy with it. I'd be hard-pressed to find a glaring issue that hasn't been addressed.

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.

Sauce Labs is a SaaS service hosted on the company's cloud. They have a number of cell phones and mobile devices housed on their cloud, and my team can perform tests on these devices from around the world. We have about 50 users right now, including business analysts, testers, automation, QA, developers, product owners, and third-party vendors. 

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.

You can access Sauce Labs remotely from different locations. This feature has been especially useful during the pandemic because the members of my home team aren't in one location anymore. The ability to remotely access devices has been essential.

Sauce Labs provides a single visual snapshot for visual and functional regressions, which we can use as proof when there are defects. It also helps us leverage our existing tools, especially the automation component. Sauce Labs has broad coverage, allowing us to test both functional and visual aspects of the UI. This is crucial because we need to see how the application displays on the various types of devices out there.

We've been using Sauce Labs for around a year and a half.

Sauce Labs' stability is good. We haven't experienced any downtime.

Sauce Labs' scalability is good. It's possible for us to scale higher, so I don't foresee any issues with that.

Sauce Labs' support has been great. I would rate them 10 out of 10 because they respond quickly when we have a problem, but we seldom have issues.

Positive

Setting up Sauce Labs was straightforward because most of the work was on the vendor's side. I think it only took a few days. We didn't deploy it into our system. Sauce Labs set it up for us. It requires some maintenance but not a dedicated person. It's one person spending around 10 percent of their time on this. We have an admin who adds users, so it's not really maintenance—more like administration. 

We purchased the solution through a reseller, and everything went fine. 

I don't have any hard data, but we have seen a return. Sauce Labs expands the number of tests we can run with our staff. For example, if we were limited to five physical devices, we could only test with five people. Now, our testing is only limited by the number of staff. From that perspective, it's a return on our investment.

The pricing model of Sauce Labs could be more flexible. Sauce Labs has just one price for the type of solution and a set number of devices. Other solutions have a fee for the base solution and an additional cost per device. 

If you're a smaller organization, you have to consider your needs. Some smaller companies still need to test various devices, so my advice is to start small and scale up as needed. We had initially planned to start big, but that would have been a big waste.

Eventually, I got approved to expand, but it didn't make sense, so I would advise starting smaller. Everything is about costs. Structure it in different phases. If this is something new for you, start with fewer devices to see if the solution is the right for you because it's costly.

You always have to weigh how much the solution costs versus buying physical devices, so I would say go for a phased approach. That way, you can determine whether it pays for itself. We did a phased approach, and we didn't have to go any higher for at least a year. We might go a little higher based on what we're doing this year. We're still evaluating that right now, so we'll see. 

I don't remember the names of the other solutions we evaluated, but we were going through resellers, and those resellers were using other companies. 

I rate Sauce Labs nine out of 10. If you're thinking about implementing the solution, you should talk to Sauce Labs about your needs and challenges. Their salespeople have a technical background, so they have enough knowledge to help you determine if this solution is right for you.

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. 

I work as an automation engineer using Selenium WebDriver with Java, and API automation using Rest Assured with Java. I have also worked with Docker integration on AWS.

Additionally, I have experience with performance testing using JMeter.

We use Jenkins for our CI/CD pipeline. Our project is integrated with Jenkins, which we have configured to work with our repositories on Git.

We use recording features, which are available through Google plugins. However, they are not very robust as many details can't be captured through this method. Selenium plays a significant role here, as it allows us to modify or update scripts based on our needs. Improvements can be made by using Selenium.

So, the analytics and reporting features helped in identifying issues more efficiently.

I like the mortgage domain or a banking domain project.

Sauce Labs can include new technologies like generative AI, which can reduce the human effort in writing test cases. For example, in my current project, we reduced the time it took to complete user acceptance tests from six hours to three. There's potential to further optimize the execution cycle time of test scripts.

I have been using it for the past seven years. 

I never faced any issues with the stability. 

I would rate the scalability a seven out of ten.

Technical support is equally very important. If you talk about anything deployed to production, and the project is live, customers are using that, and they might face some issues, some functional issues. That's when support people play a role in identifying the fix or the incident. 

Based on that, we create an incident based on the customer defect or whatever.  

Once the incident gets raised, the support will play a role in working on that particular incident. If it's a code-based incident, administration, or integration issue, support people play a big role in resolving those issues before reaching the exact developers.

We have two types of setup processes: our SPN (Sauce Connect Proxy) and Git. The SPN setup isn't very difficult. However, Git, in line with current trends, is very user-friendly. It offers great features for building and deploying within the repository. 

You can manage code updates efficiently, with developers pulling and pushing changes. While you can do similar things with SPN, Git offers more techniques and features.

On the development side, there's a thorough deployment process with various checkpoints before the code reaches production. In terms of your automation setup, the first step is building your project. 

Jenkins can help here, as it handles downloading the necessary JARs and WAR files to run your tests on Sauce Labs. So, the time depends on how long the build process takes – that doesn't directly involve customer time. 

Once the build is complete, you can begin test execution immediately.

I would recommend it. Generally, if you already have Selenium as a free tool, I suggest sticking with that. However, if you're primarily focused on desktop-based applications, then UFT becomes necessary, and you'd need to purchase a license. But, if you're comfortable working with Webex applications, then definitely go with a tool like this.

Overall, I would rate the solution a seven out of ten. 

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.