Tag: PHPUnit

1. Understanding Magento Fixtures in Integration Tests

   Dec 16, 2025

   Without clean fixtures, integration tests are fragile: tests create test data that affects the next test, rollbacks fail and the fixture script sits at a different path than expected. The Magento Test Framework offers a sophisticated fixture system, provided you understand the mechanisms behind it.

   Read more

2. Connecting Xdebug and PHPUnit in Docker with PhpStorm the Right Way

   Dec 15, 2025

   Debugging PHPUnit tests in a Docker environment with PhpStorm is one of the most frustrating parts of PHP development. Configuration usually fails because of XDEBUG_MODE, incorrect path mapping, or a remote interpreter that was never set up correctly. This guide shows the complete path, from installing Xdebug to running coverage reports.

   Read more

3. Integrating PHPUnit into GitLab CI and GitHub Actions

   Dec 3, 2025

   Tests that only ever run locally do not protect a project. Only integration into CI/CD turns test automation into a quality gate: every pull request is checked automatically, coverage reports are stored as artifacts, and failures are reported where they happen, in the code, not first at deploy time. This article shows the complete CI/CD integration of PHPUnit for both major platforms.

   Read more

4. PHPUnit 11: What Changed and What Teams Need to Adjust

   Nov 28, 2025

   PHPUnit 11 is not an incremental update. It removes docblock annotations in favor of native PHP attributes, tightens coverage configuration, fundamentally changes the mock system, and sets PHP 8.1 as the minimum requirement. Anyone migrating has to change more than just the version number in composer.json.

   Read more

5. Reading PHPUnit Coverage Correctly: Signal, Not a Vanity Metric

   Nov 24, 2025

   80% line coverage sounds good. But line coverage says nothing about whether the right cases are being tested. A branch that gets executed for one particular input counts as covered, no matter whether the other branch is ever tested. Coverage is a tool, not a goal. Anyone who treats it as a vanity metric ends up optimizing the number instead of the quality.

   Read more

6. 50 PHPUnit Patterns for Productive PHP and Magento Projects

   Nov 23, 2025

   Anyone who writes tests without a clear pattern ends up with a test suite that is slow, brittle and hard to understand. Data providers, meaningful assertions, isolated mocks and a sensible coverage strategy separate tests that immediately catch a refactoring mistake from green tests that stay green despite bugs.

   Read more

7. Making PHPUnit Coverage and Xdebug Usable for Large Magento Projects

   Nov 17, 2025

   Code coverage sounds like a simple concept, but it quickly becomes a bottleneck in large Magento 2 projects: Xdebug slows the test suite down by a factor of five to ten, reports become huge, and without proper configuration you end up measuring the wrong thing. PCOV, targeted whitelist configuration and CI thresholds turn coverage into a useful tool instead of a bottleneck.

   Read more

8. PHPUnit: Testing Filesystem and IO Code Without Fragile Tests

   Nov 7, 2025

   Filesystem operations are among the most frequently untested parts of PHP applications. Anyone who calls file_get_contents() and file_put_contents() directly ends up writing code that either doesn't get tested at all, or leaves behind tests that create real files, have order dependencies, and break when run in parallel. vfsStream, stream wrappers and filesystem abstraction solve this problem at its root.

   Read more

9. Testing Exceptions in PHPUnit Correctly

   Oct 26, 2025

   Anyone who does not deliberately test exceptions leaves error handling unverified, which is the most dangerous blind spot in a PHP test suite. PHPUnit provides precise methods to ensure that the correct exception type, the right message, and the correct error code are actually raised.

   Read more

10. PHPUnit Golden Master Tests for Refactorings

    Oct 21, 2025

    Anyone who wants to refactor legacy code without tests faces a chicken-and-egg problem: writing tests requires understanding the code, understanding requires reading the code, but confidence when changing it requires tests. Golden Master tests untangle this knot, they test the behavior before it is understood.

    Read more