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.zip

Installs 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.
155 chars✓ has a “when” trigger
Intermediate

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

You give it
PHP class or service
You get back
Test suite results

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) or dataset (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 only assertNotNull($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 title fix(...) must introduce a test reproducing the defect prior to the fix.

Write Tests with PHPUnit and Pest

  • Standards: Use PHPUnit (9/10+) or Pest. Organize into Unit/, Integration/, and Feature/. Class names should extend TestCase.
  • TDD Workflow ([BE-TEST-05]): Follow Red-Green-Refactor. Write failing test first, implement minimal logic, then refactor.
  • Fluent Assertions ([BE-TEST-03]): Use assertSame (===) over assertEquals to avoid type coercion. Also use assertCount() and assertMatchesRegularExpression(). Avoid shallow assertions.
  • Data Providers ([BE-TEST-01]): Use #[DataProvider('statusProvider')] (PHPUnit 10+) or dataset (Pest).
  • PHPUnit Data Providers: PHPUnit data providers must use static methods and return test-case arrays.
  • Mocking & Isolation ([BE-TEST-02], [BE-TEST-04]): Use createMock() for dependencies; ban 1:1 pass-through mock echoing. Ensure tests are independent and repeatable. DB tests must use Transactions or SQLite :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 only assertNotNull without 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.

SkillInstallsUpdatedSafetyDifficulty
php-testing (this skill)84moNo flagsIntermediate
laravel-13-facades06moNo flagsIntermediate
php-best-practices154moNo flagsBeginner
laravel-pdf116moReviewBeginner

Try saying

Example prompts that trigger this skill in your AI assistant.

Search skills

Search the agent skills registry