php-testing
A guide for unit and integration testing in PHP. Helps developers enforce quality standards across PHP projects.
Install
mkdir -p .claude/skills/php-testing && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/3258" && unzip -o skill.zip -d .claude/skills/php-testing && rm skill.zipInstalls to .claude/skills/php-testing
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Write unit and integration tests for PHP applications with PHPUnit and Pest. Use when writing PHPUnit unit tests or integration tests for PHP applications.Key capabilities
- →Write unit tests with PHPUnit or Pest
- →Implement integration tests
- →Create mocks for dependencies
- →Use data providers for test cases
How it works
It provides standards for structuring tests, isolating dependencies through mocking, and using data providers to ensure repeatable test execution.
Inputs & outputs
When to use php-testing
- →Write unit tests for PHP classes
- →Set up integration test suites
- →Review PHP test coverage
About this skill
PHP Testing
Priority: P1 (HIGH)
Core Rule Anchors
[BE-TEST-01]Parameterized Tests for Equivalent Cases: Prefer#[DataProvider](PHPUnit) ordataset(Pest) when methods have multiple equivalent inputs or boundary permutations. Distinct scenarios may stay separate test methods. Reviewers must not demand parameterized rewrites without a behavioral gap.[BE-TEST-02]Ban on Brittle DB Mock String Matching: Do not use string-matching mocks for raw SQL queries. Test pure domain calculations directly, or use SQLite in-memory / real DB for database repository verification.[BE-TEST-03]Ban on Shallow Assertions: Never assert onlyassertNotNull($result)without inspecting domain fields, status codes, and invariants.[BE-TEST-04]Ban on Pass-Through Interface Mocks: Repositories and service handlers must test contract compliance and error mapping. Ban 1:1 pass-through mock echoing without contract assertions.[BE-TEST-05]Bug-First Regression Lock: Every PR fixing a bug ticket or with titlefix(...)must introduce a test reproducing the defect prior to the fix.
Write Tests with PHPUnit and Pest
- Standards: Use
PHPUnit(9/10+) orPest. Organize intoUnit/,Integration/, andFeature/. Class names should extendTestCase. - TDD Workflow (
[BE-TEST-05]): Follow Red-Green-Refactor. Write failing test first, implement minimal logic, then refactor. - Fluent Assertions (
[BE-TEST-03]): UseassertSame(===) overassertEqualsto avoid type coercion. Also useassertCount()andassertMatchesRegularExpression(). Avoid shallow assertions. - Data Providers (
[BE-TEST-01]): Use#[DataProvider('statusProvider')](PHPUnit 10+) ordataset(Pest). - PHPUnit Data Providers: PHPUnit data providers must use static methods and return test-case arrays.
- Mocking & Isolation (
[BE-TEST-02],[BE-TEST-04]): UsecreateMock()for dependencies; ban 1:1 pass-through mock echoing. Ensure tests are independent and repeatable. DB tests must useTransactionsorSQLite :memory:. - Coverage: Coverage is diagnostic and project-configured; verify risk-weighted critical paths rather than padding code for an arbitrary percentage.
Anti-Patterns
[BE-TEST-01]Stylistic parameterized rewrites: Do not demand data provider rewrites without a behavioral gap.[BE-TEST-02]Brittle DB mock string matching: Do not match SQL strings in mocks.[BE-TEST-03]Shallow assertions: Never assert onlyassertNotNullwithout domain payload checks.[BE-TEST-04]Pass-through mock echoing: Ban 1:1 mock echoing without contract assertions.[BE-TEST-05]Bug fix without reproduction test: Ban bug fixes without a reproduction test.- No testing private methods: Test through public interfaces only.
- No over-mocking internals: Mock only external boundaries.
- No real network/DB in unit tests: Use in-memory databases or mocks.
- No coverage-metric chasing: Prioritize meaningful assertions over arbitrary percentage metrics.
References
When not to use it
- →When testing private methods directly
- →When using real network or database connections in unit tests
Limitations
- →Requires tests to be independent and repeatable
How it compares
It enforces TDD workflows and isolation patterns that prevent common testing anti-patterns in PHP.
Compared to similar skills
php-testing side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| php-testing (this skill) | 8 | 4mo | No flags | Intermediate |
| laravel-13-facades | 0 | 6mo | No flags | Intermediate |
| php-best-practices | 15 | 4mo | No flags | Beginner |
| laravel-pdf | 11 | 6mo | Review | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by HoangNguyen0403
View all by HoangNguyen0403 →You might also like
laravel-13-facades
kooda-ai
Use when: working with Laravel 13 facades, Illuminate\Support\Facades namespace, facades vs dependency injection, facades vs helper functions, Facade base class behavior, getFacadeAccessor(), facade testing with shouldReceive(), real-time facades, Facades\ prefixes, and Laravel 13 facade code review
php-best-practices
HoangNguyen0403
PHP best practices, PSR standards, and code quality guidelines.
laravel-pdf
spatie
Generate PDFs from Blade views or HTML using spatie/laravel-pdf. Covers creating, formatting, saving, downloading, and testing PDFs with the Browsershot, Cloudflare, or DOMPDF driver.
laravel-architecture
HoangNguyen0403
Core architectural standards for scalable Laravel applications.
php-guidelines-from-spatie
freekmurze
Describes PHP and Laravel guidelines provided by Spatie. These rules result in more maintainable, and readable code.
laravel-specialist
Jeffallan
Use when building Laravel 10+ applications requiring Eloquent ORM, API resources, or queue systems. Invoke for Laravel models, Livewire components, Sanctum authentication, Horizon queues.