phpunit - Help needed about risky tests

Question

i'm implementing some tests for a site. In a particular test, this result occurred:

{
"event": "test",
"suite": "Example_V_test",
"test": "Example_V_test::test_3",
"status": "error",
"time": 13.469105958939,
"trace": [
    {
        "file": "\/opt\/lampp\/htdocs\/buy\/application\/tests\/phpunit.phar",
        "line": 569,
        "function": "main",
        "class": "PHPUnit_TextUI_Command",
        "type": "::"
    }
],
"message": "Risky Test: Test code or tested code did not (only) close its own output buffers",
"output": ""
}R                                                                 3 / 3 (100%)

Time: 25.76 seconds, Memory: 59.25MB

There was 1 risky test:

1) Example_V_test::test_3
Test code or tested code did not (only) close its own output buffers

/opt/lampp/htdocs/buy/application/tests/phpunit.phar:569

OK, but incomplete, skipped, or risky tests!

My question is this: how to find the line of code that cause this 'issue'?

Where can I find the error log? I'm testing a site built with codeigniter and i didn't find it in the directory that contains the phpunit.phar file, i.e.:/opt/lampp/htdocs/codeigniter/application/tests . Also, i look in the codeigniter/application/log folder and here it's no output from phpunit testing. — bobc82
I understand. In my case it's the /opt/lampp/logs/error.log file, but there is no output from phpunit test... — bobc82

JSchirrmacher JSchirrmacher · Accepted Answer · 2016-07-19T12:32:25

The message is reported if PHPUnit detects that the output buffering level at the end of a test method is different from the level at the beginning. This is due to the fact that it uses its own output buffer and checks that the test produces no output.

Because there is no option in PHPUnit to ignore this, you need to find the reason why the output buffering in your code was started but not ended (or ended too much) and fix that.

That might be really difficult to achieve because there is no hint, where output buffering is started, but you could use a full-text search on your source code (and libs) to identify candidates. Then look for Exceptions, which might break the normal program flow and so prevent ob_end_flush() (or similar) to be called.

phpunit - Help needed about risky tests

1 Answers