fix(cli): Make the total timeout configurable.

angular · Oct 8, 2013 · e34a4ab · cristifilip · Oct 16, 2013 · juliemr
1 parent 7d74184
commit e34a4ab
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 1 deletion.
diff --git a/lib/cli.js b/lib/cli.js
@@ -27,6 +27,7 @@ var config = {
   seleniumArgs: [],
   seleniumPort: null,
   seleniumAddress: null,
+  allScriptsTimeout: 11000,
   capabilities: {
     'browserName': 'chrome'
   },
@@ -146,7 +147,7 @@ var startJasmineTests = function() {
       withCapabilities(config.capabilities).build();
 
   driver.getSession().then(function(session) {
-    driver.manage().timeouts().setScriptTimeout(11000);
+    driver.manage().timeouts().setScriptTimeout(config.allScriptsTimeout);
 
     id = session.getId();
 

diff --git a/referenceConf.js b/referenceConf.js
@@ -35,6 +35,10 @@ exports.config = {
   // seleniumAddress: 'http://localhost:4444/wd/hub'
   seleniumAddress: null,
 
+  // The timeout for each script run on the browser. This should be longer
+  // than the maximum time your application needs to stabilize between tasks.
+  allScriptsTimeout = 11000,
+
   // ----- What tests to run -----
   //
   // Spec patterns are relative to the location of this config.