Code coverage is not shown

[enjibby]

I'm having trouble articulating my issue, but it appears there is a problem parsing code coverage for my most recent Laravel project. I have a number of projects that are configured the same, save using the latest version of Laravel based on when I created them. Most projects were based on Laravel v11, but this newer one is Laravel v12. I suspect there is a compatibility issue between this extension and Pest v3 where this extension has trouble parsing coverage-clover-xml from this newer version.

I'm kind of running on N=1 and I cannot see any logging int VSCode to suggest this extension is having an issue with parsing, but I can clearly see the XML file being generated when I run in CLI, so it has to be at the parsing step or later.

Any assistance would be appreciated!

[DaDummy]

Not sure if this is your issue, but in a project of mine the extension does not parse coverage from clover xml for classes that have a namespace. (And thus are nested in a package-tag in the xml)