Mark Scherer

All apps ship with this now since 5.1: https://github.com/cakephp/app/commit/a7a23b81a6038e8aff829312fbd36954ce71f242

Actually, this seems to get triggered even without it, so this must come from our TestCase in general.

For one specific test https://github.com/laravel/framework/issues/49502#issuecomment-2790009661 seems to work But once you run multiple ones, this is not working anymore either.. What a bunch of crap with this PHPUnit majors.

I thought it mainly comes from ->disableErrorHandlerMiddleware() and the Configure::write('Error.exceptionRenderer', TestExceptionRenderer::class); we switch the error handler with it. But that itself also dosnt seem to change things. Adding restore_error_handler(); restore_exception_handler();...

https://github.com/cakephp/cakephp/compare/test-phpunit12-issues seems to fix most of it, but some seem to be left for some reason $this->post(['controller' => 'Events', 'action' => 'add'], $data); triggers it while another post() in the...

In one app this only shows up when there is an error. Then below in CI output: ``` There were 56 risky tests: 1) App\Test\TestCase\ApplicationTest::testBootstrap * Test code or tested...

Not sure whats going on, but closing for now.

Couldn't we pass those in in the construction process? What other data might be useful here?

Maybe there is a non breaking solution for 5.2 with migration guide note. Depends on the concrete solution I guess.

@LordSimal I opened a PR. You are more experienced with cells than me.