Building a CI System Using Selenium Builder, GitHub, Travis and Sauce Labs

Posted Mar 12th, 2013

Today I'm going to show you how you can use Selenium Builder with GitHubTravis, and Sauce Labs to make a continuous integration solution for your website that's all on the Internet, nothing stored locally. You can either follow along with the demo video below or read on for the written tutorial. The great thing about this setup is that if you put your site code and your tests into the same GitHub repository, then whenever you update the site code, and whenever you update the tests, Travis will rerun your Selenium tests on Sauce OnDemand - and then send you an email about whether or not they still work! Screen shot 2013-03-07 at 14.11.55 So you can get a full Selenium CI solution by putting together these components. And because they're all components, if you want to use something else in part - for example Jenkins instead of Travis - you can construct your own solution. For now I'm going to show you this set of four things that work really well together. The great thing about this is that you store everything on GitHub, so all your tests are stored in the cloud, nothing is stored on some local machine somewhere. You can record and edit tests from any computer that runs Firefox. You can access your tests, edit them, & play them back locally. And all of the actual execution of the testing - the CI - is handled by Travis and Sauce. So you actually don't need to build any of your own testing infrastructure!

OK! So how do you actually do this?

The first thing you need to do is install the plugins. You go into Selenium Builder, you go into Plugins, and you just click install on GitHub integration and Sauce. Restart Builder. Screen shot 2013-03-07 at 14.12.19 Thanks for following along!


Written by

The Sauce Labs Team


Topics

SeleniumGithub