Testing

The kits ship with a test suite and code quality checks that run locally and in CI with one command (composer test).

Tool	Purpose
Pest 5 + pestphp/pest-plugin-laravel	Feature and unit tests
Larastan (PHPStan)	Static analysis
Pint	PHP code style
ESLint, Prettier, framework type checker	Frontend lint and types (npm run lint)

Structure

tests/
├── Feature/
│   ├── Auth/            # Authentication, EmailVerification, PasswordConfirmation, PasswordReset,
│   │                    # Registration, TwoFactorChallenge, VerificationNotification
│   ├── Settings/        # ProfileUpdate, Security (+ LayoutSetting in React/Svelte)
│   ├── Tenancy/         # React and Svelte: TenantAuthentication, TenantCreation
│   ├── DashboardTest.php
│   └── ExampleTest.php
├── Unit/ExampleTest.php
├── Pest.php             # Feature tests extend TestCase and use RefreshDatabase
└── TestCase.php         # skipUnlessFortifyHas() helper

Removing a Fortify feature

tests/TestCase.php provides skipUnlessFortifyHas($feature), so auth tests skip cleanly when you remove a feature from config/fortify.php.

Test environment

Tests run on in-memory SQLite, so your MySQL data is never touched. phpunit.xml overrides:

Key	Value
DB_CONNECTION / DB_DATABASE	sqlite / :memory:
CACHE_STORE	array
SESSION_DRIVER	array
QUEUE_CONNECTION	sync
MAIL_MAILER	array
BCRYPT_ROUNDS	4

Commands

php artisan test --compact                                  # all Pest tests
php artisan test --compact tests/Feature/Auth               # one folder
php artisan test --compact --filter="users can authenticate" # one test
composer test                                               # full CI check

composer test runs the full check in this order:

config:clear → lint:check (Pint + npm run lint) → types:check (PHPStan) → php artisan test

• In the Vue kit, lint:check also runs wayfinder:generate --with-form.
• composer ci:check runs the same as composer test without a process timeout.

Frontend type checks are part of npm run lint (eslint . && prettier --check resources/ && <type checker>):

Kit	Type checker
Vue	vue-tsc --noEmit
React	tsc --noEmit
Svelte	svelte-check --tsconfig ./tsconfig.json

Writing tests

php artisan make:test --pest ProjectTest          # tests/Feature/ProjectTest.php
php artisan make:test --pest --unit ProjectTest   # tests/Unit/ProjectTest.php

A feature test for a permission-protected page:

use App\Models\User;

test('users with permission can view the users page', function () {
    $user = User::factory()->create();
    $user->givePermissionTo(
        Spatie\Permission\Models\Permission::findOrCreate('View Users', 'web')
    );

    $this->actingAs($user)->get(route('users.index'))->assertOk();
});

For tenant behaviour, create a tenant and switch context with tenancy()->initialize($tenant) or $tenant->run(...), and end tenancy in afterEach. See tests/Feature/Tenancy in the React or Svelte kit.

AI agent rules about tests

The kits ship Laravel Boost guidelines for AI coding agents. The two guideline files set different test rules:

File	Used by	Test rule
CLAUDE.md	Claude Code	Test Enforcement: every change must be tested; write or update a test and run the affected tests with php artisan test --compact
AGENTS.md	Codex, Junie and other agents	Testing Policy: do not create tests or run the suite unless the user asks

Both also say: use Pest (php artisan make:test --pest), use factories, and never delete tests without approval.

Align the rules with your team

Edit both files to match your team's policy. php artisan boost:update may regenerate them (it runs after composer update).

Project rules for agents live in .ai/rules/ (for example .ai/rules/general.md: no code comments in new code).