Agent Skills: Laravel Testing

Write tests with Pest 3/PHPUnit, feature tests, unit tests, mocking, fakes, and factories. Use when testing controllers, services, models, or implementing TDD.

UncategorizedID: fusengine/agents/laravel-testing

Install this agent skill to your local

pnpm dlx add-skill https://github.com/fusengine/agents/tree/HEAD/plugins/laravel-expert/skills/laravel-testing

Skill Files

Browse the full folder contents for laravel-testing.

Download Skill

Loading file tree…

plugins/laravel-expert/skills/laravel-testing/SKILL.md

Skill Metadata

Name
laravel-testing
Description
Write tests with Pest 4/PHPUnit 12, feature tests, unit tests, mocking, fakes, and factories. Use when testing controllers, services, models, or implementing TDD on Laravel 13.

Laravel Testing

Agent Workflow (MANDATORY)

Before ANY implementation, use TeamCreate to spawn 3 agents:

  1. fuse-ai-pilot:explore-codebase - Analyze existing test patterns
  2. fuse-ai-pilot:research-expert - Verify Pest/PHPUnit docs via Context7
  3. mcp__context7__query-docs - Check assertion and mocking patterns

After implementation, run fuse-ai-pilot:sniper for validation.


Overview

| Type | Purpose | Location | |------|---------|----------| | Feature | HTTP, full stack | tests/Feature/ | | Unit | Isolated classes | tests/Unit/ | | Arch | Code architecture | tests/Arch.php |


Decision Guide: Test Type

What to test?
├── HTTP endpoint → Feature test
├── Service/Policy logic → Unit test
├── Code structure → Arch test
├── External API → Mock with Http::fake()
├── Mail/Queue/Event → Use Fakes
└── Database state → assertDatabaseHas()

Decision Guide: Test Strategy

Coverage strategy?
├── Feature tests (70%) → Critical flows
├── Unit tests (25%) → Business logic
├── E2E tests (5%) → User journeys
└── Arch tests → Structural rules

Critical Rules

  1. Use RefreshDatabase for database isolation
  2. Use factories for test data (never raw inserts)
  3. Mock external services - Never call real APIs
  4. Test edge cases - Empty, null, boundaries
  5. Run parallel - pest --parallel for speed

Reference Guide

Pest Basics

| Topic | Reference | When to Consult | |-------|-----------|-----------------| | Pest Syntax | pest-basics.md | it(), test(), describe() | | Datasets | pest-datasets.md | Data providers, hooks | | Architecture | pest-arch.md | arch() tests |

HTTP Testing

| Topic | Reference | When to Consult | |-------|-----------|-----------------| | Requests | http-requests.md | GET, POST, headers | | JSON API | http-json.md | API assertions | | Authentication | http-auth.md | actingAs, guards | | Assertions | http-assertions.md | Status, redirects |

Database Testing

| Topic | Reference | When to Consult | |-------|-----------|-----------------| | Basics | database-basics.md | RefreshDatabase | | Factories | database-factories.md | Factory patterns | | Assertions | database-assertions.md | DB assertions |

Mocking

| Topic | Reference | When to Consult | |-------|-----------|-----------------| | Services | mocking-services.md | Mock, spy | | Fakes | mocking-fakes.md | Mail, Queue, Event | | HTTP & Time | mocking-http.md | Http::fake, travel |

Other

| Topic | Reference | When to Consult | |-------|-----------|-----------------| | Console | console-tests.md | Artisan tests | | Troubleshooting | troubleshooting.md | Common errors |

Templates

| Template | When to Use | |----------|-------------| | FeatureTest.php.md | HTTP feature test | | UnitTest.php.md | Service unit test | | ArchTest.php.md | Architecture test | | ApiTest.php.md | REST API test | | PestConfig.php.md | Pest configuration |


Quick Reference

// Feature test
it('creates a post', function () {
    $user = User::factory()->create();

    $this->actingAs($user)
        ->postJson('/api/posts', ['title' => 'Test'])
        ->assertCreated()
        ->assertJsonPath('data.title', 'Test');

    $this->assertDatabaseHas('posts', ['title' => 'Test']);
});

// With dataset
it('validates emails', function (string $email, bool $valid) {
    // test logic
})->with([
    ['valid@test.com', true],
    ['invalid', false],
]);

// Mock facade
Mail::fake();
// ... action ...
Mail::assertSent(OrderShipped::class);

Commands

# Run all tests
php artisan test

# Pest directly
./vendor/bin/pest

# Parallel execution
./vendor/bin/pest --parallel

# Filter by name
./vendor/bin/pest --filter "user can"

# Coverage
./vendor/bin/pest --coverage --min=80

# Profile slow tests
./vendor/bin/pest --profile

Best Practices

DO

  • Use RefreshDatabase trait
  • Follow AAA pattern (Arrange-Act-Assert)
  • Name tests descriptively
  • Test one thing per test
  • Use factories for data

DON'T

  • Create test dependencies
  • Call real external APIs
  • Use production database
  • Skip edge cases

Laravel 13 Notes

PHPUnit 12 + Pest 4

Laravel 13 exige PHPUnit 12 et supporte Pest 4. Les attributs PHP remplacent les annotations docblock.

use PHPUnit\Framework\Attributes\Test;
use Illuminate\Foundation\Testing\Attributes\Seed;
use Illuminate\Foundation\Testing\Attributes\Seeder;

#[Seed]                          // exécute DatabaseSeeder
#[Seeder(UserSeeder::class)]     // exécute un seeder ciblé
final class UserTest extends TestCase
{
    #[Test]
    public function it_creates_user(): void { /* ... */ }
}

Str cache reset

Laravel 13 réinitialise automatiquement les caches Str (random, slug) entre tests pour éviter le state leak. Aucun setup manuel requis.

Migration depuis Pest 3

  • pest --init regénère Pest.php avec la nouvelle API
  • Datasets supportent désormais les générateurs natifs PHP
  • expect()->toBeInstanceOf() → typage strict requis