.env.testing not being loaded at all

[VictorMLima98]

Laravel Version

12.10.1

PHP Version

8.4.1

Database Driver & Version

MySQL 9.2.0

Description

.env.testing is not loaded when running php artisan test on Laravel 12

I'm running a Laravel 12 project, and I’m having trouble getting the .env.testing file to load when running tests via php artisan test.

According to the docs, .env.testing should be loaded automatically when running tests using Artisan. However, this does not seem to be happening in my setup.

---

Expected Behavior

Laravel should load .env.testing and use the environment variables defined in it.

Actual Behavior

Laravel loads the default .env file.
The environment remains local, and the DB_DATABASE is not coming from .env.testing.
This means tests are running against the development database.

Additional Info

1. .env.testing is correctly placed in the project root.
2. All caches were cleared: config:clear, cache:clear, view:clear, route:clear.
3. app()->environmentFile() still returns .env.
4. I've created an artisan command to debug it. Running php artisan my-command --env=testing loads .env.testing correctly, but running artisan test does not

Steps To Reproduce

1. Create a .env.testing file in the project root with:

APP_ENV=testing
DB_DATABASE=testing

2. Create a test like this

it('checks the environment', function () {
    dump([
        'env' => app()->environment(),
        'db' => config('database.connections.mysql.database'),
        '__env_file' => app()->environmentFile(),
    ]);
});

3. Run the test

php artisan test --filter="checks the environment"

You can also try to migrate the testing database with php artisan migrate --env=testing and see if your development database got refreshed, which is my case.

[VictorMLima98]

Just a note: I've just tested an app on Laravel 11 using the same environment described above and it worked fine.

[yoeriboven]

Do you have APP_ENV set to testing in your phpunit.xml?

https://github.com/laravel/laravel/blob/f6e4638ee6ca1cd40aa7c56311d89ea3d91a24f8/phpunit.xml#L21

[lloricode]

for work arround, just put this in your phpunit.xml

    <php>
        <env name="APP_ENV" value="testing"/>
    </php>

[yoeriboven]

That is not a workaround. That’s where you set the environment so it knows which .env to use.

[utsavsomaiya]

[faissaloux]

@utsavsomaiya which version of the framework you using?

[gsinti]

@VictorMLima98: I was having this issue just now and came here to look for others reporting it.

One thing that differed with my environment was that I had just upgraded from 12.11 to 12.12.

I ran composer install and it fixed the issue for me.

[VictorMLima98]

@VictorMLima98: I was having this issue just now and came here to look for others reporting it.

One thing that differed with my environment was that I had just upgraded from 12.11 to 12.12.

I ran composer install and it fixed the issue for me.

Sorry for the late reply, guys. I've managed to get around this issue by downgrading my project a few minor versions. I'm using 12.8.1 and the issue no longer takes place.

I bet that's a problem that has been introduced on 12.10 or something like that.

I tried to debug the framework files for a few hours without success, so I just downgraded and boom, problem's gone.

[VictorMLima98]

Actually it just happened again on 12.8.1.

Tried upgrading to 12.12 and it persists.

[gsinti]

@VictorMLima98: I assume after switching versions, you're running a composer install between each attempt to run tests?

[VictorMLima98]

Sure! I even deleted my whole vendor folder and re-installed it, but no solution yet :/

[itpilotdk]

Confirmed. Having same problem in v12.12.0. Also in Sail
(when using laravel dusk, the chromium http calls do not use testing env, but artisan commands does).

Testing e.g. user creation creates a user (with dusk) in the regular database, and not the testing database).
Running pest tests, creates it in the testing database fint (but i had to change the phpunit.xml).

[crynobone]

Hey there, thanks for reporting this issue.

We'll need more info and/or code to debug this further. Can you please create a repository with the command below, commit the code that reproduces the issue as one separate commit on the main/master branch and share the repository here?

Please make sure that you have the latest version of the Laravel installer in order to run this command. Please also make sure you have both Git & the GitHub CLI tool properly set up.

laravel new bug-report --github="--public"

Do not amend and create a separate commit with your custom changes. After you've posted the repository, we'll try to reproduce the issue.

Thanks!

[crynobone]

Hey there,

We're closing this issue because it's inactive, already solved, old, or not relevant anymore. Feel free to open up a new issue if you're still experiencing this problem.