Errors in after-last-test methods are not reported

[jocutajar]

after class exceptions are just swallowed and you need the debugger to understand what is going on

Originally posted by @BafS in 258e4e9

[sebastianbergmann]

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.

[BafS]

Tested with PHPUnit 11 but it should be the same with v10

in tests/A.php

<?php

class ATest extends \PHPUnit\Framework\TestCase
{
    public static function tearDownAfterClass(): void {
        echo PHP_EOL . 'THIS SHOULD FAIL' . PHP_EOL;
        throw new \Exception('A-FAIL');
    }

    public function testA(): void {
        self::assertTrue(true);
    }
}

Run it:

./vendor/bin/phpunit tests/ATest.php
PHPUnit 11.5.2 by Sebastian Bergmann and contributors.

Runtime:       PHP 8.3.14

.                                                                   1 / 1 (100%)
THIS SHOULD FAIL


Time: 00:00.006, Memory: 6.00 MB

OK (1 test, 1 assertion)

It's eaten by the empty catch(), there is no message, no failure.

[BafS]

Thank you!

[noefleury]

When updating my codebase packages today I've suddenly got some strange issue coming from the tearDownAfterClass method.

After a lot of investigation I've finally found that the error came from phpunit and more precisely the 11.5.3 version.

Changes from this minor : 11.5.2...11.5.3.

I've finally found the exact reasons : 15a2f3e / d2be391 / a7dbfad.

→ A non-impactful error was silently thrown on my side and finally got correctly caught by these changes.

Thank you for your work.

---

Hope this comment will help someone with debugging.