cea8aee05e
Maintenance::finalSetup should have access to a SettingsBuilder so it can manipulates config settings without resorting to global variables. MaintenanceRunner will always provide a SettingsBuilder when calling this method, so implementations should be able to rely on always getting one. The $settings parameter was introduced as optional in order to maintain backwards compatibility with implementations that did not declare the parameter. But these should all have been fixed since. Depends-On: I8a3699b13bfb4dc15f3bed562731ed9d525651cc Change-Id: I334a103e02fd905faafc43c7c5b95996bc91fd18 |
||
|---|---|---|
| .. | ||
| AnsiTermColorer.php | ||
| badCharacters.txt | ||
| comments.txt | ||
| DbTestPreviewer.php | ||
| DbTestRecorder.php | ||
| definitionLists.txt | ||
| DjVuSupport.php | ||
| DummyTermColorer.php | ||
| editTests.php | ||
| extLinks.txt | ||
| fuzzTest.php | ||
| indentPre.txt | ||
| indicators.txt | ||
| interlanguageLinks.txt | ||
| interwikiLinks.txt | ||
| legacyMedia.txt | ||
| magicLinks.txt | ||
| magicWords.txt | ||
| media.txt | ||
| MultiTestRecorder.php | ||
| ParserTestMockParser.php | ||
| ParserTestParserHook.php | ||
| ParserTestPrinter.php | ||
| ParserTestResult.php | ||
| ParserTestResultNormalizer.php | ||
| ParserTestRunner.php | ||
| parserTests.php | ||
| parserTests.txt | ||
| pfeqParserTests.txt | ||
| PhpunitTestRecorder.php | ||
| preprocessor.txt | ||
| preTags.txt | ||
| pst.txt | ||
| pWrapping.txt | ||
| quotes.txt | ||
| README | ||
| redirects.txt | ||
| tables.txt | ||
| TestFileEditor.php | ||
| TestRecorder.php | ||
| toc.txt | ||
| wtEscaping.txt | ||
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: $ composer phpunit -- --testsuite parsertests You can optionally filter by title using --filter, e.g. composer phpunit -- --testsuite parsertests --filter="T6400"