Timo Tijhof d8a532c87e tests: Remove QUnit.newMwEnvironment from ve.test.utils.mwEnvironment ... Two problems: * At least one caller already calls QUnit.newMwEnvironment(), which means it runs twice which is unsupported and breaks If4141df10eae55 in core. * It assumes the return will contain 'setup' and 'teardown', which is internal and also changes with If4141df10eae55 in core. Using 'setup' and 'teardown' for this within VE-MW is fine. First attempt is to simply remove it. Uses that already called QUnit.newMwEnvironment are effectively unchanged. Uses that didn't and only pass ve.test.utils.mwEnvironment to QUnit.module directly will now run without core's QUnit.newMwEnvironment() setup/teardown. If that breaks anything, we can add it back to those tests that actually need it. Change-Id: I9ef0368ba58daf1c7dc92d083ae79c108cc27638		2017-07-20 00:15:51 +00:00
..
browser	Update tests to Selenium 3	2017-02-28 14:39:00 +01:00
ce	Ensure MWInlineImages get the ve-ce-leafNode class	2017-06-26 12:43:23 +00:00
dm	build: Upgrade grunt-eslint from 19.0.0 to 20.0.0	2017-07-18 12:55:33 +01:00
init/targets	Remove mobile browsers from the blacklist	2017-05-22 14:58:54 +02:00
ui	Update VE core submodule to master (fbeb0db2c)	2017-05-10 10:02:54 -05:00
mw-preload.js
ve.test.utils.js	tests: Remove QUnit.newMwEnvironment from ve.test.utils.mwEnvironment	2017-07-20 00:15:51 +00:00