Testing
Drupal 10 ships with three PHPUnit test types: Unit (no Drupal), Kernel (real services, no browser), and Functional (full browser via BrowserKit). Each type makes different trade-offs between speed and coverage depth. This guide explains when to use each and how to write effective tests for custom modules. Key Takeaways
Testing
WordPress plugin unit tests don't need a running WordPress install. WP_Mock and Brain\Monkey let you mock WordPress functions, hooks, and globals so your PHPUnit tests run in isolation — fast, deterministic, and CI-friendly. This guide shows how to set up both tools and write meaningful tests for
PHP
Code coverage is one of those metrics that developers either obsess over or dismiss entirely. The truth sits between those extremes: coverage data is genuinely useful for finding untested code paths, but a 90% coverage number tells you nothing about whether those tests are actually meaningful. Understanding what coverage measures
PHP
Infection is the leading mutation testing framework for PHP. It operates on the Abstract Syntax Tree (AST) level — generating mutants by altering your source code according to predefined mutation operators — then running your test suite against each change. A test suite that kills 80%+ of mutants provides much stronger behavioral
Tools & Frameworks
Most PHP projects end up with three separate testing tools: PHPUnit for unit tests, something else for HTTP integration, and a browser automation library bolted on for end-to-end scenarios. Each tool has its own configuration format, its own runner, and its own reporting conventions. Codeception was built to fix exactly
Tools & Frameworks
PHPUnit is the standard PHP testing framework. Pest is a modern alternative that wraps PHPUnit with a cleaner functional syntax. Both produce identical test results — the difference is entirely how you write tests. Pest is Laravel's default since v11. PHPUnit is the safe choice everywhere else. Key Takeaways
Integration Testing
Integration tests verify that PHP components work together: your service classes with a real database, your HTTP controllers with real routing, your external API clients against real or stubbed endpoints. This guide covers database integration testing with transactions, HTTP layer testing, testing with real queues and caches, and integrating with
Tools & Frameworks
Mockery is PHP's most powerful mocking library, popular in Laravel and Symfony ecosystems. It provides a fluent API for creating test doubles: mocks, stubs, spies, and partial mocks. This guide covers creating mocks, defining expectations with shouldReceive, argument matchers, mock verification, spies, and using Mockery with PHPUnit and
Tools & Frameworks
Pest is a modern PHP testing framework built on top of PHPUnit. It offers a simpler, more expressive syntax with test(), it(), and expect() — inspired by Jest and RSpec. Pest is Laravel's default testing framework since Laravel 11. This guide covers setup, writing tests, datasets, architecture testing, and
Tools & Frameworks
Laravel ships with a complete testing setup: PHPUnit configured, database factories, HTTP test helpers, and Artisan commands to generate tests. Feature tests let you make real HTTP requests to your application without a running server. This guide covers unit tests, feature tests, database testing, facade mocking, queue/event faking, and
Tools & Frameworks
PHPUnit is the standard testing framework for PHP. Every major PHP framework — Laravel, Symfony, WordPress — uses or supports PHPUnit. This guide covers installation, writing test classes, assertions, test doubles (mocks, stubs, spies), data providers, exception testing, code coverage, and CI integration. Key Takeaways PHPUnit test classes extend TestCase and methods