Files
dyncoll-dev/backend/phpunit.xml
Giuseppe Naponiello cc4e174880 auth tests
2026-06-22 14:31:44 +02:00

43 lines
2.0 KiB
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>
<!-- IMPORTANTE: la sicurezza del DB NON dipende da questo file. Nel container
le env (DB_HOST=db, DB_DATABASE=dyncoll, APP_ENV=local, ...) sono REALI e
finiscono in $_SERVER, che l'env() di Laravel legge PRIMA: il force qui sotto
NON le sovrascrive. L'override autoritativo arriva dalle -e di `make test`
(DB_HOST=db-test, DB_DATABASE=dyncoll_test). Questi force servono solo come
rete per i driver non-DB se qualcuno lancia `php artisan test` a mano; il
redirect verso db-test resta garantito dal guard in Tests\TestCase. -->
<env name="APP_ENV" value="testing" force="true"/>
<env name="APP_MAINTENANCE_DRIVER" value="file" force="true"/>
<env name="BCRYPT_ROUNDS" value="4" force="true"/>
<env name="BROADCAST_CONNECTION" value="null" force="true"/>
<env name="CACHE_STORE" value="array" force="true"/>
<env name="DB_CONNECTION" value="mysql" force="true"/>
<env name="DB_DATABASE" value="dyncoll_test" force="true"/>
<env name="MAIL_MAILER" value="array" force="true"/>
<env name="QUEUE_CONNECTION" value="sync" force="true"/>
<env name="SESSION_DRIVER" value="array" force="true"/>
<env name="PULSE_ENABLED" value="false" force="true"/>
<env name="TELESCOPE_ENABLED" value="false" force="true"/>
<env name="NIGHTWATCH_ENABLED" value="false" force="true"/>
</php>
</phpunit>