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.

(cherry-picked from ff18d8e2060ae7c15c7694dc6bcbbeb9cbfbdaa4)

Closes gh-2232

diff --git a/test/data/testrunner.js b/test/data/testrunner.js
index 4719a67d9c14a365fd38e772aa9e4946ec38c1f6..d1e8b8fa8edae77b1c0a7514f30aec79b2386c56 100644 (file)
--- a/test/data/testrunner.js
+++ b/test/data/testrunner.js
@@ -16,7 +16,7 @@ var reset,
 
 // 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;