Packages Toolkit for Laravel

https://packages.tools/
Admin
Packages Toolkit for Laravel is a collection of tools for writing, testing, and previewing Laravel...
Tokens:10,212
Snippets:121
Trust Score:6.3
Update:7 months ago
Show doc for...
Tokens:
Raw
### Override setUp Method

Source: https://packages.tools/testbench/the-basic

Demonstrates how to safely override the setUp method in Testbench, ensuring parent::setUp() is called and utilizing lifecycle hooks like afterApplicationCreated.

```php
class TestCase extends \Orchestra\Testbench\TestCase
{
    protected function setUp(): void
    {
        $this->afterApplicationCreated(function () {
            // Code after application created.
        });

        $this->beforeApplicationDestroyed(function () {
            // Code before application destroyed.
        });

        parent::setUp();
    }
}
```

--------------------------------

### Install Testbench for Laravel Packages

Source: https://packages.tools/testbench

Installs the Testbench package for Laravel development using Composer. This is the first step to setting up an environment for package testing.

```bash
composer require --dev "orchestra/testbench"
```

--------------------------------

### Replace Testbench with Browser Kit Support

Source: https://packages.tools/testbench/troubleshooting

Resolves missing browser kit support when testing on Laravel 5.4 by replacing `orchestra/testbench` with `orchestra/testbench-browser-kit`. Users should follow the installation guide for the new package.

```bash
# No direct code example provided, but implies a composer command like:
# composer require --dev "orchestra/testbench-browser-kit:^x.y.z"
```

--------------------------------

### Install and Scaffold Testbench Dusk

Source: https://packages.tools/testbench-dusk

Commands to install the Testbench Dusk dependency via Composer and scaffold the package with the recommended workbench directory structure.

```bash
composer require --dev "orchestra/testbench-dusk"
vendor/bin/testbench workbench:install
```

--------------------------------

### Scaffold Package with Testbench

Source: https://packages.tools/testbench

Scaffolds a new Laravel package with the recommended setup using the Testbench CLI. This command helps initialize the necessary files and configurations for package development.

```bash
vendor/bin/testbench workbench:install
```

--------------------------------

### Run Laravel Package Tests with Collision and Testbench CLI

Source: https://packages.tools/testbench/integrations

Demonstrates how to execute the `package:test` command using the Testbench CLI after installing the `nunomaduro/collision` package. This command leverages Collision for enhanced testing capabilities.

```bash
vendor/bin/testbench package:test
```

--------------------------------

### Workbench Configuration YAML

Source: https://packages.tools/testbench-dusk

Example configuration for testbench.yaml defining service providers and the custom Laravel skeleton path.

```yaml
providers:
  - Laravel\Sanctum\SanctumServiceProvider
  - Workbench\App\Providers\WorkbenchServiceProvider

laravel: ./skeleton
```

--------------------------------

### Install Collision for Laravel-Flavored Artisan Test Commands

Source: https://packages.tools/testbench/integrations

Provides the Composer command to install the `nunomaduro/collision` package, which enables Laravel-flavored artisan test commands within Testbench. This is a prerequisite for using commands like `package:test`.

```bash
composer require --dev "nunomaduro/collision"
```

--------------------------------

### Configure Testbench Versions for Legacy Factories

Source: https://packages.tools/testbench/troubleshooting

Ensures `orchestra/testbench` uses compatible minimum versions when `laravel/legacy-factories` is required, preventing CI issues. The example shows how to specify version constraints in `composer.json` for supporting Laravel 5.6 and below.

```json
{
    "require-dev": {
        "orchestra/testbench": "~3.6.7 || ~3.7.8 || ~3.8.6 || ^4.8 || ^5.2 || ^6.0"
    }
}
```

--------------------------------

### Use Spatie Ray for Debugging in PHPUnit Tests

Source: https://packages.tools/testbench/integrations

Demonstrates how to use the Spatie Ray debugging tool within PHPUnit tests when using Laravel Testbench. This requires Testbench version 6.10 or later and the Ray package installed.

```php
use PHPUnit\Framework\Attributes\Test;

#[Test]
public function it_can_resolve_domain_route()
{
    /** @var \Illuminate\Testing\TestResponse $response */
    $response = $this->get('http://api.localhost/hello');

    ray($response);
}
```

--------------------------------

### Run Default Laravel Migrations with WithMigration Attribute

Source: https://packages.tools/testbench/the-basic/databases

Includes the `WithMigration` attribute to automatically run default Laravel migrations, such as the 'users' table. This simplifies the setup for tests requiring core Laravel tables.

```php
use Orchestra\Testbench\Attributes\WithMigration; 

#[WithMigration] 
class TestCase extends \Orchestra\Testbench\TestCase
{
    //
}
```

--------------------------------

### Define Application Environment Setup in Laravel Testbench

Source: https://packages.tools/testbench/the-basic/environment

The defineEnvironment method allows for custom configuration during the application bootstrapping process. It is commonly used to override database connections or queue configurations before service providers are fully booted.

```php
use IlluminateContractsConfigRepository;

class TestCase extends \Orchestra\Testbench\TestCase
{
    protected function defineEnvironment($app) 
    {
        tap($app['config'], function (Repository $config) { 
            $config->set('database.default', 'testbench'); 
            $config->set('database.connections.testbench', [ 
                'driver'   => 'sqlite', 
                'database' => ':memory:', 
                'prefix'   => '', 
            ]); 
            
            $config([ 
                'queue.batching.database' => 'testbench', 
                'queue.failed.database' => 'testbench', 
            ]); 
        });
    }
}
```

```php
protected function getEnvironmentSetup($app)
{
    // Backward compatible method for environment setup
}
```

--------------------------------

### Configure In-Memory SQLite Database for PHPUnit

Source: https://packages.tools/testbench/the-basic/databases

Sets the 'testing' database connection to use an in-memory SQLite database for reduced setup. This is configured within the PHPUnit XML configuration file.

```xml
<phpunit>
    // ...
    <php>
        <env name="DB_CONNECTION" value="testing"/>
    </php>
</phpunit>
```

--------------------------------

### Enable Parallel Testing with Testbench Package Test Command

Source: https://packages.tools/testbench/integrations

Illustrates how to use the `--parallel` option with the `vendor/bin/testbench package:test` command to enable parallel testing. Users should consult Laravel documentation for detailed configuration and considerations regarding parallel testing.

```bash
vendor/bin/testbench package:test --parallel
```

--------------------------------

### Configure Spatie Ray Debugging via PHPUnit XML

Source: https://packages.tools/testbench/integrations

Shows how to configure Spatie Ray's integration with Testbench using the `phpunit.xml` configuration file. This allows enabling or disabling various Ray features like sending dumps, logs, and exceptions.

```xml
<phpunit>

    // ...

    <php>
        <env name="RAY_ENABLED" value="(true)"/>
        <env name="SEND_CACHE_TO_RAY" value="(false)"/>
        <env name="SEND_DUMPS_TO_RAY" value="(true)"/>
        <env name="SEND_JOBS_TO_RAY" value="(false)"/>
        <env name="SEND_LOG_CALLS_TO_RAY" value="(true)"/>
        <env name="SEND_QUERIES_TO_RAY" value="(false)"/>
        <env name="SEND_REQUESTS_TO_RAY" value="(false)"/>
        <env name="SEND_VIEWS_TO_RAY" value="(false)"/>
        <env name="SEND_EXCEPTIONS_TO_RAY" value="(true)"/>
    </php>

</phpunit>
```

--------------------------------

### Run Browser Tests

Source: https://packages.tools/testbench-dusk

Command to execute only the tests defined within the Browser test suite.

```bash
vendor/bin/phpunit --testsuite=Browser
```

--------------------------------

### Override Console and HTTP Kernels

Source: https://packages.tools/testbench/the-basic

Shows how to swap the default Console or HTTP kernels by overriding the resolveApplicationConsoleKernel and resolveApplicationHttpKernel methods.

```php
use Illuminate\Contracts\Console\Kernel as ConsoleKernel;
use Illuminate\Contracts\Http\Kernel as HttpKernel;

class TestCase extends \Orchestra\Testbench\TestCase
{
    protected function resolveApplicationConsoleKernel($app) 
    {
        $app->singleton(ConsoleKernel::class, 'Tests\Console\Kernel');
    }

    protected function resolveApplicationHttpKernel($app) 
    {
        $app->singleton(HttpKernel::class, 'Tests\Http\Kernel');
    }
}
```

--------------------------------

### Configure Workbench Integration

Source: https://packages.tools/testbench-dusk

Uses the WithWorkbench trait to enable configuration via testbench.yaml, including custom service providers and Laravel skeleton paths.

```php
use Orchestra\Testbench\Concerns\WithWorkbench; 

class DuskTestCase extends \Orchestra\Testbench\Dusk\TestCase
{
    use WithWorkbench; 
}
```

--------------------------------

### Enable Testbench Workbench Autoloading

Source: https://packages.tools/testbench

Enables autoloading using `testbench.yaml` by using the `WithWorkbench` trait in your TestCase. This allows Testbench to use configurations defined in the `testbench.yaml` file.

```php
use Orchestra\Testbench\Concerns\WithWorkbench;

class TestCase extends \Orchestra\Testbench\TestCase
{
    use WithWorkbench;
}
```

--------------------------------

### Configure Package Service Providers in testbench.yaml

Source: https://packages.tools/testbench

Defines the package service providers to be used when `WithWorkbench` is enabled. This configuration is read from the `testbench.yaml` file.

```yaml
providers:
  - Laravel\Sanctum\SanctumServiceProvider
  - Workbench\App\Providers\WorkbenchServiceProvider
```

--------------------------------

### Configure Dusk Test Case

Source: https://packages.tools/testbench-dusk

Demonstrates extending the base Testbench Dusk TestCase class to enable browser testing capabilities in your package.

```php
class DuskTestCase extends \Orchestra\Testbench\Dusk\TestCase
{
    //
}
```

--------------------------------

### Configure PHPUnit Test Suites

Source: https://packages.tools/testbench

Shows how to configure `phpunit.xml` to separate tests into different suites, such as 'Feature' and 'Unit'. This allows for running specific test types on demand.

```xml
<testsuites>
    <testsuite name="Feature">
        <directory suffix="Test.php">./tests/Feature</directory>
    </testsuite>
    <testsuite name="Unit">
        <directory suffix="Test.php">./tests/Unit</directory>
    </testsuite>
</testsuites>
```

--------------------------------

### Configure Package Auto-Discovery

Source: https://packages.tools/testbench/the-basic

Manages package auto-discovery in Testbench by either ignoring specific packages, enabling all, or setting a global property.

```php
class TestCase extends \Orchestra\Testbench\TestCase
{
    /**
     * Ignore package discovery from.
     *
     * @return array<int, string>
     */
    public function ignorePackageDiscoveriesFrom() 
    {
        return [ 
            'laravel/passport',
        ];
    }
}

// Enable all
class TestCase extends \Orchestra\Testbench\TestCase
{
    public function ignorePackageDiscoveriesFrom() 
    {
        return [];
    }
}

// Global property
class TestCase extends \Orchestra\Testbench\TestCase
{
    protected $enablesPackageDiscoveries = true; 
}
```

--------------------------------

### Configure APP_KEY for Encrypter Errors in PHPUnit

Source: https://packages.tools/testbench/troubleshooting

Resolves the 'No supported encrypter found' error in test suites by adding a dummy or specific `APP_KEY` to the `phpunit.xml` configuration file. This ensures the encrypter has a valid key for testing purposes.

```xml
<phpunit>
    // ...
    <php>
        <env name="APP_KEY" value="AckfSECXIvnK5r28GVIWUAxmbBSjTsmF"/>
    </php>
</phpunit>
```

--------------------------------

### Run Testing-Specific Migrations

Source: https://packages.tools/testbench/the-basic/databases

Loads migrations specifically intended for testing purposes from a designated directory (e.g., 'workbench/database/migrations') within the `defineDatabaseMigrations` method. This separates test data from package migrations.

```php
use function Orchestra\Testbench\workbench_path; 

class TestCase extends \Orchestra\Testbench\TestCase
{
    /**
     * Define database migrations.
     *
     * @return void
     */
    protected function defineDatabaseMigrations() 
    {
        $this->loadMigrationsFrom(
            workbench_path('database/migrations')
        );
    }
}
```

--------------------------------

### Configure Custom Laravel Skeleton in testbench.yaml

Source: https://packages.tools/testbench

Specifies a custom Laravel skeleton path to be used when `WithWorkbench` is enabled. This allows for testing against a specific Laravel application structure defined in `testbench.yaml`.

```yaml
laravel: ./skeleton
```

--------------------------------

### Extend Testbench TestCase for Laravel Tests

Source: https://packages.tools/testbench

Demonstrates how to extend Orchestra\Testbench\TestCase instead of the default PHPUnit\Framework\TestCase. This provides a pre-configured Laravel application fixture for testing.

```php
class TestCase extends \Orchestra\Testbench\TestCase
{
    //
}
```

--------------------------------

### Define PHPUnit Test Suites

Source: https://packages.tools/testbench-dusk

Configures the phpunit.xml file to separate browser tests from feature and unit tests, allowing for targeted test execution.

```xml
<testsuites>
    <testsuite name="Browser">
        <directory suffix="Test.php">./tests/Browser</directory>
    </testsuite>
    <testsuite name="Feature">
        <directory suffix="Test.php">./tests/Feature</directory>
    </testsuite>
    <testsuite name="Unit">
        <directory suffix="Test.php">./tests/Unit</directory>
    </testsuite>
</testsuites>
```

--------------------------------

### Configure Application Key and Timezone

Source: https://packages.tools/testbench/the-basic/environment

Set global application settings like the APP_KEY via XML configuration or override the default timezone using the getApplicationTimezone method.

```xml
<phpunit>
    <php>
        <env name="APP_KEY" value="AckfSECXIvnK5r28GVIWUAxmbBSjTsmF"/>
    </php>
</phpunit>
```

```php
protected function getApplicationTimezone($app)
{
    return 'Asia/Kuala_Lumpur';
}
```

--------------------------------

### Override Application Bindings

Source: https://packages.tools/testbench/the-basic

Allows replacing default Laravel service providers with custom implementations using the overrideApplicationBindings method.

```php
class TestCase extends \Orchestra\Testbench\TestCase
{
    /**
     * Get package providers.
     *
     * @param  \Illuminate\Foundation\Application  $app
     * @return array<class-string<\Illuminate\Support\ServiceProvider>, class-string<\Illuminate\Support\ServiceProvider>>
     */
    protected function overrideApplicationBindings($app) 
    {
        return [
            'Illuminate\View\ViewServiceProvider' => 'Acme\ViewServiceProvider',
        ];
    }
}
```

--------------------------------

### Manually Configure and Execute Migrations

Source: https://packages.tools/testbench/the-basic/databases

Manually defines and executes migration steps using the `defineDatabaseMigrations` method and the `artisan` helper. This allows for custom migration control, including rollback.

```php
use function Orchestra\Testbench\artisan; 

class TestCase extends \Orchestra\Testbench\TestCase
{
    /**
     * Define database migrations.
     *
     * @return void
     */
    protected function defineDatabaseMigrations() 
    {
        artisan($this, 'migrate', ['--database' => 'testbench']);

        $this->beforeApplicationDestroyed(
            fn () => artisan($this, 'migrate:rollback', ['--database' => 'testbench'])
        );
    }
}
```

--------------------------------

### Modify Served Application Instance Configuration

Source: https://packages.tools/testbench-dusk/the-basic

Uses the beforeServingApplication method to apply temporary configuration changes to the served Laravel instance during a specific test case.

```php
use Laravel\Dusk\Browser;
use PHPUnit\Framework\Attributes\Test;

// ...

#[Test]
public function it_can_send_email()
{
    $this->beforeServingApplication(function ($app, $config) { 
        $config->set('mail.default', 'log');
    });

    $this->browse(function (Browser $browser) {

    });
}
```

--------------------------------

### Run Specific PHPUnit Test Suite

Source: https://packages.tools/testbench

Executes only the feature tests defined in the PHPUnit configuration by using the `--testsuite=Feature` option. This is useful for focusing on integration and feature-level testing.

```bash
vendor/bin/phpunit --testsuite=Feature
```

--------------------------------

### Automatically Run Package Migrations with RefreshDatabase

Source: https://packages.tools/testbench/the-basic/databases

Uses the `RefreshDatabase` trait to automatically run package migrations defined in the service provider. This trait ensures migrations are run before each test and rolled back afterward.

```php
use Illuminate\Foundation\Testing\RefreshDatabase; 

class TestCase extends \Orchestra\Testbench\TestCase
{
    use RefreshDatabase; 
}
```

--------------------------------

### Configure Database Connection for Dusk

Source: https://packages.tools/testbench-dusk/the-basic

Sets the default database connection for the test environment. Note that SQLite in-memory mode is not supported in Testbench Dusk.

```php
class DuskTestCase extends \Orchestra\Testbench\Dusk\TestCase
{
    /**
     * Define environment setup.
     *
     * @param  Illuminate\Foundation\Application  $app
     *
     * @return void
     */
    protected function defineEnvironment($app) 
    {
        $this->app['config']->set('database.default', 'sqlite');
    }
}
```

```bash
vendor/bin/testbench-dusk package:create-sqlite-db
```

--------------------------------

### Set In-Memory SQLite Database using defineEnvironment

Source: https://packages.tools/testbench/the-basic/databases

Explicitly sets the default database connection to 'testing' within the `defineEnvironment` method of the test class. This provides a programmatic way to configure the database connection.

```php
class TestCase extends \Orchestra\Testbench\TestCase
{
    /**
     * Define environment setup.
     *
     * @param  \Illuminate\Foundation\Application  $app
     * @return void
     */
    protected function defineEnvironment($app)
    {
        $app['config']->set('database.default', 'testing');
    }
}
```

--------------------------------

### Update ChromeDriver for Laravel Dusk

Source: https://packages.tools/testbench-dusk/troubleshooting

If you encounter 'session not created: Chrome version must be between 70 and 73' errors, this command updates your ChromeDriver to a compatible version. It ensures compatibility between your Chrome browser and the WebDriver used by Laravel Dusk.

```bash
vendor/bin/dusk-updater update
```

```bash
vendor/bin/dusk-updater detect --auto-update
```

--------------------------------

### Add Guzzle HTTP Client Dependency for Laravel 7+

Source: https://packages.tools/testbench/troubleshooting

Ensures the HTTP Client in Laravel 7 and later versions functions correctly by adding the `guzzlehttp/guzzle` dependency to the package's `composer.json` file. This is necessary because `guzzlehttp/guzzle` might be an optional requirement in `laravel/laravel` and could be removed by developers.

```bash
composer require "guzzlehttp/guzzle"
```

--------------------------------

### Register Package Service Providers

Source: https://packages.tools/testbench/the-basic

Overrides the getPackageProviders method to register custom service providers for the test environment. It returns an array of provider class strings.

```php
class TestCase extends \Orchestra\Testbench\TestCase
{
    /**
     * Get package providers.
     *
     * @param  \Illuminate\Foundation\Application  $app
     * @return array<int, class-string<\Illuminate\Support\ServiceProvider>>
     */
    protected function getPackageProviders($app) 
    {
        return [
            'Acme\AcmeServiceProvider',
        ];
    }
}
```

--------------------------------

### Run Specific Laravel Migrations with WithMigration Attribute

Source: https://packages.tools/testbench/the-basic/databases

Uses the `WithMigration` attribute with parameters to selectively run specific Laravel migrations like 'cache', 'queue', 'notifications', or 'session'. This allows for fine-grained control over which default migrations are included.

```php
use Orchestra\Testbench\Attributes\WithMigration; 

#[WithMigration('laravel', 'cache', 'queue')] 
#[WithMigration('session')]
class TestCase extends \Orchestra\Testbench\TestCase
{
    //
}
```

--------------------------------

### Configure Custom Host and Port for Testbench Dusk

Source: https://packages.tools/testbench-dusk/the-basic

Overrides the default server host and port used by Testbench Dusk during testing. By default, it uses 127.0.0.1 on port 8001.

```php
class DuskTestCase extends \Orchestra\Testbench\Dusk\TestCase
{
    /**
     * The base serve host URL to use while testing the application.
     *
     * @var string
     */
    protected static $baseServeHost = '127.0.0.1'; 

    /**
     * The base serve port to use while testing the application.
     *
     * @var int
     */
    protected static $baseServePort = 9000; 
}
```

--------------------------------

### Toggle Browser UI Visibility in Dusk Tests

Source: https://packages.tools/testbench-dusk/the-basic

Controls whether the browser window appears during test execution. Using withoutUI() is the default and typically results in faster test performance.

```php
use Orchestra\Testbench\Dusk\Options; 

class DuskTestCase extends \Orchestra\Testbench\Dusk\TestCase
{
    /**
     * Prepare the testing environment web driver options.
     *
     * @api
     *
     * @return void
     */
    public static function defineWebDriverOptions() 
    {
        // To show the UI during testing
        Options::withUI();

        // To hide the UI during testing
        Options::withoutUI();
    }
}
```

--------------------------------

### Enable Blade Component Testing

Source: https://packages.tools/testbench/the-basic

Integrates the InteractsWithViews trait into the test case to allow for testing Blade components within the Orchestra Testbench framework.

```php
use Illuminate\Foundation\Testing\Concerns\InteractsWithViews; 

class TestCase extends \Orchestra\Testbench\TestCase
{
    use InteractsWithViews; 
}
```

--------------------------------

### Define Routes with defineRoutes() Method in Laravel Packages

Source: https://packages.tools/testbench/the-basic/routes

This PHP code snippet shows how to use the `defineRoutes()` method within a Laravel TestCase to set up routes early in the application bootstrapping process. This method is executed between registering and booting service providers.

```php
class TestCase extends \Orchestra\Testbench\TestCase
{
    /**
     * Define routes setup.
     *
     * @param  \Illuminate\Routing\Router  $router
     * @return void
     */
    protected function defineRoutes($router)
    {
        // Define routes.
    }
}
```

--------------------------------

### Register Package Aliases

Source: https://packages.tools/testbench/the-basic

Overrides the getPackageAliases method to register custom facades or aliases for the test application. It returns an associative array mapping alias names to class strings.

```php
class TestCase extends \Orchestra\Testbench\TestCase
{
    /**
     * Override application aliases.
     *
     * @param  \Illuminate\Foundation\Application  $app
     * @return array<string, class-string<\Illuminate\Support\Facades\Facade>>
     */
    protected function getPackageAliases($app) 
    {
        return [
            'Acme' => 'Acme\Facade',
        ];
    }
}
```

--------------------------------

### Set In-Memory SQLite Database using WithConfig Attribute

Source: https://packages.tools/testbench/the-basic/databases

Configures the database default connection to 'testing' using the `WithConfig` attribute from OrchestraTestbench. This attribute directly sets configuration values for the test class.

```php
use Orchestra\Testbench\Attributes\WithConfig; 

#[WithConfig('database.default', 'testing')] 
class TestCase extends \Orchestra\Testbench\TestCase 
{
    //
}
```

--------------------------------

### Set In-Memory SQLite Database using WithEnv Attribute

Source: https://packages.tools/testbench/the-basic/databases

Configures the 'testing' database connection using the `WithEnv` attribute from OrchestraTestbench. This attribute sets environment variables for the test class.

```php
use Orchestra\Testbench\Attributes\WithEnv; 

#[WithEnv('DB_CONNECTION', 'testing')] 
class TestCase extends \Orchestra\Testbench\TestCase
{
    //
}
```

--------------------------------

### Require laravel/legacy-factories for Laravel 8+ Compatibility

Source: https://packages.tools/testbench/troubleshooting

Addresses the 'Class Illuminate\Database\Eloquent\Factory not found' error in Laravel 8 by requiring the `laravel/legacy-factories` package. This allows packages to support older Laravel versions while using the new class-based factories, with a minimum PHP 7.3 requirement.

```bash
composer require --dev "laravel/legacy-factories:^1.0.4"
```

--------------------------------

### Configure Laravel Dusk Testbase for Migration Conflicts

Source: https://packages.tools/testbench-dusk/troubleshooting

Resolves 'Cannot declare class CreateUsersTable' errors when using `loadLaravelMigrations()` with both Dusk and standard Testbench test classes. This involves overriding `applicationBasePath()` to ensure all tests use the same Laravel skeleton from `testbench-dusk`.

```php
use function Orchestra\Testbench\package_path; 

class DuskTestCase extends \Orchestra\Testbench\Dusk\TestCase 
{
    /**
     * Get Application base path.
     *
     * @return string
     */
    public static function applicationBasePath()
    {
        // Adjust this path depending on where your override is located.
        return package_path('vendor/orchestra/testbench-dusk/laravel'); 
    }
}
```

--------------------------------

### Control Environment Variable Loading

Source: https://packages.tools/testbench/the-basic/environment

Configure whether Testbench automatically loads the .env file by toggling the $loadEnvironmentVariables property in your TestCase.

```php
class TestCase extends \Orchestra\Testbench\TestCase
{    
    protected $loadEnvironmentVariables = false; 
}
```

--------------------------------

### Customize Environment per Test using Attributes and Annotations

Source: https://packages.tools/testbench/the-basic/environment

Use the DefineEnvironment attribute or the deprecated @define-env annotation to apply specific environment configurations to individual test methods.

```php
use Orchestra\Testbench\Attributes\DefineEnvironment;
use PHPUnit\Framework\Attributes\Test;

class TestCase extends \Orchestra\Testbench\TestCase
{
    protected function usesMySqlConnection($app) { $app['config']->set('database.default', 'mysql'); }

    #[Test]
    #[DefineEnvironment('usesMySqlConnection')]
    public function it_can_be_connected_with_mysql() { /* ... */ }
}
```

```php
/**
 * @test
 * @define-env usesMySqlConnection
 */
public function it_can_be_connected_with_mysql() { /* ... */ }
```

--------------------------------

### Customize defineRoutes() with Attributes in Laravel Packages

Source: https://packages.tools/testbench/the-basic/routes

This PHP code demonstrates using the `Orchestra\Testbench\Attributes\DefineRoute` attribute to customize the `defineRoutes()` method for specific tests. This allows for granular control over route definitions on a per-test basis.

```php
use Orchestra\Testbench\Attributes\DefineRoute; 
use PHPUnit\Framework\Attributes\Test;

class TestCase extends \Orchestra\Testbench\TestCase
{
    /**
     * Define routes setup.
     *
     * @param  \Illuminate\Routing\Router  $router
     * @return void
     */
    protected function usesAuthRoutes($router)
    {
        // Load auth routes.
    }

    #[Test]
    #[DefineRoute('usesAuthRoutes')] 
    public function it_does_load_auth_routes()
    {
        // 
    }

    #[Test]
    public function it_doesnt_load_auth_routes()
    {
        //
    }
}
```

--------------------------------

### Override Laravel Skeleton Path in Testbench

Source: https://packages.tools/testbench/the-basic

Configures the base path for the Laravel skeleton used in tests. Use applicationBasePath for modern versions or getBasePath as a fallback for versions prior to v6.22.0.

```php
use function Orchestra\Testbench\package_path;

class TestCase extends \Orchestra\Testbench\TestCase
{
    /**
     * Get Application base path.
     *
     * @return string
     */
    public static function applicationBasePath() 
    {
        return package_path('skeleton');
    }
}
```

```php
class TestCase extends \Orchestra\Testbench\TestCase 
{
    /**
     * Get base path.
     *
     * @return string
     */
    protected function getBasePath() 
    {
        return __DIR__.'/../skeleton';
    }
}
```

--------------------------------

### Customize defineRoutes() with Deprecated Annotations in Laravel Packages

Source: https://packages.tools/testbench/the-basic/routes

This PHP code shows the deprecated usage of `@define-route` annotation to customize the `defineRoutes()` method for specific tests. While functional, it is recommended to use attributes for future compatibility.

```php
class TestCase extends \Orchestra\Testbench\TestCase
{
    /**
     * Define routes setup.
     *
     * @param  \Illuminate\Routing\Router  $router
     * @return void
     */
    protected function usesAuthRoutes($router)
    {
        // Load auth routes.
    }

    /**
     * @test
     * @define-route usesAuthRoutes
     */
    public function it_does_load_auth_routes()
    {
        // 
    }

    /**
     * @test
     */
    public function it_doesnt_load_auth_routes()
    {
        //
    }
}
```

--------------------------------

### Utilize Database Transactions for Migrated State

Source: https://packages.tools/testbench/the-basic/databases

Employs the `DatabaseTransactions` trait to manage database state within transactions for each test. This ensures a clean database state for every test by rolling back transactions after execution.

```php
use Illuminate\Foundation\Testing\DatabaseTransactions; 

class TestCase extends \Orchestra\Testbench\TestCase
{
    use DatabaseTransactions; 
}
```
Tokens:
Raw