add drupal to validation tests
This commit is contained in:
Родитель
b48b1584c8
Коммит
e1231e688e
|
@ -22,3 +22,6 @@
|
|||
[submodule "validation/frameworks/cakephp"]
|
||||
path = validation/frameworks/cakephp
|
||||
url = https://github.com/cakephp/cakephp
|
||||
[submodule "validation/frameworks/drupal"]
|
||||
path = validation/frameworks/drupal
|
||||
url = https://github.com/drupal/drupal
|
||||
|
|
99
phpunit.xml
99
phpunit.xml
|
@ -1,49 +1,58 @@
|
|||
<phpunit bootstrap="src/bootstrap.php">
|
||||
<testsuites>
|
||||
<testsuite name="invariants">
|
||||
<testsuites>
|
||||
<testsuite name="invariants">
|
||||
<!--
|
||||
Tests that token/tree production is "structurally" sound.
|
||||
* INPUT: All PHP files in `tests/cases/**/`
|
||||
* OUTPUT: TODO - output failing tests
|
||||
-->
|
||||
<file>tests/LexerInvariantsTest.php</file>
|
||||
<file>tests/ParserInvariantsTest.php</file>
|
||||
</testsuite>
|
||||
|
||||
<testsuite name="grammar">
|
||||
<!--
|
||||
Tests that we are properly implementing the grammar.
|
||||
* INPUT: All files in `tests/cases/**/`
|
||||
* OUTPUT: TODO - output failing tests
|
||||
-->
|
||||
<file>tests/LexicalGrammarTest.php</file>
|
||||
<file>tests/ParserGrammarTest.php</file>
|
||||
</testsuite>
|
||||
|
||||
<testsuite name="validation">
|
||||
<!--
|
||||
Validates against real-world scenarios.
|
||||
* INPUT: All files in `validation/frameworks/<framework-name>/*`
|
||||
* OUTPUT: Failing tests are output to `tests/output/<framework-name>`
|
||||
-->
|
||||
<file>tests/ParserFrameworkValidationTests.php</file>
|
||||
</testsuite>
|
||||
|
||||
<testsuite name="api">
|
||||
<file>tests/NodeApiTest.php</file>
|
||||
</testsuite>
|
||||
|
||||
<testsuite name="performance">
|
||||
<!-- TODO: Validates that there are no performance regressions. -->
|
||||
</testsuite>
|
||||
</testsuites>
|
||||
|
||||
<filter>
|
||||
<!-- Code coverage whitelist. -->
|
||||
<whitelist processUncoveredFilesFromWhitelist="true">
|
||||
<directory suffix=".php">/src/Node</directory>
|
||||
<file>/src/Parser.php</file>
|
||||
<file>/src/PhpTokenizer.php</file>
|
||||
</whitelist>
|
||||
</filter>
|
||||
|
||||
<php>
|
||||
<!--
|
||||
Tests that token/tree production is "structurally" sound.
|
||||
* INPUT: All PHP files in `tests/cases/**/`
|
||||
* OUTPUT: TODO - output failing tests
|
||||
TODO: see if we can remove this in the future. It may be indicative of not passing things
|
||||
by reference properly in the API.
|
||||
https://github.com/Microsoft/tolerant-php-parser/issues/23
|
||||
-->
|
||||
<file>tests/LexerInvariantsTest.php</file>
|
||||
<file>tests/ParserInvariantsTest.php</file>
|
||||
</testsuite>
|
||||
|
||||
<testsuite name="grammar">
|
||||
<!--
|
||||
Tests that we are properly implementing the grammar.
|
||||
* INPUT: All files in `tests/cases/**/`
|
||||
* OUTPUT: TODO - output failing tests
|
||||
-->
|
||||
<file>tests/LexicalGrammarTest.php</file>
|
||||
<file>tests/ParserGrammarTest.php</file>
|
||||
</testsuite>
|
||||
|
||||
<testsuite name="validation">
|
||||
<!--
|
||||
Validates against real-world scenarios.
|
||||
* INPUT: All files in `validation/frameworks/<framework-name>/*`
|
||||
* OUTPUT: Failing tests are output to `tests/output/<framework-name>`
|
||||
-->
|
||||
<file>tests/ParserFrameworkValidationTests.php</file>
|
||||
</testsuite>
|
||||
|
||||
<testsuite name="api">
|
||||
<file>tests/NodeApiTest.php</file>
|
||||
</testsuite>
|
||||
|
||||
<testsuite name="performance">
|
||||
<!-- TODO: Validates that there are no performance regressions. -->
|
||||
</testsuite>
|
||||
</testsuites>
|
||||
|
||||
<filter>
|
||||
<!-- Code coverage whitelist. -->
|
||||
<whitelist processUncoveredFilesFromWhitelist="true">
|
||||
<directory suffix=".php">/src/Node</directory>
|
||||
<file>/src/Parser.php</file>
|
||||
<file>/src/PhpTokenizer.php</file>
|
||||
</whitelist>
|
||||
</filter>
|
||||
<ini name="memory_limit" value="256M"/>
|
||||
</php>
|
||||
</phpunit>
|
|
@ -0,0 +1 @@
|
|||
Subproject commit bf93f84100bbc1949c75ae22bd8d7ce0392f3082
|
Загрузка…
Ссылка в новой задаче