The initial setup was very straightforward.

We get a service rep that guides us on how to set up the tunnels to access our intra-sites, and then the device procurement is pretty straightforward. You give a list of what devices you want and they are put into each of the data centers, San Jose or Germany.

They do offer training as part of the agreement, as well, and we're in the midst of doing that because we're rolling out the mobile component in January.

Everything that I've needed, they've been there.

In terms of how much effort and how long it took to deploy, because it's on the cloud, the majority of the effort is on the Sauce Labs side. We've had some basic internal procedures to follow, but that doesn't really align with Sauce Labs. This included things like security approvals and stuff like that but overall, it was very little effort on our side.

Our implementation strategy was pretty straightforward. They make it available to us and then we do the training for the end-users. We have a registration list of about a thousand people, to which we have provided demos and documentation. Sauce Labs has a very robust document site. It's a combination of self-service education for the testers and developers in training. So, that's essentially our rollout plan.

We had to rightsize how many licenses we needed, based on user consumption, which was part of the planning phase. We did a full pilot where Sauce Labs gave us an area to access the mobile environment, and we ran our use cases before selecting the software.

Setting up Sauce Labs is straightforward. We initially set up a few sets of test cases, and it took some time to get familiar with the product and understand how we're going to integrate. Once it was up and running, we did our own thing. We've increased the number of test cases since then. We bundle all of that up then take the CI/CD piece and just run it. There's no post-deployment maintenance on our end.

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

Compared to the other cloud providers, it was easy. If you are technically strong, it'll take you just one day or eight hours. If you are a beginner to the cloud service providers or automation itself, it'll not take more than three days for you to get started with Sauce Labs. They provide a good knowledge base and good documentation for you to get started, which makes it an easy job.

Integrating Sauce Labs with the framework is a separate task. It took us 40 hours to integrate Sauce Labs with the framework we had.

In terms of maintenance, so far, it's only on the framework side. We just change the version that we want to run. A particular version might get outdated, so we just go and change it in our code, and it'll appropriately take that particular version on Sauce Labs.

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.

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. 

The solution was adopted before I joined the company.

It was already set up when I joined the company.

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.

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

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

I was not involved in the initial setup, but I was able to quickly adapt to using Sauce Labs after joining the company.

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

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

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

It was very easy. They have a wiki and a GitHub repo with all of the codes for every programming language. We can either use their template page or inherit it to our use cases.

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

Opening the network securely was challenging, but once established, it was very easy to start executing automated tests through the proxy.

Straightforward and easy, with good instructions in their knowledge base.

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

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

The initial setup was so easy that I thought I must be missing something. Since their service provides so many features I was certain that there must be some other options that I have to declare in the code to get those features, but no it was really that straight forward. 

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.

Pretty straightforward for the most part.

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

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

Straightforward for me.

Straightforward. Just integrate the client libraries and setup processes into your existing automation framework. Detailed documents are available on Sauce Labs’ website and its Github report.

There were some issues with our firewall and the tunnel for the SauceCloud. But we were able to overcome the hurdles fairly quickly.

Setup was straightforward because we had help from employees that had previous experience. Additionally, documentation was helpful and it is easy to reach out to a Sauce Labs representative for hands-on help.

Sauce Labs was very easy to use for it's basic needs, but using Sauce Connect was very confusing. I am a technical person, but the documentation needs to be a little more "dummy" friendly for nonprogrammers. This sites documentation is really more geared for the software engineer rather than the Qa Engineer in my opinion.

Straightforward since the cloud based examples were clear.

The initial setup is straightforward.

Somewhat complex in terms of configuring server.

It was easy.

Initial setup was easy. Our company already had the account open, but I simply added the sauce configurations to my test configuration file and ran the test.

Initial setup was somewhat difficult originally. That was due to multiple reasons, namely lack of actual programming experience on our behalf, and the documentation at the time was a mountain to climb. Sauce Labs has since updated this documentation, and we have since gained experience.

Easy

It was straightforward.

Pretty straightforward as the documentation is quite extensive.

It was quite straightforward. All we did was integrate Sauce's sample scripts into our base test and then modify, once we got the hang of it.

It was very straightforward but there was a slight learning curve.

It's a very simple initial setup.

The initial setup is straightforward.

The initial setup was simple and straightforward. The documentation is very helpful and good. You just need a username and access key to launch your automation tests.

Straightforward.

For a technical person, it's pretty straightforward.

It can be complex given the nature of Selenium and integrating with a third-party platform. But once you understand the fundamentals of Selenium and Sauce, it's simple enough to connect your tests to their infrastructure and capture the results for your own reporting needs.

The initial setup was straightforward and easy.

The initial setup was straightforward.

The initial setup was straightforward.

The initial setup was straightforward.

The initial setup is straightforward.

Straightforward.

Straightforward.

Not complex at all.

Straightforward.

The initial setup was straightforward.

Not at all.

It was built by my team before I joined the company.

The setup was straightforward.

Very straightforward. You just need username and access key to launch your automation test.

Unknown, as I was not part of the initial work to perform the setup.

Straightforward. You just need a username and key to start.