thiemowmde 5aa6cb0c7b Replace extremely slow parser test with fast unit tests ... This parser test is a bit obscure, in my opinion. We added it in I8c4de96 to make sure we don't get thousand separators in most places. We continued reworking the code since then. By now it's effectively impossible to "accidentally" get thousand separators. The problematic methods from the Language class are not even accessible any more from this code. To make the tests more robust we now use createNoOpMock (done via the previous patch) where it matters, specifically for all Language and Parser mocks. This proves the problematic Language methods are never called. Bug: T253743 Bug: T238187 Change-Id: I9bfe1f4decfaf699996da63e19473c2c0d581d9d		2023-07-28 00:32:38 +00:00
..
bookReferencing.txt	Add parser & unit test cases for different $wgFragmentMode's	2022-01-03 14:14:47 +01:00
citeParserTests-knownFailures.json	Enable integrated testing with Parsoid	2023-03-07 00:22:55 -06:00
citeParserTests.txt	Sync up Cite repo with Parsoid	2023-05-12 09:59:44 -04:00
citeSmokeTests.txt	parser tests: move test which requires {{#ifeq}} into its own file	2022-05-27 11:38:02 -04:00
fragementModes.txt	parser tests: Make !! config values JSON-compatible	2022-05-11 21:05:55 -04:00
parserFunctionTests.txt	Remove problematic spaces from a parser test case + Rename a test file	2023-03-01 08:54:11 -06:00
responsiveReferences.txt	Add parser & unit test cases for different $wgFragmentMode's	2022-01-03 14:14:47 +01:00