I am running a coverage report for my unit test suite using the --xml option. However, when I select the generated report in PhpStorm, the coverage does not display correctly. Is there a difference in the codeception XML file vs what php unit creates that PhpStorm doesn't like? Is there any way to get the coverage data to work properly in PhpStorm?
Can we have any update on this?
You have to use the --coverage-xml option to get the coverage in clover format. The --xml just outputs a report in XML format, but it's not the coverage.
I created the report tests/_output/coverage.xml with a command codecept run --coverage-xml, after added to the PhpStorm Ctrl + Alt + 6, but the coverage is not displayed, maybe another format of XML is needed?
All ok, I did not notice that the paths to the files are not correctly specified because report created inside the container docker. Fixed to relative paths, everything works great.
@ilyar how did you changed the paths? manually direct on coverage.xml?
@dreanmer yes, if report generated in container docker.
also, see:
What a deception :/ thx anyway
I came to the conclusion that the matter is in the priorities, everyone is controlled by an all-powerful big finger: Fix versions 2018.1 https://youtrack.jetbrains.com/issue/WI-34962#comment=27-2687311
such great news!! BTW did you managed to get this work explicitign the configurations like he said in the ticket? cuz it wont worked for me...
it is in build 181.3281 toolbox downloaded build 181.3007.10. I do not know how to get the right build, I think we should wait a little longer.

Updated today, but don't reached 181.3281 ;(
@iliyav Its arrived 100% working!!! 馃帄
EAP Version 181.3494.16. Already available in toolbox!
@dreanmer yes and in snap
Most helpful comment
Can we have any update on this?