Risky was occurred. about ci-phpunit-test HOT 6 CLOSED

How about this? 7e256d9

from ci-phpunit-test.

You are great! I should have use ob_get_level like this.
Thank you for your commit.

from ci-phpunit-test.

Output buffering of PHP is stackable.

Thank you for your report!

from ci-phpunit-test.

@kenjis I am having a same problem here, but my code is not simple as show_404 but really complicated. Do you have any advice on how to trace down the output buffering issue?

My test target method is using form_validation, ReCaptcha (third-party library) and bunch of models.

from ci-phpunit-test.

The reason PHPUnit reports risky is you have output buffer which is not cleared.
$this->request() calls ob_start().

You have to search ob_start() and make sure all of them are cleared and buffering is turned off.

from ci-phpunit-test.

@kenjis thank you, I found the reason.

There are severals call to ob_start() in core/Exceptions.php. When there is PHP Error in the application, CI render the error template and somehow mess around with the output buffering. I fixed that by fixing the error in my application code, not sure if this is a CodeIgniter's issue or should we fix it in ci-phpunit-test.

Anyway, the risky test helped me to know if there is unexpected PHP Errors in the output, so I find it helpful in an unexpected way.

from ci-phpunit-test.