Skip to content
Discussion options

You must be logged in to vote

This issue has been fixed in recent versions.

Root cause: The extension previously wrote the coverage clover XML file to /tmp/ inside the Docker container. Since /tmp is not part of the volume mount, the host (VS Code) could not read the generated clover file, so coverage results never appeared in the UI.

Fix: In PR #370, the clover file path was changed from /tmp to ${workspaceFolder}/.phpunit.cache/. Because Laravel Sail mounts ${workspaceFolder} to /var/www/html inside the container, and phpunit.paths maps between them, the clover file is now written to a location accessible from both the Docker container and the host.

Please update to the latest version and try again. Your existing co…

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by andriawan
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants