From 1ce3d7ab7e61d1bde98e4f1ce9028e8f77fc918a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Bartosz=20Dziewo=C5=84ski?= Date: Fri, 14 Jan 2022 01:06:29 +0100 Subject: [PATCH] Work around Karma test runner timeouts caused by large tests Change-Id: I8c7d32dac073e1f0510e57f26ba81ff22f005f0a --- tests/qunit/modifier.test.js | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/tests/qunit/modifier.test.js b/tests/qunit/modifier.test.js index ef8b4e773..b72b97254 100644 --- a/tests/qunit/modifier.test.js +++ b/tests/qunit/modifier.test.js @@ -5,11 +5,12 @@ var QUnit.module( 'mw.dt.modifier', testUtils.newEnvironment() ); -QUnit.test( '#addListItem/#removeAddedListItem', function ( assert ) { - var cases = require( '../cases/modified.json' ), - fixture = document.getElementById( 'qunit-fixture' ); +require( '../cases/modified.json' ).forEach( function ( caseItem, i ) { + // This should be one test with many cases, rather than multiple tests, but the cases are large + // enough that processing all of them at once causes timeouts in Karma test runner. + QUnit.test( '#addListItem/#removeAddedListItem case ' + i, function ( assert ) { + var fixture = document.getElementById( 'qunit-fixture' ); - cases.forEach( function ( caseItem ) { var dom = mw.template.get( 'test.DiscussionTools', caseItem.dom ).render(), expected = mw.template.get( 'test.DiscussionTools', caseItem.expected ).render(), config = require( caseItem.config ),