phpunit.xml

<?xml version="1.0" encoding="UTF-8"?>
<phpunit xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:noNamespaceSchemaLocation="vendor/phpunit/phpunit/phpunit.xsd"
         bootstrap="vendor/autoload.php"
         colors="true"
         displayDetailsOnTestsThatTriggerDeprecations="true"
         displayDetailsOnTestsThatTriggerWarnings="true"
         displayDetailsOnTestsThatTriggerNotices="true"
         displayDetailsOnTestsThatTriggerErrors="true"
>
    <testsuites>
        <testsuite name="Install">
            <directory suffix="Test.php">./tests/Install</directory>
        </testsuite>
        <testsuite name="Backend">
            <directory suffix="Test.php">./tests/Backend</directory>
        </testsuite>
        <testsuite name="Frontend">
            <directory suffix="Test.php">./tests/Frontend</directory>
        </testsuite>
        <testsuite name="Api">
            <directory suffix="Test.php">./tests/Api</directory>
        </testsuite>
        <testsuite name="Browser">
            <directory suffix="Test.php">./tests/Browser</directory>
        </testsuite>
    </testsuites>
    <!--
        restrictNotices/restrictWarnings limit surfaced notices/warnings to those
        triggered by our own code (app, lib). This filters benign, intentionally
        @-suppressed framework internals we don't own and can't fix - e.g. the
        Symfony FilesystemTagAwareAdapter symlink race ("File exists") that its own
        is_link() fallback already handles - while still surfacing any notice or
        warning originating in Maho code.
    -->
    <source restrictNotices="true" restrictWarnings="true">
        <include>
            <directory>app</directory>
            <directory>lib</directory>
        </include>
    </source>
</phpunit>