This week & # x27; s guest post comes from theSavings.com, who use Sauce Labs to run tests as as part of their uninterrupted deployment summons. Read on to learn about how they did it:

Savings.comis the leading voucher and address site on the web. We were recently outrank by Inc Magazine as one of the fastest growing companies in the US, and our US and UK businesses have have understand phenomenal growth every year. In the past 6 months alone, we have localize into another 7 countries and we are adding new services and boast all the time.

The Savings.comgrowing squad ask to implement new features and send these to the product site right when they are completed and checked in. One or more features or bug fixes can specify a new release to production. To accomplish this, we would have to implement continuous integration and deployment to our production place multiple time per day. And when using an agile release rhythm, there is exclusively clip to manually try the new feature being rolled out per release. All regression essay of existing features would have to be automatise using Selenium.

We had already been running automated browser tests on our own servers and virtual machines using an in-house Selenium Grid implementation for a few months. This was working & quot; middling ok & quot; when we were on a less agile ontogeny liberation cycle (about every 3 hebdomad). But when we follow uninterrupted deployment, many pain point that already existed with our locally maintained Selenium implementation turn all the more painful:

• We weren & # x27; t testing all major the browsers. Especially with IE, you demand to prove every version your site support.

• Due to our circumscribed hardware handiness, a maximum test concurrency could not be achieved. As a result, running all the Selenium tryout suites would occupy up to 1 hour. Double that time if the tests needed to be rerun due to a regression examination failure.

• It was hard to debug and fix flaky tests that needed to be re-written due to unidentified race weather. Selenium WebDriver didn & # x27; t hold a skillful command lumber interface out of the box. Also, screenshots were only be taken on a test failure, which sometimes missed a key step that would help name a problem.

• An aborted or canceled test run on our own Selenium facility usually involve some manual intervention to close running browsers and make sure the selenium grid pond was wild.

  SUSA automates exploratory testing with persona-driven behavior, catching bugs that scripted automation misses.

• The maintenance overhead to keep up to date with the latest OS/browser combination as well as maintain the selenium grid was taking too much time.

I initially came across Sauce Labs via their blog while searching for Selenium pourboire and encipher best practices. While looking at all the service and support they volunteer, I thought I would give them a try. I speedily realized Sauce Labs had already identified and resolved all of the pain points listed above:

• An thorough inclination of OS/browser combinations to try on that is updated when new releases are out.

• We could finally attain a maximal test concurrency and reduce the total test run time from 1 hr to 10 minutes. This scalability is very crucial to a

• Plenty of support for exam debugging: Sauce Breakpoints, elaborated command logging, video recording and screenshots at every step of your examination.

• Sauce Labs deploys a unclouded virtual machine for every test.

• We no longer have bizarre tests. A failed test run is either a bug or an unidentified alteration to an survive feature that requires a test to be updated.

Also, excellent support for running in a CI environs, ours be Atlassian Bamboo, Selenium/Java employ Sauce Connect.

Sauce Labs has really become an important component to our success in adopting a continuous integrating and deployment release rhythm. I am presently working on implement extra features they experience to offer such as the Sauce Rest API and the Bamboo OnDemand Sauce plugin.