Last workweek our friends atCircleCIshowed us how to securely run cross-browser front-end test on the cloud expend their host Continuous Integration service. We ’ ve long be advocates of good continuous integration practice and have developed a few plugins for some of the more mutual CI servers out there. We ’ re superintendent excited to add CircleCI to our inclination and even more delirious about how leisurely it is to get it going!Uninterrupted Integration in the CloudContinuous Integration, if you don ’ t already cognise, is the process of construct your app frequently from a shared source codification deposit and run tests to make sure everything works. If your test don ’ t walk and the build is not successful, the code that was check in since the final full build is where the defects were introduced, and so problems are lots easier to find and fix quickly. Maintaining a local CI server can be a hassle. Anyone who ’ s spent any considerable time configure Jenkins chore with all it ’ s various plugins and tasks can state you all about it. CircleCI, on the early hand, integrate directly with GitHub and can actually * infer * necessary scene directly from your codification (if you ’ re following good development practices for that words and environment) and so many projects just magically build themselves on CircleCI without any extra constellation on your part. It ’ s like three click from zero to CI. Pretty sweet! If you do need to tweak or customize any setting, you can easily do so by describing those settings in acircle.ymlfile placed in your repo.Running Tests on Sauce Labs BrowsersSauce Labs is the world ’ s largest cross-browser client cloud. We host o'er 375 different configurations of operating systems and browser so you can ensure that your app works on all the specific program and adaptation you need to support. These days that ’ s an ever-growing list! So it makes sense to run these tryout with your continuous integration process so you cognize things act across the board and you don ’ t end up pass a bunch of time and hassle trying to run down bug that were introduce much earlier in the development cycle. Now, if your build deploys your codification to a publicly accessible surround, CircleCI will only fulfill your Selenium tests and you probably won ’ t need to configure anything, since Sauce Labs browsers will be able connect to that environment over the public network. However, if you require CircleCI to execute your tests topically in it ’ s build containers, you ’ ll need to use Sauce Connect. Sauce Connect is a secure tunneling usefulness which allows you to fulfill tests behind firewalls via an encrypted connection between Sauce Labs and your test environment. When you run Sauce Connect yourself, you typically do it from a command line or shell script and issue your Sauce Labs story certificate as parameters. With a CircleCI build, you ’ ll need to set it up in the circle.yml file so it can be launched as part of the build process and those tests can run inside the local container. All that ’ s actually involved here is recount the build task where to find Sauce Connect and how to start it up with your chronicle credentials. The first part is downloading and unpacking the Sauce Connect file, which you add as a custom dependency debut in your circle.yml:

dependencies:
post:
- wget https: //saucelabs.com/downloads/sc-latest-linux.tar.gz
- tar -xzf sc-latest-linux.tar.gz

The second part is to add your credentials, establish the tunnel, and check that it ’ s run before kicking off the examination. You ’ ll put these line in the ` test ` section of circle.yml:

Pro tip: Tools like SUSA can handle this autonomously — upload your app and get results without writing a single test script.

test:
override:
- ./bin/sc -u $ SAUCE_USERNAME -k $ SAUCE_ACCESS_KEY -f ~/sc_ready:
background: true
pwd: sc- * -linux
# Wait for burrow to be ready
- while [! -e ~/sc_ready]; do sleep 1; done

That ’ s all there is to it. You can find out the particular here and see a full example onGitHub. And CircleCI has a nice littleutilityto help you add your credential as environs variables so that they are not visible as plain text in the repo. With CircleCI tackling all the necessary employment imply in supporting your continuous integration process and Sauce Labs hosting the world ’ s most blanket cross-browser client cloud, you can be free of the price and hassles of managing all these system and grid and get back to focusing on the business of making great software. -Michael Sage, Principal Technology Evanglist, Sauce LabsMichael Sage is a Principal Technology Evangelist at Sauce Labs. He helps software teams develop, deliver, and care for great apps. He ’ s lived through two or three engineering revolutions and require a few more to come, and finds the expectation incredibly stir. A indigene of Philadelphia, he ’ s get San Francisco his home for over 25 years, but still can ’ t find a good wedge there.