<?php

declare(strict_types=1);

/*
|--------------------------------------------------------------------------
| Test Case Configuration
|--------------------------------------------------------------------------
|
| 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.
|
| Test Groups:
| - feature: Integration tests that test your application's features
| - unit: Unit tests that test individual components in isolation
| - browser: Browser tests that test your application in a real browser
|
*/

// Feature tests
pest()->extend(Tests\TestCase::class)
    ->group('feature')
    ->in('Feature');

// Unit tests
pest()->extend(Tests\TestCase::class)
    ->group('unit')
    ->in('Unit');

// Browser tests (if you have browser testing setup)
pest()->extend(Tests\TestCase::class)
    ->group('browser')
    ->in('Browser');

pest()->presets()
    ->custom('skeleton', function (array $userNamespaces) {
        return [
            expect($userNamespaces)->toUseStrictEquality(),
            expect([
                'sleep',
                'usleep',
            ])->not->toBeUsed(),
        ];
    });
/*
|--------------------------------------------------------------------------
| 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', function () {
    return $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.
|
*/

function something()
{
    // ..
}
