-
Notifications
You must be signed in to change notification settings - Fork 121
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wrong namspace - not a PHPUnit code coverage file #333
Comments
@sebastianbergmann Any Change I should have known about? |
@sebastianbergmann: Technically speaking, that was a BC break... |
Thanks for the fix. I'm looking forward for the next release. |
Hi, the https://schema.phpunit.de/coverage/1.0 is returning error 404 nad because of that is not possible to use it. are nay other option to avoid this? |
@joaomfrebelo I don't understand your problem? It's a namespace uri, not a schema validation. (See #367 (comment)) |
@joaomfrebelo If you think the fact the namespace uri doesn't resolve is a problem/bug, open an issue with https://github.com/sebastianbergmann/php-code-coverage |
Hi,
When i use phpdox with a phpunit enricher, an exception is thrown saying "Wrong namspace - not a PHPUnit code coverage file" .
The file "src/generator/enricher/phpunit/PHPUnit.php" has a XMLNS constant which defined a "http" address. But phpunit generates xml report with a "https" value. Hence the exception.
I tried modifying the phpunit report to "http" and the enricher stop throwing the exception.
I don't know if adding "https" to the constant would have another impact.
php : 7.2.5
phpunit : 7.1.5
phpdox : 0.11.1
The text was updated successfully, but these errors were encountered: