Not really an issue just an possible speed upgrade about laravel-fast-refresh-database

[Tray2]

That is an option, but I feel that you shouldn't run any seeders that you don't need.

[sinnbeck]

If you set the seeder on your TestCase class it will automatically be seeded with the migrations (once). Just be aware that changes to this seeder will require that you manually delete or alter the checksum file

public $seeder = SomeSeeder::class

[krzysztofrewak]

I was thinking about the same issue. Maybe the better approach would be to run all migrations with seeders once and then created a dump of entire "base" database. With this approach migrate:fresh would not be ran anymore as we would need to recreate a dump file.

[Tray2]

I tried that, but it didn't make any difference with seeding of around 3K records in one seeder.

[Tray2]

I think this one can be closed without further a do