PHPstorm PHPunit code co coverage

Question

When I run my test suite in PHPstorm, the code coverage comes back with 0% for everything (which I know is not true), and when I run PHPunit from the command line, the logged HTML output documents show that I actually DO have coverage and lists all the detailed information.

In PHPstorm, I have my PHP interpreter set to /usr/local/bin/php (PHP 5.6.7) and xdebug 2.3.2 (screenshot: https://dl.dropboxusercontent.com/u/379071/Screen%20Shot%202015-04-20%20at%206.57.39%20PM.png). In my PHPunit preferences, I have the 'path to script' set to my composer autoload.php file. In my runtime configuration, I have a PHPunit runtime set to run with a 'defined configuration file' (See below). When I run, all the tests run and pass (a failure shows a stack trace), but the code coverage is completely zero for everything.

Any help would be greatly appreciated. I'm sure I've just missed something.

Contents of my XML configuration file:

<?xml version="1.0" encoding="UTF-8"?>
<phpunit bootstrap="./tests/bootstrap.php"
         colors="true">
    <testsuites>
        <testsuite>
            <directory>tests</directory>
        </testsuite>
    </testsuites>
    <filter>
        <whitelist>
            <directory suffix=".php">src</directory>
        </whitelist>
    </filter>
    <logging>
        <log type="coverage-html" target="./log/codeCoverage" charset="UTF-8"
             yui="true" highlight="true"
             lowUpperBound="50" highLowerBound="80"/>
        <log type="testdox-html" target="./log/testdox.html"/>
    </logging>
</phpunit>

Most likely you are using symbolic links or your code is outside of the project and IDE is unable to match file names produced by xdebug to project files. — LazyOne
– LazyOne, Commented Apr 21, 2015 at 8:56
So how did you actually fix this issue? I'm having the same problem. — AgmLauncher
– AgmLauncher, Commented Aug 4, 2015 at 18:30

Daniel Ness · Accepted Answer · 2016-04-29 23:57:26Z

5

I know this is an old thread but I just encountered this issue. In my case the project path contained a symlink to a different hd. By changing the project root to the absolute path (/media/hdd/...) I was able to resolve the problem.

answered Apr 29, 2016 at 23:57

Daniel Ness

662 silver badges3 bronze badges

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

1 Comment

alex-phillips Over a year ago

Turns out the same issue was with me - it was a symlink (same HDD, but a symlink nonetheless).

funivan · Accepted Answer · 2015-04-21 11:20:51Z

-2

Possible you just run tests without code coverage in phpstorm. You can invoke Run with coverage action. I have similar configurations and all works fine.

enter image description here

answered Apr 21, 2015 at 11:20

funivan

3,4631 gold badge18 silver badges20 bronze badges

2 Comments

alex-phillips Over a year ago

I made sure I was running with coverage - same issue. The 'coverage summary' side pane even opens up after the operation is complete.

funivan Over a year ago

My filter configuration. Possible add slash at the end <filter> <whitelist> <directory suffix=".php">src/</directory> </whitelist> </filter>

Collectives™ on Stack Overflow

PHPstorm PHPunit code co coverage

2 Answers 2

1 Comment

2 Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

1 Comment

2 Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related