Skip to content
Advertisement

PHPUnit can’t generate code coverage when running tests in separate processes

I have a problem that I could not find the solution on Google. When I run my unit tests with PHPUnit and Xdebug, I would like to do a code coverage.

However, when I do that, I get this error:

PHPUnitFrameworkException: Fatal error: Uncaught SebastianBergmannCodeCoverageNoCodeCoverageDriverAvailableException: No code coverage driver available in /Users/theobenoit/Desktop/Antipode.nosync/Sites/wp-framework-core/vendor/phpunit/php-code-coverage/src/Driver/Selector.php:53
   ├ Stack trace:
   ├ #0 Standard input code(43): SebastianBergmannCodeCoverageDriverSelector->forLineCoverage(Object(SebastianBergmannCodeCoverageFilter))
   ├ #1 Standard input code(123): __phpunit_run_isolated_test()
   ├ #2 {main}
   ├   thrown in /Users/theobenoit/Desktop/Antipode.nosync/Sites/wp-framework-core/vendor/phpunit/php-code-coverage/src/Driver/Selector.php on line 53

I realized that this is because in some of my tests there is this at the top:

/**
 * @runTestsInSeparateProcesses
 * @preserveGlobalState disabled
 */

When I remove @runTestsInSeparateProcesses everything works fine, but there are problems because I mock functions.

If anyone has ever had this problem.

Advertisement

Answer

This is likely because with runTestsInSeparateProcesses, PHPUnit starts a new PHP process for every test. And it seems that it does that without Xdebug loaded.

The PHP that is started for each test needs to be the same as the one that you originally started PHPUnit with. Perhaps there is a different PHP binary first in the PATH?

If that is the case, the way to solve it is to make sure the “right” PHP is first in the PATH.

User contributions licensed under: CC BY-SA
9 People found this is helpful
Advertisement