Tests: Make Karma browser timeout larger than the QUnit one

Since the default Karma browser no activity timeout was lower than the QUnit
timeout, a single timing out test was interrupting the whole test run of
a browser.

The QUnit timeout is set to 1 minute so I set the Karma one to 2 minutes.

Closes gh-4943

(cherry picked from commit 4fd6912bfd8fffbfabc98a9b0789d28f10af0914)

diff --git a/Gruntfile.js b/Gruntfile.js
index 5a7bb1de7c6c21f8cbe0988198846e428207a271..50a835c9c67d9dac61f3f4720b09b62fa0e846dd 100644 (file)
--- a/Gruntfile.js
+++ b/Gruntfile.js
@@ -214,6 +214,10 @@ module.exports = function( grunt ) {
                                ],
                                reporters: [ "dots" ],
                                autoWatch: false,
+
+                               // 2 minutes; has to be longer than QUnit.config.testTimeout
+                               browserNoActivityTimeout: 120e3,
+
                                concurrency: 3,
                                captureTimeout: 20 * 1000,
                                singleRun: true