Fixed
- The baseline generated using
--generate-baselinecontains an issue once for each time it was triggered, for instance once for each data set of a test that uses a data provider, instead of once - A baseline is not applied to the issues that are triggered in a file that is not located in the directory of the baseline, or in a directory below it, for instance when the baseline is located in
build/baseline.xmland the file insrc - When
--log-junit php://stdoutis used, orphp://stdoutis configured for the JUnit XML logfile in the XML configuration file, and the test runner prints its regular output, the test runner ends withAn error occurred inside PHPUnitafter the JUnit XML was printed: the test results are not printed, code coverage reports and the baseline are not written, and the shell exit code is255 - When
--log-junit php://stdoutis used together with--stderr, the JUnit XML is printed to the standard error stream - When no test is run,
--compactonly printsNo tests executed!and not why, for instance the PHPUnit error for the invalid data provider of the only test, or the test runner warning for a test class without tests
Learn how to install or update PHPUnit 13.4 in the documentation.
Keep up to date with PHPUnit:
- You can follow @phpunit@phpc.social to stay up to date with PHPUnit's development.
- You can subscribe to the PHPUnit Updates newsletter to receive updates about and tips for PHPUnit.