Code Coverage not working
Hi,
when i run phpunit tests with code coverage, tests are fine, .coverage files are generated, but no coverage is shown in editor nor coverage pane.
I run the same tests with the same phpunit.xml on my jenkins instance, where everything works.
This is the generated output:
/usr/local/Cellar/php72/7.2.2_13/bin/php -dxdebug.coverage_enable=1 /private/var/www/app4/vendor/bin/phpunit.phar --coverage-clover /Users/thomas/Library/Caches/PhpStorm2017.3/coverage/app4$AttachmentTest.coverage --configuration /private/var/www/app4/phpunit.xml App\Tests\Service\AttachmentTest /var/www/app4/tests/Service/AttachmentTest.php --teamcity
PHPUnit 7.0.2 by Sebastian Bergmann and contributors.
Time: 8.71 seconds, Memory: 28.00MB
OK (30 tests, 48 assertions)
Generating code coverage report in Clover XML format ... done
Process finished with exit code 0
Please sign in to leave a comment.
We would need to check logs for that. Try to reproduce that and share your idea.log (Help > Show log in...) afterward (you can use e.g. pastebin for that)
Hi Dmitry,
Thx for your help and sorry for the delay. I quit PHPStorm, deleted the old Log, start PHPStorm and done PHPUnit Tests with coverage for one controller. Here is the log: https://www.dropbox.com/s/fbfgddfvtpv5bd3/idea.log?dl=0
I use PHP 7.2.2, PHPUnit 7.0.2 and PhpStorm2017.3.
Thanks!
Could you please do that again, but first please open Help | Debug Log Settings... and add #com.jetbrains.php line?
Could you please check if coverage file is generated and can be opened (/Users/thomas/Library/Caches/PhpStorm2017.3/coverage/app4$AttachmentTest.coverage)?
Hi,
ok, I've done so. Here ist the log: https://www.dropbox.com/s/rhfuor1k5xnkurv/idea.log?dl=0
and here is the coverage file: https://www.dropbox.com/s/6jr62bl123rvv91/app4%24UserControllerTest.coverage?dl=0
Has anything ever come from this? I'm having the same issue now...
Sorry, can't find if this issue was ever addressed. Chris Vermeulen I would suggest to contact us directly via Help | Contact Support to investigate the issue closely.