$ recombobulate _
home / tips / use-claude-to-write-pest-php-tests
233

Use Claude to Write Pest PHP Tests

recombobulate @recombobulate · Mar 26, 2026 · Workflows
use-claude-to-write-pest-php-tests

Pest's expressive syntax is a joy to write, but generating a full test suite from scratch still takes time. Just describe the behaviour and let Claude do the heavy lifting.

claude "Write Pest tests for a UserRegistrationService that validates email uniqueness, hashes passwords, and fires a UserRegistered event. Include happy path and failure cases."

Claude will scaffold a complete test file using Pest's fluent it() and expect() API, including setup, mocking, and assertions — without you having to hand-craft each case.

For existing code, paste the class directly and ask Claude to cover it:

cat app/Services/OrderService.php | claude "Write thorough Pest tests for this class. Use mocks for any external dependencies and cover edge cases."

You can also ask Claude to add arch tests — Pest's static analysis layer — to enforce your project's structural rules:

// Claude can generate these too
arch('controllers should not use models directly')
    ->expect('App\Http\Controllers')
    ->not->toUse('App\Models');

Let Claude write the tests — you just make them pass.

~/recombobulate $ tip --comments --count=0

Log in to leave a comment.

~/recombobulate $ tip --related --limit=3
0
Run Claude Code in GitHub Actions to Automatically Review Every Pull Request

Set up Claude Code as an automated reviewer in your CI pipeline — on every pull request, it reads the diff, checks for bugs, security issues, missing tests, and convention violations, then posts its findings as a PR comment. Your human reviewers get a head start because the obvious issues are already flagged before they look.

recombobulate @recombobulate · 1 month ago
0
Ask Claude to Build a Deployment Checklist from Your Actual Infrastructure

Before deploying, tell Claude to read your project — migrations, environment variables, queue workers, scheduled tasks, caching, third-party integrations — and generate a deployment checklist that's specific to your app. Not a generic "did you run migrations?" list, but one that knows YOUR infrastructure and catches the things YOUR deploy can break.

recombobulate @recombobulate · 1 month ago
0
Ask Claude to Generate a README from Your Actual Codebase — Not a Template

Instead of writing a README from memory or copying a template, tell Claude to read your project and generate one that's actually accurate — real setup instructions from your config, real architecture from your directory structure, real API examples from your routes, and real prerequisites from your dependency files.

recombobulate @recombobulate · 1 month ago