a8f20adc42
This now aligns with Parsoid commit 4d7cacfedc69ecac6e65f8d62f54583b900a54d2 Change-Id: I14d74032d09da1c6abf478e058e67c4040c1fcd0 |
||
|---|---|---|
| .. | ||
| 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"