Laravel 8: phpunit giving error on test

Put it in the DatabaseSeeder.php

use Illuminate\Database\Seeder;

then run 

composer dumpautoload

Looks like Laravel 8 has the seeder classes namespaced now.

After doing that I'm getting the following error:

Target class [Database\Seeders\Faker\Generator] does not exist.

In Laravel 7 and below, seed classes didn't have namespaces, in Laravel 8 you should add them.

Laravel 8 - https://github.com/laravel/laravel/blob/master/database/seeders/DatabaseSeeder.php

Laravel 7 - https://github.com/laravel/laravel/blob/7.x/database/seeds/DatabaseSeeder.php

Thanks, I've adjusted it, but now a different problem occurs.

When running the tests, the migrations are not executed.

Is this because I used the new schema dump feature of Laravel 8 and I don't have any migrations left?

Does it not run the generated schema when doing tests?

This is the abstract testcase class that all tests are extended from

abstract class TestCase extends BaseTestCase
{
    use CreatesApplication;
    use RefreshDatabase;

    protected function setUp() : void
    {
        parent::setUp();
        Artisan::call('migrate:fresh --seed');
    }

    protected function login($user = null)
    {
        $user = $user ?: factory('App\User')->create();

        $this->actingAs($user);

        return $this;
    }
}

https://laravel.com/docs/8.x/database-testing#resetting-the-database-after-each-test

If RefreshDatabase is in used, the database will be cleared after finished executing every test(method).

It's not making any difference...

The SQL file from the schema dump doesn't seem to execute with an inmemory sqlite database

Yes, just run into this. This issue is indeed related to generated dump file and sqlite in memory db for testing. I was able to fix the issue by creating a test database and specifying it in phpunit.xml:

    <server name="DB_CONNECTION" value="mysql"/>
    <server name="DB_DATABASE" value="test_db"/>

I wonder if people just reply here to gain points or pimp their profile.

If you don't know the solution, why reply at all?

In the meantime, I found the solution and it's explained here: https://laravel.com/docs/8.x/migrations#squashing-migrations

If you have a SQLite database for your test environment, it's not going to take into account the Schema dump. So you either change your test database to mysql or put your squashed migrations back to their original state.

As I said earlier: I have run into this issue and found this thread. Then I figured out the problem and found the solution. So I have posted a solution, so it might help others. Sorry, if my answer was not obvious to understand.