Installation

Testing for Laravel is a dev-only package — install it into require-dev. It ships assertions, a base test case, fixtures and Pest expectations. There is no service provider, no config file, no migration and nothing that runs in a production code path:

composer require --dev roundly-consulting/testing-for-laravel

The Pest expectations register automatically through the package’s Pest plugin (extra.pest.plugins), so they exist the moment the package is installed. Suites that disable plugin discovery register them explicitly in tests/Pest.php:

<?php

declare(strict_types=1);

use RoundlyConsulting\Testing\Expectations\Expectations;

uses(Tests\TestCase::class)->in('Arch', 'Feature', 'Unit');

Expectations::register(); // idempotent — a no-op if the Pest plugin already ran

Both paths coexist: Expectations::register() guards on an internal flag, so calling it after the plugin already ran is a no-op. Expectations::registered() reports whether registration has happened.

Bind the Arch directory to your TestCase too, as above. Several checks read the booted application — swappableModelsAreNotFinal, toBeSwappableVia and toBeFakeable among them — and an arch file bound to no TestCase has none; they fail with instructions rather than passing.

Three call styles

Assertions are reachable in three styles. Lead with the Pest expectation — it is the canonical, documented API:

use RoundlyConsulting\Testing\Arch\ArchPresets;
use RoundlyConsulting\Testing\Assert;

// 1. Pest expectation — the canonical API
expect(database_path('migrations'))->toHaveRunnableMigrationOrder();

// 2. Static mirror — for plain PHPUnit test classes
Assert::migrationsRunInDependencyOrder(database_path('migrations'));

// 3. Arch preset — at the top level of a Pest arch file
ArchPresets::strictTypes('App');

Package surface vs app surface

• Works in any Laravel app, Testbench-free: the static Assert, every Pest expectation except the two publish-only guards, and ArchPresets. The package’s own arch test enforces that none of them references Testbench.
• Package-only: PackageTestCase, the LoadsProviderMigrations concern, and the toNotAutoLoadMigrations / toPublishMigrationsTimestamped expectations — they assume a package service provider and Testbench.