aboutsummaryrefslogtreecommitdiffstats
path: root/Gruntfile.js
diff options
context:
space:
mode:
authorMichał Gołębiowski-Owczarek <m.goleb@gmail.com>2021-10-30 00:56:31 +0200
committerMichał Gołębiowski-Owczarek <m.goleb@gmail.com>2021-10-30 00:57:20 +0200
commita51eec74846e2875345e16c737edcc76481f0e34 (patch)
tree0d8aaed18e5a23e4f8c2936b74b9a78046216ac4 /Gruntfile.js
parent509eeb892c85fca0f489a2af5bf334285e9330de (diff)
downloadjquery-a51eec74846e2875345e16c737edcc76481f0e34.tar.gz
jquery-a51eec74846e2875345e16c737edcc76481f0e34.zip
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)
Diffstat (limited to 'Gruntfile.js')
-rw-r--r--Gruntfile.js4
1 files changed, 4 insertions, 0 deletions
diff --git a/Gruntfile.js b/Gruntfile.js
index 5a7bb1de7..50a835c9c 100644
--- 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