We deployed in-house and we are happy with the support provided by the vendor.

We had help from Sauce Labs during the deployment, but they weren't on site. We did everything over the phone or on WebEx and Zoom. We had two QA architects building the framework doing the integration. We had about four or five technicians from our company, including two or three on the application side, and definitely two from testing.

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

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.

The initial setup was done in-house.

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

We developed our test framework based on Sauce Labs in-house. There was no other vendor team.

We worked closely with Sauce Labs' support and technical teams to implement the solution properly in-house.

In-house.

I am a user in my company, I had no interaction with the vender.

Purchased and implemented directly through Sauce Labs.

I implemented it in-house since I was tired of managing 25 virtual machines and 12 mobile devices and 5 physical machines on a seemingly daily basis.

We deployed with an in-house team.

In-house.

I implemented in-house.

An in-house team implemented it.

We implemented through an in-house team.

Implemented in-house.

The implementation was done in-house.

In-house

We implemented it in-house.

Our in-house team performed the implementation. For advice, it’s a lot like setting up Selenium Grid. One thing we did was have an Environmental Variable “ISTESTLOCAL”, we use this as a gate to whether or not our tests should run on Sauce Labs or not. This is very helpful in increasing the speed which we can write and debug our own tests.

Also, if using the Bamboo plugin, make sure to check the settings page as there is a list of already in use environmental variables set when Sauce Labs runs.

In-house.

In-house.

In-house.

In House.

The implementation was done in-house.

We implemented in-house

In-house.

I help companies implement Selenium. When implementing Sauce (which is a given unless there are constraints that prohibit it) I either update their existing test code to work with it, or implement my open source Selenium framework for their testing needs (http://github.com/chemistrykit/chemistrykit) which comes with Sauce support built-in.

We used an in-house team.

We implemented in-house.

It was implemented in-house.

In-house.

In-house.

In-house.

In-house.

In-house.

In-house.

Ourselves.

In-house.

We implemented this in-house.

In-house. It's very easy for any non-technical user to follow the descriptive documentation.

The implementation was done in-house.

Implemented myself.

Eight out of 10.