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

Question

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:

PHPUnit\Framework\Exception: Fatal error: Uncaught SebastianBergmann\CodeCoverage\NoCodeCoverageDriverAvailableException: 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): SebastianBergmann\CodeCoverage\Driver\Selector->forLineCoverage(Object(SebastianBergmann\CodeCoverage\Filter))
   ├ #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.

Derick · Accepted Answer · 2021-07-27 11:37:22Z

2

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.

edited Jul 27, 2021 at 11:37

answered Jul 27, 2021 at 9:30

Derick

36.9k7 gold badges82 silver badges104 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Théo Benoit Over a year ago

Hello @Derick, thanks for your answer. Yes you might be right. It might be because PHP is not the same. When i run php -v I have the php with xDebug, but when i run which php, i get the path to the php, and this php -v doesn't have xDebug. php: aliased to /Applications/MAMP/bin/php/php7.4.9/bin/php -c "/Library/Application Support/appsolute/MAMP PRO/conf/php7.4.9.ini"

Théo Benoit Over a year ago

By the way, If i just run ./vendor/bin/phpunit I have "no code driver" but If i do php ./vendor/bin/phpunit it's fine. It may come from here

Paflow · Accepted Answer · 2022-01-21 17:05:42Z

0

I could fix the very same problem by disabling force break when there are no mappings, a setting in the IDE under xdebug-settings.

See: https://intellij-support.jetbrains.com/hc/en-us/community/posts/360009770579-Docker-debug-problem-Remote-file-path-home-www-Standard-input-code-is-not-mapped-to-any-file-path-in-project-

answered Jan 21, 2022 at 17:05

Paflow

2,3975 gold badges34 silver badges58 bronze badges

Collectives™ on Stack Overflow

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

2 Answers 2

2 Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

2 Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related