53fe91ded5
The Preprocessor_DOM implementation doesn't interact well with PHP memory profiling, and has some limitations not present in the Preprocessor_Hash implementation (see T216664). There is no reason to keep around two versions of the preprocessor: it just complicates on-going wikitext feature development. Hard deprecate use of Preprocessor_DOM, so we can remove the redundant code in a future release. Bug: T204945 Depends-On: Id38c9360e4d02b570996dbf7a660f964f02f1a2c Change-Id: Ica5d1ad5b1e677542962fc36d582a793f941155e |
||
|---|---|---|
| .. | ||
| preprocess | ||
| DbTestPreviewer.php | ||
| DbTestRecorder.php | ||
| DjVuSupport.php | ||
| editTests.php | ||
| extraParserTests.txt | ||
| fuzzTest.php | ||
| MultiTestRecorder.php | ||
| ParserTestMockParser.php | ||
| ParserTestParserHook.php | ||
| ParserTestPrinter.php | ||
| ParserTestResult.php | ||
| ParserTestResultNormalizer.php | ||
| ParserTestRunner.php | ||
| parserTests.php | ||
| parserTests.txt | ||
| PhpunitTestRecorder.php | ||
| README | ||
| TestFileEditor.php | ||
| TestFileReader.php | ||
| TestRecorder.php | ||
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"