TestDox printer does not display details about exceptions raised in before-test methods

[BladeMF]

Since PHPUnit 10, exceptions that are thrown in setUp (as opposed to the actual test body) are not displayed although the test is marked as "E", forcing you to write your own try/catch and see what they are. Since setting up is part of the test I don't think why it should be treated differently. Saying there was an error but not explaining what the error was is most unhelpful.

[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.

[BladeMF]

There - https://github.com/BladeMF/phpunit-setup-exception. The interesting bit - the --testdox needs to be on.

Case 1 - A throw in the test body

command

'/var/www/test-repo2/vendor/bin/phpunit' --colors=always --filter 'test_something_with_error' --testdox --display-deprecations --display-errors '/var/www/test-repo2/tests/MyTestWithNormalThrows.php'

output

PHPUnit 11.0.6 by Sebastian Bergmann and contributors.

Runtime:       PHP 8.2.13

E                                                                   1 / 1 (100%)

Time: 00:00.009, Memory: 8.00 MB

My Test With Normal Throws (Tests\MyTestWithNormalThrows)
 ✘ Something with error
   ┐
   ├ Exception: An error in the test!
   │
   │ /var/www/test-repo2/tests/MyTestWithNormalThrows.php:11
   ┴

Case 2 - A throw in the setUp method

command

'/var/www/test-repo2/vendor/bin/phpunit' --colors=always --filter 'test_something' --testdox --display-deprecations --display-errors '/var/www/test-repo2/tests/MyTestWithSetupThrows.php'

output

PHPUnit 11.0.6 by Sebastian Bergmann and contributors.

Runtime:       PHP 8.2.13

E                                                                   1 / 1 (100%)

Time: 00:00.011, Memory: 8.00 MB

ERRORS!
Tests: 1, Assertions: 0, Errors: 1.

[DanteB918]

@BladeMF thank you for the testing environment! after playing around with it, I have found the issue to be with the --testdox flag. As seen in my screenshots below, without this flag, the exception is being shown.

With testdox flag

Without testdox flag

[sebastianbergmann]

@DanteB918 Thank you for investigating.