wiki.techinc.nl/tests/parser
Tim Starling d459add63d Introduce wfDeprecatedMsg()
Deprecating something means to say something nasty about it, or to draw
its character into question. For example, "this function is lazy and good
for nothing". Deprecatory remarks by a developer are generally taken as a
warning that violence will soon be done against the function in question.
Other developers are thus warned to avoid associating with the deprecated
function.

However, since wfDeprecated() was introduced, it has become obvious that
the targets of deprecation are not limited to functions. Developers can
deprecate literally anything: a parameter, a return value, a file
format, Mondays, the concept of being, etc. wfDeprecated() requires
every deprecatory statement to begin with "use of", leading to some
awkward sentences. For example, one might say: "Use of your mouth to
cough without it being covered by your arm is deprecated since 2020."

So, introduce wfDeprecatedMsg(), which allows deprecation messages to be
specified in plain text, with the caller description being optionally
appended. Migrate incorrect or gramatically awkward uses of wfDeprecated()
to wfDeprecatedMsg().

Change-Id: Ib3dd2fe37677d98425d0f3692db5c9e988943ae8
2020-06-22 14:34:39 +10:00
..
preprocess Use singular they to refer to IP address 2018-12-13 17:41:36 +01:00
DbTestPreviewer.php Coding style: Auto-fix MediaWiki.Usage.IsNull.IsNull 2020-01-10 14:17:13 -08:00
DbTestRecorder.php Add public as visibility in tests folder 2019-10-10 21:55:37 +02:00
DjVuSupport.php PHP: Use short ternary operator (?:) where possible 2018-06-11 11:26:35 +02:00
editTests.php Use class keyword for classname resolution 2020-03-27 09:33:01 +01:00
extraParserTests.txt Update extraParserTests.txt to parserTests v2 (tidy by default) 2020-04-01 13:15:32 -04:00
fuzzTest.php Use class keyword for classname resolution 2020-03-27 09:33:01 +01:00
MultiTestRecorder.php Replace all call_user_func(_array) in all tests 2020-06-06 18:41:20 +02:00
ParserTestMockParser.php Improve test coverage for ApiStashEdit 2018-08-21 15:32:29 -07:00
ParserTestParserHook.php tests: Don't expect the Parser to be passed by ref 2019-11-18 17:43:35 +01:00
ParserTestPrinter.php Add parserTests file line number to failing tests output 2020-01-29 00:17:36 +00:00
ParserTestResult.php
ParserTestResultNormalizer.php Remove references to Html5Depurate 2019-03-13 16:33:37 -05:00
ParserTestRunner.php Remove unneeded creation of revision objects 2020-06-10 09:09:55 +00:00
parserTests.php Use class keyword for classname resolution 2020-03-27 09:33:01 +01:00
parserTests.txt Sync up with Parsoid parserTests.txt 2020-05-29 11:10:37 -04:00
PhpunitTestRecorder.php build: Updating mediawiki/mediawiki-codesniffer to 16.0.0 2018-02-17 13:29:13 +01:00
README tests: Replace implicit Bugzilla bug numbers with Phab ones 2017-02-21 02:14:34 +00:00
TestFileEditor.php Parser: remove leftover "transparent hook" code 2020-01-28 20:10:20 -05:00
TestFileReader.php Introduce wfDeprecatedMsg() 2020-06-22 14:34:39 +10:00
TestRecorder.php Add missing @param and @return to documentation 2019-11-16 13:45:55 +01:00

Parser tests can be run either via PHPUnit or by using the standalone
parserTests.php in this directory. The standalone version provides more
options.

To run parser tests via PHPUnit:

 $ cd tests/phpunit
 ./phpunit.php --testsuite parsertests

You can optionally filter by title using --filter, e.g.

 ./phpunit.php --testsuite parsertests --filter="T6400"