Laravel Dusk should use phpunit.xml env variables by default

[Sairahcaz]

Following scenario:

You start working on your tests, you set up the phpunit.xml file and you set the env variables for instance like so:

<php>
    <env name="APP_ENV" value="testing"/>
    <env name="BCRYPT_ROUNDS" value="4"/>
    <env name="CACHE_DRIVER" value="array"/>
    <env name="DB_CONNECTION" value="mysql"/>
    <env name="DB_DATABASE" value="my_app_testing"/>
    <env name="MAIL_MAILER" value="array"/>
    <env name="QUEUE_CONNECTION" value="sync"/>
    <env name="SESSION_DRIVER" value="array"/>
    <env name="TELESCOPE_ENABLED" value="false"/>
  </php>

(Note that DB_DATABASE is set to my_app_testing...)

Now your tests are looking good and you want to go on with some browser tests using dusk.

You use the DatabaseTruncation trait for your browser test.

uses(
    DatabaseTruncation::class
)->in('Browser');

Your first browser test is looking fine, you run php artisan dusk and now oops your completely database was truncated.
Thats cause dusk uses the .env file by default. I would say it makes a lot more sense if dusk would use the phpunit.xml environment variables. Maybe if there is a .env.dusk.local file then it should use this one instead. But please don't use the normal .env file by default...