From b8cf79895ebcaf75e97166f24a49a885a2f84c59 Mon Sep 17 00:00:00 2001
From: Jarek Radosz <jradosz@gmail.com>
Date: Sat, 15 Apr 2023 14:34:13 +0200
Subject: [PATCH] DEV: Set QUnit per-test timeout (#21102)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

60s is a lot, and I'd prefer 15s, but the first test in a suite can take up to 40s. 60s is still better than `Infinity` 😌
---
 app/assets/javascripts/discourse/tests/setup-tests.js | 1 +
 test/run-qunit.js                                     | 2 --
 2 files changed, 1 insertion(+), 2 deletions(-)

diff --git a/app/assets/javascripts/discourse/tests/setup-tests.js b/app/assets/javascripts/discourse/tests/setup-tests.js
index 78bdbf47c0b..6f1d61ac570 100644
--- a/app/assets/javascripts/discourse/tests/setup-tests.js
+++ b/app/assets/javascripts/discourse/tests/setup-tests.js
@@ -202,6 +202,7 @@ export default function setupTests(config) {
   setupDeprecationCounter(QUnit);
 
   QUnit.config.hidepassed = true;
+  QUnit.config.testTimeout = 60_000;
 
   sinon.config = {
     injectIntoThis: false,
diff --git a/test/run-qunit.js b/test/run-qunit.js
index 77fe4b5b582..23bebaeac82 100644
--- a/test/run-qunit.js
+++ b/test/run-qunit.js
@@ -213,8 +213,6 @@ function logQUnit() {
 
   console.log("\nRunning: " + JSON.stringify(QUnit.urlParams) + "\n");
 
-  QUnit.config.testTimeout = 10000;
-
   let durations = {};
 
   let inTest = false;