feat(runner): allow bypassing the selenium standalone server if running only chr

Using the config option `chromeOnly` now enables running ChromeDriver directly,
without going through the Selenium Standalone. The chromedriver binary should be
available in your PATH, or should be specified with the config option
`chromeDriver`.

Author: juliemr

lib/runner.js

@@ -3,6 +3,7 @@ var path = require('path')
 var fs = require('fs');
 var webdriver = require('selenium-webdriver');
 var remote = require('selenium-webdriver/remote');
+var chrome = require('selenium-webdriver/chrome');
 var minijn = require('minijasminenode');
 var protractor = require('./protractor.js');
 var SauceLabs = require('saucelabs');
@@ -110,7 +111,10 @@ var setUpSelenium = function() {
     });
   }
 
-  if (config.seleniumAddress) {
+  if (config.chromeOnly) {
+    util.puts('Using ChromeDriver directly...');
+    deferred.fulfill(null);
+  } else if (config.seleniumAddress) {
     util.puts('Using the selenium server at ' + config.seleniumAddress);
     deferred.fulfill(config.seleniumAddress);
   } else if (sauceAccount) {
@@ -195,9 +199,16 @@ var runJasmineTests = function() {
   // TODO: This should not be tied to the webdriver promise loop, it should use
   // another promise system instead.
   var runDeferred = webdriver.promise.defer();
-  driver = new webdriver.Builder().
-      usingServer(config.seleniumAddress).
-      withCapabilities(config.capabilities).build();
+
+  if (config.chromeOnly) {
+    var service = new chrome.ServiceBuilder(config.chromeDriver).build();
+    driver = chrome.createDriver(
+        new webdriver.Capabilities(config.capabilities), service);
+  } else {
+    driver = new webdriver.Builder().
+        usingServer(config.seleniumAddress).
+        withCapabilities(config.capabilities).build();
+  }
 
   driver.getSession().then(function(session) {
     driver.manage().timeouts().setScriptTimeout(config.allScriptsTimeout);

referenceConf.js

@@ -9,6 +9,10 @@ exports.config = {
   // 2. seleniumAddress - to connect to a Selenium server which is already
   //    running.
   // 3. sauceUser/sauceKey - to use remote Selenium servers via SauceLabs.
+  //
+  // If the chromeOnly option is specified, no Selenium server will be started,
+  // and chromeDriver will be used directly (from the location specified in
+  // chromeDriver)
 
   // The location of the selenium standalone server .jar file.
   seleniumServerJar: './selenium/selenium-server-standalone-2.37.0.jar',
@@ -20,6 +24,9 @@ exports.config = {
   // the system property webdriver.chrome.driver. If null, selenium will
   // attempt to find chromedriver using PATH.
   chromeDriver: './selenium/chromedriver',
+  // If true, only chromedriver will be started, not a standalone selenium.
+  // Tests for browsers other than chrome will not run.
+  chromeOnly: false,
   // Additional command line options to pass to selenium. For example,
   // if you need to change the browser timeout, use
   // seleniumArgs: ['-browserTimeout=60'],