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"
>
    <testsuites>
        <testsuite name="Unit">
            <directory>tests/Unit</directory>
        </testsuite>
        <testsuite name="Feature">
            <directory>tests/Feature</directory>
        </testsuite>
    </testsuites>
    <source>
        <include>
            <directory>app</directory>
        </include>
    </source>
    <php>
        <env name="APP_ENV" value="testing"/>
        <env name="APP_MAINTENANCE_DRIVER" value="file"/>
        <env name="BCRYPT_ROUNDS" value="4"/>
        <env name="BROADCAST_CONNECTION" value="null"/>
        <env name="CACHE_STORE" value="array"/>
        <env name="DB_DATABASE" value="testing"/>
        <env name="DB_URL" value=""/>
        <env name="MAIL_MAILER" value="array"/>
        <env name="QUEUE_CONNECTION" value="sync"/>
        <env name="SCOUT_DRIVER" value="collection"/>
        <env name="SESSION_DRIVER" value="array"/>
        <env name="PULSE_ENABLED" value="false"/>
        <env name="TELESCOPE_ENABLED" value="false"/>
        <env name="NIGHTWATCH_ENABLED" value="false"/>
        <!--
            Keep the demo-mode tests hermetic. A developer previewing the public
            demo locally has DEMO_MODE=true in their .env; without this pin that
            ambient value boots every test with the destructive-action guard on
            and the suite fails locally while CI (booting from .env.example)
            stays green. Pinning also keeps DEMO_MODE defined at the process
            level, so the immutable env repository never "adopts" the .env value
            as its own and re-writes it on later application refreshes. `force`
            makes the pin win even over an exported/process-level DEMO_MODE, so
            the suite is deterministic no matter how the flag arrives.
        -->
        <env name="DEMO_MODE" value="false" force="true"/>
        <!--
            Keep the SSO/LDAP feature tests hermetic. A developer running the
            `sso` dev-container profile has real LDAP_*/SSO_* values in their
            .env; without these pins that ambient config leaks into the test
            environment (config('sso.ldap.enabled') reads true, the GUID maps to
            `entryuuid`, etc.) and the suite fails locally while CI (booting from
            .env.example) stays green. Toggle/credential/provider keys pin to
            empty so no provider is "configured" by default; the attribute keys
            pin to their config defaults so directory entries created without
            them (relying on the emulator's auto-assigned objectguid) still bind.
        -->
        <env name="AUTH_SSO_ONLY" value="false"/>
        <env name="LDAP_CONNECTION" value="default"/>
        <env name="LDAP_HOST" value=""/>
        <env name="LDAP_BASE_DN" value=""/>
        <env name="LDAP_USERNAME" value=""/>
        <env name="LDAP_PASSWORD" value=""/>
        <env name="LDAP_ATTR_USERNAME" value="mail"/>
        <env name="LDAP_ATTR_MAIL" value="mail"/>
        <env name="LDAP_ATTR_NAME" value="cn"/>
        <env name="LDAP_ATTR_GUID" value="objectguid"/>
        <env name="SSO_OIDC_CLIENT_ID" value=""/>
        <env name="SSO_OIDC_ISSUER" value=""/>
        <env name="SSO_DEFAULT_TEAM_ID" value=""/>
        <env name="SCIM_TOKEN" value=""/>
        <env name="GIPHY_API_KEY" value=""/>
        <!-- Avatars resolve through the image proxy, which fetches the remote
             image server-side. Left enabled, every rendered avatar would make the
             suite reach gravatar.com — and in the browser tests that fetch blocks
             the single-process app server the page is talking to. Tests that
             exercise Gravatar itself opt back in with config()->set(). -->
        <env name="GRAVATAR_ENABLED" value="false"/>
    </php>
</phpunit>