laravel:tdd-with-pest
Laravel TDD (Pest/PHPUnit)
Write the test first. Watch it fail. Write minimal code to pass. Keep tests fast and realistic.
Test Runner
# Sail
sail artisan test --parallel
# Non-Sail
php artisan test --parallel
Prefer Pest (default in new Laravel apps). PHPUnit is fine if your project uses it.
RED – Write a failing test
- Use model factories; avoid heavy mocking
More from jpcaparas/superpowers-laravel
laravel:routes-best-practices
Keep routes clean and focused on mapping requests to controllers; avoid business logic, validation, or database operations in route files
97laravel:blade-components-and-layouts
Compose UIs with Blade components, slots, and layouts; keep templates pure and testable
96laravel:quality-checks
Unified quality gates for Laravel projects; Pint, static analysis (PHPStan/Psalm), Insights (optional), and JS linters; Sail and non-Sail pairs provided
87laravel:performance-caching
Use framework caches and value/query caching to reduce work; add tags, locks, and explicit invalidation strategies for correctness
84laravel:queues-and-horizon
Operate and verify queues with or without Horizon; safe worker flags, failure handling, and test strategies
83laravel:eloquent-relationships
Define clear relationships and load data efficiently; prevent N+1, use constraints, counts/sums, and pivot syncing safely
82