Enforces Pest testing conventions for Laravel projects including coverage and mocking rules.
npx skills add https://github.com/loki495/dotfiles --skill pest-testing-loki495
Please help me install this Agent Skill. Skill: pest-testing Source: https://github.com/loki495/dotfiles/tree/main/ai/skills/pest-testing Command: npx skills add https://github.com/loki495/dotfiles --skill pest-testing-loki495
it(), test(), describe() blocks and the expect() expectation API, never PHPUnit class-based syntax. - Coverage rules: Mandates both happy-path and sad-path tests per action, with sad paths asserting the correct handled outcome (422, specific exception, redirect with flash error) rather than just a status code. - Third-party API mocking: Directs use of Http::fake() for network calls, with sandbox credentials and idempotency rules when real API hits are unavoidable. - Hard rule against test tampering: Prohibits deleting, weakening, or skipping tests to make a failing suite pass; failures must be fixed in code or escalated. - Use Case: When asked to write tests for a new Laravel action, the Skill produces Pest tests calling handle() directly with factory-built data, covering valid input, validation failures, and mocked third-party failures. ## Quick Start Write Pest tests for this Laravel action covering both the happy path and validation failure cases, mocking any external API calls with Http::fake().High-intent search queries and answers about installing and using this skill.
Write Pest tests using it(), test(), and describe() blocks with the expect() expectation API, never PHPUnit class syntax. Call the action's handle() method directly and assert on the returned result, grouping related tests in describe() blocks.
Mock third-party calls with Http::fake() or the relevant fake instead of hitting real services. If a real hit is necessary, use the provider's sandbox endpoint or test mode, keep the test idempotent, and avoid consuming paid credits.
Happy path coverage tests valid input with expected success, while sad paths test invalid input, failed validation, unauthorized access, and third-party failures. Sad-path tests must assert the correct handled outcome, such as a 422 with validation errors, not just any response.
Use the RefreshDatabase trait on feature tests that touch the database. Confirm which driver the project uses first, since SQLite in-memory is common for fast local runs but some SQL features behave differently between SQLite and MySQL.
No. Tests must never be deleted, have assertions weakened, or be skipped to force a pass without explicit confirmation. The default action is to fix the underlying code or flag the conflict and ask how to proceed.
No, these conventions apply to Laravel projects only. OpenCart projects are excluded unless a project explicitly opts in through its own .claude/project.md configuration.
Mentor-WizardGenerate Laravel application architecture using Laravel Actions, domain organization, and Eloquent models.
latitude-devMonitor GitHub PR CI checks and automatically fix failures until all pass.
kveperedoImplements Prisma ORM v7 driver adapters for custom database drivers.
ensi-platformCreate Pest PHP tests for Ensi Laravel API endpoints and database models.