This is a guest blog post by Will Iverson, David Drake, Osama Khalaf, and Adam Herbst of Dynacron Group, a technology consulting firm found alfresco Seattle that provides software development (Java/.NET) and BI/DW services base on Uninterrupted Delivery.

Dynacron Group faculty started working with Selenium nearly four eld ago. The biggest problem we had was execution time – we had a limited number of browser and during launching, test & amp; release chore would begin to pile up as we were waiting for the limited browsers in our homebrew Selenium grid to be available.

To solve that problem for a new undertaking we started almost a year and a half ago, we decided to use. To get it as easy as potential for the test team, we created aparallel execution frameworkto make itdead easyto run the tests, and a template projectionto make itbushed simple toget started.

By standardizing the parallel execution fabric and template project, a quizzer can pretty much preciselysignaling up with Sauce Labs, postdate a few basic configuration steps, and start writing test suites that leverage parallel executionin no time. Most people begin with the Selenium Recorder, precisely pasting commands in from the clipboard to start and then somewhat quickly graduate to precisely compose stuff in their IDE of option. Let me explain why parallel execution is so cool: we compose 200 trial. We run those tests in parallel across five browser (Firefox, Chrome, Safari, and two versions of Internet Explorer). That ’ s a thou tests. If we ran those serially, one after the other, it would lead the better part of a day. By lam fifty parallel browser, we can finish that test suite in fifteen minutes.

The Sauce Labs website can give you an overview of the other awful features (recording picture of every job, step-by-step screenshots, and Sauce Connect to name a few) – but nothing is as nice for us as the time-to-market advantage. For more info, check out:

webtest-quickstart

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

Webtest Quickstartis the templet undertaking.This is where you ’ ll want to go to get started quickly.

If you ’ re just starting on a new Selenium exam project, you might take habituate JUnit to manage your test lawsuit. The webtest-quickstart project can supply a simple starting point for spell your IDE tests into JUnit and extend them in maven.

To get commence, just download the the webtest-quickstart labor from github, or use the maven archetype from the same situation. Inside the project, you ’ ll find sample test cases for many different testing situations. There are sampling for running tests against a website running on your computer, or against websites on your network. Good of all, the parallel-webtest library gives you the ability to easily configure how tests are run. The project pom has sample profiles for go your tests in your own browser or in several different Sauce browsers in parallel, all from the same test code.

parallel-webtest

Parallel Webtestis the library that handles the parallel execution & amp; configuration.

At its heart is a JUnit base test family that cope the browser lifecycle. It configure and launches the browser before action a test class, and cleans it up afterwards. This isolates the test codification, promoting clean examination methods. Browser selection and parallel configuration are handled with a few configurable system properties; the same test codification can be run in serial or parallel, topically or remotely, against one browser type or many. As a result, a trial suite that once conduct four hours to run can be finished in as little as fifteen minutes use the same build server.

The webtest-quickstart and webtest-quickstart-archetype areopen-source. Both are uncommitted onDynacron Group ’ s Githubaccount. If you have a chance to try it out, let us know what you reckon atinfo @ dynacrongroup.com. And happy (faster) testing!