Browse files

Tests: Increase QUnit timeout

Android 2.3 is very slow & times out a lot in async tests, they have to be
restarted multiple times to settle. Long test execution is not a huge problem
as Android 2.3 is tested only periodically during the night, unstable tests
are a bigger problem. This might mitigate that.

In a regular scenario almost all tests should pass so increasing the timeout
for all browsers shouldn't have a huge impact on overall test time.

Closes gh-2232
  • Loading branch information...
mgol committed Apr 26, 2015
1 parent f6de5a9 commit ff18d8e2060ae7c15c7694dc6bcbbeb9cbfbdaa4
Showing with 1 addition and 1 deletion.
  1. +1 −1 test/data/testrunner.js
@@ -15,7 +15,7 @@ var oldCacheLength = 0,
// Max time for stop() and asyncTest() until it aborts test
// and start()'s the next test.
QUnit.config.testTimeout = 2e4; // 20 seconds
QUnit.config.testTimeout = 12e4; // 2 minutes
// Enforce an "expect" argument or expect() call in all test bodies.
QUnit.config.requireExpects = true;

0 comments on commit ff18d8e

Please sign in to comment.