Article

PhpStorm PHPUnit Setup

Run PHPUnit from PhpStorm using the project’s Composer-installed binary and configuration.

Prefer Composer’s PHPUnit

Use vendor/bin/phpunit (or the project’s documented script) rather than a globally installed older PHPUnit. Point PhpStorm’s test framework configuration at the project autoload and phpunit.xml / phpunit.xml.dist.

Working directory and bootstrap

Set the working directory to the Composer root so relative paths in configuration files resolve. If bootstrap files assume a web SAPI, keep those assumptions out of unit tests or document the required env vars.

Debugging tests

Attach Xdebug to the same interpreter used for PHPUnit. Start with a single test method before enabling coverage or parallel runners that complicate path mapping.

CI parity

Mirror PhpStorm’s command in Composer scripts so CI remains authoritative. The IDE should be a convenience launcher, not a second unofficial test definition.

Verification and maintenance

PhpStorm PHPUnit Setup was reviewed for this seed on 2026-08-09. Confirm current releases and extension publishers through PHPUnit Documentation before adopting recommendations.

Related tools

Related reading