mirror of
https://github.com/AnimeThemes/animethemes-server.git
synced 2026-07-11 01:24:46 +02:00
Kyrch
83 lines
2.3 KiB
PHP
83 lines
2.3 KiB
PHP
<?php
|
|
|
|
declare(strict_types=1);
|
|
|
|
use App\Enums\Auth\SpecialPermission;
|
|
use App\Filament\Resources\BaseResource;
|
|
use App\Models\Auth\User;
|
|
use Illuminate\Foundation\Testing\RefreshDatabase;
|
|
|
|
use function Pest\Laravel\actingAs;
|
|
|
|
use Tests\TestCase;
|
|
|
|
/*
|
|
|--------------------------------------------------------------------------
|
|
| Test Case
|
|
|--------------------------------------------------------------------------
|
|
|
|
|
| The closure you provide to your test functions is always bound to a specific PHPUnit test
|
|
| case class. By default, that class is "PHPUnit\Framework\TestCase". Of course, you may
|
|
| need to change it using the "pest()" function to bind a different classes or traits.
|
|
|
|
|
*/
|
|
|
|
pest()->extend(TestCase::class)
|
|
->use(RefreshDatabase::class)
|
|
->in('Feature', 'Unit');
|
|
|
|
pest()
|
|
->in('Feature/Filament/Resources')
|
|
->beforeEach(function (): void {
|
|
$user = User::factory()
|
|
->withPermissions(SpecialPermission::VIEW_FILAMENT->value)
|
|
->createOne();
|
|
|
|
actingAs($user);
|
|
});
|
|
|
|
/*
|
|
|--------------------------------------------------------------------------
|
|
| Expectations
|
|
|--------------------------------------------------------------------------
|
|
|
|
|
| When you're writing tests, you often need to check that values meet certain conditions. The
|
|
| "expect()" function gives you access to a set of "expectations" methods that you can use
|
|
| to assert different things. Of course, you may extend the Expectation API at any time.
|
|
|
|
|
*/
|
|
|
|
expect()->extend('toBeOne', fn () => $this->toBe(1));
|
|
|
|
/*
|
|
|--------------------------------------------------------------------------
|
|
| Functions
|
|
|--------------------------------------------------------------------------
|
|
|
|
|
| While Pest is very powerful out-of-the-box, you may have some testing code specific to your
|
|
| project that you don't want to repeat in every file. Here you can also expose helpers as
|
|
| global functions to help you to reduce the number of lines of code in your test files.
|
|
|
|
|
*/
|
|
|
|
// Filament
|
|
/**
|
|
* @param class-string<BaseResource> $resource
|
|
*/
|
|
function getIndexPage(string $resource): string
|
|
{
|
|
$pages = $resource::getPages();
|
|
|
|
return $pages['index']->getPage();
|
|
}
|
|
|
|
/**
|
|
* @param class-string<BaseResource> $resource
|
|
*/
|
|
function getViewPage(string $resource): string
|
|
{
|
|
$pages = $resource::getPages();
|
|
|
|
return $pages['view']->getPage();
|
|
}
|