Random Dusk failures, caching issue?

I did have that issue with wrong database usage, but I do not recall how I've solved it. I'm leaving this post as a reminder to myself to check that if I can remember.

Thanks, had to smile about your post. Maybe a little more information: I am running the application in a local Homestead Vagrant box. I am not using

php artisan serve

as from my understanding it is not necessary (correct me if I am wrong). It was initially a Laravel 4.x application which I upgraded to Laravel 6, means the configuration files in the config directory look a little different, but I assume they did all changes in a downward compatible way. The application itself is running without problems. The database connection looks like this:

        'dusk' => [
            'driver' => 'sqlite',
            'database' => env('DB_DATABASE', database_path('dusk.sqlite')),
            'prefix' => '',
        ],

In the .env.dusk.local I am referring to it via

DB_CONNECTION=dusk

There is nothing wrong with laughing ;)

You can add listeners in your PHPUnit.

    <listeners>
        <listener class="Tests\BackupRestoreEnvironmentListener" file="./BackupRestoreEnvironmentListener.php"></listener>
    </listeners>

<?php

namespace Tests;

use PHPUnit\Framework\TestListenerDefaultImplementation;
use PHPUnit\Framework\TestSuite;

class BackupRestoreEnvironmentListener implements \PHPUnit\Framework\TestListener
{
    /**
     * A test suite started.
     */
    public function startTestSuite(TestSuite $suite): void
    {
	// delete screenshots
	// copy env files
    }

    /**
     * A test suite ended.
     */
    public function endTestSuite(TestSuite $suite): void
    {
	// restore env files
    }
}

Hm I am not exactly sure how this TestListener helps me with the above problem?

Without trying you will never know.

Alright, I will. But where can I find the phpunit.xml that is used by Dusk? I understood that it somehow uses an internal one.

I think it should be the same phpunit.xml file. At least it was the same file when I've used it last time.

Nope, when I add this to phpunit.xml, it doesn't seem to be executed.

It worked for me. Who knows what have changed since then. Have you tried it on a clean install?

I'm having the same problem. Sometimes if fails, sometimes it doesn't. When it fails, it's because it tries to connect to the wrong database. Meaning: all other environment variables in my .env.dusk.local are correct, for example APP_URL, APP_DOMAIN, etc., but DB_DATABASE is wrong, it's still using the one from .env. It's like this is the only environment variable that is "cached". I tried running PHP artisan config:clear, config:cache... nothing works. Then, all of a sudden, it starts working again.