Laravel 12 Docs MCP Server

# Spatie - Advanced Usage/Testing Source: https://spatie.be/docs/laravel-permission/v6/advanced-usage/testing Docs Laravel-permission Advanced-usage Testing Testing ======= ### On this page 1. Clear Cache During Tests 2. Clear Cache When Using Seeders 3. Bypassing Cache When Testing 4. Testing Using Factories ##Clear Cache During Tests -------------------------- In your application's tests, if you are not seeding roles and permissions as part of your test `setUp()` then you may run into a chicken/egg situation where roles and permissions aren't registered with the gate (because your tests create them after that gate registration is done). Working around this is simple: In your tests simply add a `setUp()` instruction to re-register the permissions, like this: ```php protected function setUp(): void { // first include all the normal setUp operations parent::setUp(); // now de-register all the roles and permissions by clearing the permission cache $this->app->make(\Spatie\Permission\PermissionRegistrar::class)->forgetCachedPermissions(); } ``` ##Clear Cache When Using Seeders -------------------------------- If you are using Laravel's `LazilyRefreshDatabase` trait, you most likely want to avoid seeding permissions before every test, because that would negate the use of the `LazilyRefreshDatabase` trait. To overcome this, you should wrap your seeder in an event listener for the `DatabaseRefreshed` event: ```php Event::listen(DatabaseRefreshed::class, function () { $this->artisan('db:seed', ['--class' => RoleAndPermissionSeeder::class]); $this->app->make(\Spatie\Permission\PermissionRegistrar::class)->forgetCachedPermissions(); }); ``` Note that `PermissionRegistrar::forgetCachedPermissions()` is called AFTER seeding. This is to prevent a caching issue that can occur when the database is set up after permissions have already been registered and cached. ##Bypassing Cache When Testing ------------------------------ The caching infrastructure for this package is "always on", but when running your test suite you may wish to reduce its impact. Two things you might wish to explore include: * Change the cache driver to `array`. **Very often you will have already done this in your `phpunit.xml` configuration.** * Shorten cache lifetime to 1 second, by setting the config (not necessary if cache driver is set to `array`) in your test suite TestCase: `'permission.cache.expiration_time' = \DateInterval::createFromDateString('1 seconds')` ##Testing Using Factories ------------------------- Many applications do not require using factories to create fake roles/permissions for testing, because they use a Seeder to create specific roles and permissions that the application uses; thus tests are performed using the declared roles and permissions. However, if your application allows users to define their own roles and permissions you may wish to use Model Factories to generate roles and permissions as part of your test suite. When using Laravel's class-based Model Factory features you will need to `extend` this package's `Role` and/or `Permission` model into your app's namespace, add the `HasFactory` trait to it, and define a model factory for it. Then you can use that factory in your seeders like any other factory related to your application's models. Performance Tips Database Seeding Help us improve this page