SeedDatabase trait along with SeedDatabaseState class gives your Laravel project the ability to seed the testing database once before running the full suite tests, which improves the speed of the tests than seeding the testing database before each test.
Also, it has the option to run custom seeders instead of the seeders that are called in the run() method of the DatabaseSeeder class you can achieve that as follows
...in the Testcase.php
public function setUp()
{
parent::setUp();
SeedDatabaseState::$seeders = [RolesSeeder::class, PermissionSeeder::class];
$this->seedDatabase();
}
Instructions:
- Place the SeedDatabase.php and the SeedDatabaseState.php into the tests folder in your Laravel project and update the TestCase.php to use the SeedDatabase trait and make the changes in the setup() method to call $this->seedDatabase(); after calling the parent::setup()
I found a problem with this trait.
When this trait is run on a class that is not using RefreshDatabase or DatabaseTransactions, it is marked as already seeded and will not be seeded again.
In code, I think it is correct to modify seedDatabase as follows
Conversely, syncTransactionTraits are simpler.
This worked in my environment.