STUDY

Since we can parallelize the tests, they run very fast. We’re covering hundreds of tests in under about 20 minutes...[I have heard from QA] nothing but good things about the mobile capabilities, especially compared to what we were using previously, so the [QA] teams are liking it.

We don’t have to worry about making sure the devices are healthy or [scaling]. Having Sauce [Labs] manage [devices] saves time for my team on the administration. It’s been much more hands-off. … It’s just nice. It just works.

[Sauce Labs] gives you confidence in the definition of 'done' — so that the teams that are in high-pressure situations can deliver software quicker, faster, and more iteratively.

We have a lot more logs available to us. We have screenshots and recordings, all of which we wouldn’t have had in the past. We may have had some basic logs, but not to the level that Sauce Labs provide us. It’s definitely a lot easier to find out where an issue has occurred.

We are catching a lot more [isues] in QA, [which is] great. ... When [code] comes into our test environment, there's nothing that's being 'thrown over.' ... The defects are getting found earlier on, and we are finding a lot more.

We have definitely improved in terms of how much we’re delivering. It’s meant that, from a QA perspective, we can pick up a lot of backlog items we had for coverage. We’re able to add stuff into our pipelines to cover different markets [— including] India, Sweden and Mexico. … In the past we may not have run tests on them at all.

We definitely don’t have as many production issues as we’ve had in the past, and I think the general stability of our products has improved. Before, a lot of blame would have come on to QA: ‘how did we miss this’, ‘how did we [not] catch that?’ That’s died down quite significantly since we’ve been using Sauce Labs.