phpunit.xml

<?xml version="1.0" encoding="UTF-8"?>
<!-- Drupal 11 and 12 PHPUnit configuration. -->
<!-- For how to customize PHPUnit configuration, see web/core/tests/README.md. -->
<!-- TODO set checkForUnintentionallyCoveredCode="true" once https://www.drupal.org/node/2626832 is resolved. -->
<!-- PHPUnit expects functional tests to be run with either a privileged user
 or your current system user. See web/core/tests/README.md and
 https://www.drupal.org/node/2116263 for details.
-->
<phpunit xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         bootstrap="web/core/tests/bootstrap.php"
         colors="true"
         beStrictAboutTestsThatDoNotTestAnything="true"
         beStrictAboutOutputDuringTests="true"
         beStrictAboutChangesToGlobalState="true"
         failOnWarning="true"
         displayDetailsOnTestsThatTriggerNotices="true"
         displayDetailsOnTestsThatTriggerErrors="true"
         displayDetailsOnTestsThatTriggerWarnings="true"
         displayDetailsOnTestsThatTriggerDeprecations="true"
         cacheResult="false"
         xsi:noNamespaceSchemaLocation="https://schema.phpunit.de/10.5/phpunit.xsd"
         cacheDirectory=".phpunit.cache">
    <php>
        <!-- Set error reporting to E_ALL & ~E_DEPRECATED. -->
        <ini name="error_reporting" value="24575"/>
        <!-- Do not limit the amount of memory tests take to run. -->
        <ini name="memory_limit" value="-1"/>
        <env name="SIMPLETEST_BASE_URL" value="http://localhost:8000"/>
        <env name="SIMPLETEST_DB" value="sqlite://localhost/drupal_test_extension.sqlite"/>
        <!-- By default, browser tests will output links that use the base URL set
         in SIMPLETEST_BASE_URL. However, if your SIMPLETEST_BASE_URL is an internal
         path (such as may be the case in a virtual or Docker-based environment),
         you can set the base URL used in the browser test output links to something
         reachable from your host machine here. This will allow you to follow them
         directly and view the output. -->
        <env name="BROWSERTEST_OUTPUT_BASE_URL" value=""/>
        <!-- The environment variable SYMFONY_DEPRECATIONS_HELPER is used to configure
          the behavior of the deprecation tests.
          Drupal core's testing framework is setting this variable to its defaults.
          Projects with their own requirements need to manage this variable
          explicitly.
        -->
        <!-- To disable deprecation testing completely uncomment the next line. -->
        <!-- <env name="SYMFONY_DEPRECATIONS_HELPER" value="disabled"/> -->
        <!-- Deprecation errors can be selectively ignored by specifying a file of
          regular expression patterns for exclusion.
          Uncomment the line below to specify a custom deprecations ignore file.
          NOTE: it may be required to specify the full path to the file to run tests
          correctly.
        -->
        <!-- <env name="SYMFONY_DEPRECATIONS_HELPER" value="ignoreFile=../.deprecation-ignore.txt"/> -->
        <!-- Example for changing the driver class for mink tests MINK_DRIVER_CLASS value: 'Drupal\FunctionalJavascriptTests\DrupalSelenium2Driver' -->
        <env name="MINK_DRIVER_CLASS" value=""/>
        <!-- Example for changing the driver args to mink tests MINK_DRIVER_ARGS value: '["http://127.0.0.1:8510"]' -->
        <env name="MINK_DRIVER_ARGS" value=""/>
        <!-- #;< DEV_FUNCTIONAL_JAVASCRIPT -->
        <!-- Example for changing the driver args to webdriver tests MINK_DRIVER_ARGS_WEBDRIVER value: '["chrome", { "goog:chromeOptions": { "w3c": false } }, "http://localhost:4444/wd/hub"]' For using the Firefox browser, replace "chrome" with "firefox" -->
        <!-- The endpoint below is the default. Both WebDriver backends bind the
          per-project port resolved by 'eddy-browser-start' (WEBDRIVER_PORT), so
          the FunctionalJavascript base class replaces the port in this value at
          run time. Tests that do not extend that base class can export their own
          MINK_DRIVER_ARGS_WEBDRIVER, which takes precedence over this entry.
        -->
        <env name="MINK_DRIVER_ARGS_WEBDRIVER" value='["chrome", {"browserName": "chrome", "goog:chromeOptions": {"w3c": true, "args": ["--no-sandbox", "--disable-gpu", "--window-size=1280,1024"]}}, "http://localhost:4444"]'/>
        <!-- #;> DEV_FUNCTIONAL_JAVASCRIPT -->
    </php>
    <extensions>
        <!-- Functional tests HTML output logging. -->
        <bootstrap class="Drupal\TestTools\Extension\HtmlLogging\HtmlOutputLogger">
            <!-- The directory where the browser output will be stored. If a relative
              path is specified, it will be relative to the current working directory
              of the process running the PHPUnit CLI. In CI environments, this can be
              overridden by the value set for the "BROWSERTEST_OUTPUT_DIRECTORY"
              environment variable.
            -->
            <!-- Setting a custom value does not work. @see https://www.drupal.org/project/drupal/issues/2992069 -->
            <parameter name="outputDirectory" value="sites/simpletest/browser_output"/>
            <!-- By default browser tests print the individual links in the test run
              report. To avoid overcrowding the output in CI environments, you can
              set the "verbose" parameter or the "BROWSERTEST_OUTPUT_VERBOSE"
              environment variable to "false". In GitLabCI, the output is saved
              anyway as an artifact that can be browsed or downloaded from Gitlab.
            -->
            <parameter name="verbose" value="true"/>
        </bootstrap>
    </extensions>
    <testsuites>
        <testsuite name="unit">
            <!-- #;< EXTENSION_MODULE -->
            <directory>web/modules/custom/*/tests/src/Unit</directory>
            <!-- #;> EXTENSION_MODULE -->
            <!-- #;< EXTENSION_THEME -->
            <directory>web/themes/custom/*/tests/src/Unit</directory>
            <!-- #;> EXTENSION_THEME -->
        </testsuite>
        <testsuite name="kernel">
            <!-- #;< EXTENSION_MODULE -->
            <directory>web/modules/custom/*/tests/src/Kernel</directory>
            <!-- #;> EXTENSION_MODULE -->
            <!-- #;< EXTENSION_THEME -->
            <directory>web/themes/custom/*/tests/src/Kernel</directory>
            <!-- #;> EXTENSION_THEME -->
        </testsuite>
        <testsuite name="functional">
            <!-- #;< EXTENSION_MODULE -->
            <directory>web/modules/custom/*/tests/src/Functional</directory>
            <!-- #;> EXTENSION_MODULE -->
            <!-- #;< EXTENSION_THEME -->
            <directory>web/themes/custom/*/tests/src/Functional</directory>
            <!-- #;> EXTENSION_THEME -->
        </testsuite>

        <!-- #;< DEV_FUNCTIONAL_JAVASCRIPT -->
        <testsuite name="functional-javascript">
            <!-- #;< EXTENSION_MODULE -->
            <directory>web/modules/custom/*/tests/src/FunctionalJavascript</directory>
            <!-- #;> EXTENSION_MODULE -->
            <!-- #;< EXTENSION_THEME -->
            <directory>web/themes/custom/*/tests/src/FunctionalJavascript</directory>
            <!-- #;> EXTENSION_THEME -->
        </testsuite>
        <!-- #;> DEV_FUNCTIONAL_JAVASCRIPT -->
    </testsuites>

    <logging>
        <junit outputFile="../.logs/test_results/phpunit/phpunit.xml"/>
    </logging>

    <!-- Settings for coverage reports. -->
    <coverage includeUncoveredFiles="true"
              pathCoverage="false"
              ignoreDeprecatedCodeUnits="true"
              disableCodeCoverageIgnore="false">
        <report>
            <html outputDirectory="../.logs/coverage/phpunit/.coverage-html" lowUpperBound="50" highLowerBound="90"/>
            <cobertura outputFile="../.logs/coverage/phpunit/cobertura.xml"/>
        </report>
    </coverage>
    <source>
        <include>
            <!-- #;< EXTENSION_MODULE -->
            <directory>web/modules/custom</directory>
            <!-- A module holds its hooks in its '.module' and '.install' files. -->
            <directory suffix=".module">web/modules/custom</directory>
            <directory suffix=".install">web/modules/custom</directory>
            <!-- #;> EXTENSION_MODULE -->
            <!-- #;< EXTENSION_THEME -->
            <directory>web/themes/custom</directory>
            <!-- A theme holds its PHP in its '.theme' file. -->
            <directory suffix=".theme">web/themes/custom</directory>
            <!-- #;> EXTENSION_THEME -->
        </include>

        <exclude>
            <!-- #;< EXTENSION_MODULE -->
            <directory>web/modules/custom/*/tests</directory>
            <directory suffix=".module">web/modules/custom/*/tests</directory>
            <directory suffix=".install">web/modules/custom/*/tests</directory>
            <!-- #;> EXTENSION_MODULE -->
            <!-- #;< EXTENSION_THEME -->
            <directory>web/themes/custom/*/tests</directory>
            <directory suffix=".theme">web/themes/custom/*/tests</directory>
            <!-- #;> EXTENSION_THEME -->
            <!-- #;< DEV_RECTOR -->
            <!-- #;< EXTENSION_MODULE -->
            <file>web/modules/custom/your_extension/rector.php</file>
            <!-- #;> EXTENSION_MODULE -->
            <!-- #;< EXTENSION_THEME -->
            <file>web/themes/custom/your_extension/rector.php</file>
            <!-- #;> EXTENSION_THEME -->
            <!-- #;> DEV_RECTOR -->
            <directory>**/node_modules/**</directory>
            <!-- #;< META -->
            <file>../install.php</file>
            <!-- #;> META -->
        </exclude>
    </source>
</phpunit>