Skip to content
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

Coverage raising inexistent fatal errors in normal run #490

Closed
antonioribeiro opened this issue Nov 30, 2016 · 2 comments
Closed

Coverage raising inexistent fatal errors in normal run #490

antonioribeiro opened this issue Nov 30, 2016 · 2 comments

Comments

@antonioribeiro
Copy link

As you can see in the image, turning coverage on raises a "PHP Fatal error" a normal phpunit run is not showing:

image

Here's my xml:

<?xml version="1.0" encoding="UTF-8"?>
<phpunit backupGlobals="false"
         backupStaticAttributes="false"
         bootstrap="tests/phpunit/bootstrap.php"
         colors="true"
         convertErrorsToExceptions="true"
         convertNoticesToExceptions="true"
         convertWarningsToExceptions="true"
         processIsolation="false"
         stopOnError="false"
         stopOnFailure="false"
         syntaxCheck="true"
         verbose="true"
>
    <testsuites>
        <testsuite name="Laravel Test Suite">
            <directory suffix="Test.php">./tests/phpunit</directory>
        </testsuite>
    </testsuites>
    <filter>
        <whitelist processUncoveredFilesFromWhitelist="true">
            <directory suffix=".php">./src</directory>
            <exclude></exclude>
        </whitelist>
    </filter>
    <php>
        <!--
        <env name="REDIS_HOST" value="127.0.0.1" />
        <env name="REDIS_PORT" value="6379" />
        -->
    </php>
</phpunit>

@antonioribeiro antonioribeiro changed the title Code coverage raising unknown fatal errors Code coverage raising inexistent fatal errors in normal run Nov 30, 2016
@antonioribeiro antonioribeiro changed the title Code coverage raising inexistent fatal errors in normal run Coverage raising inexistent fatal errors in normal run Nov 30, 2016
@sebastianbergmann
Copy link
Owner

Thank you for your report.

Please provide a minimal, self-contained, reproducing test case that shows the problem you are reporting.

Without such a minimal, self-contained, reproducing test case I will not be able to investigate this issue.

@antonioribeiro
Copy link
Author

antonioribeiro commented Dec 1, 2016

It's happening on this package: https://github.com/antonioribeiro/health

It is self-contained, but is this minimal enough?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants