2025-02-01 00:09:50 +01:00
|
|
|
<?php declare(strict_types=1);
|
|
|
|
|
2025-02-06 20:35:49 +01:00
|
|
|
use App\Tests\DbApiTestCase;
|
2025-02-01 22:37:07 +01:00
|
|
|
use App\Tests\DbWebTest;
|
|
|
|
|
2025-02-01 00:09:50 +01:00
|
|
|
/*
|
|
|
|
|--------------------------------------------------------------------------
|
|
|
|
| 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.
|
|
|
|
|
|
|
|
|
*/
|
|
|
|
|
2025-02-01 22:37:07 +01:00
|
|
|
pest()
|
|
|
|
->extends(DbWebTest::class)->in('Feature/Controller/*.php');
|
2025-02-06 20:35:49 +01:00
|
|
|
pest()
|
|
|
|
->extends(DbApiTestCase::class)->in('Feature/Api/*.php');
|
2025-02-01 22:37:07 +01:00
|
|
|
|
2025-02-01 00:09:50 +01:00
|
|
|
/*
|
|
|
|
|--------------------------------------------------------------------------
|
|
|
|
| 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.
|
|
|
|
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
function something(): void
|
|
|
|
{
|
|
|
|
// ..
|
|
|
|
}
|