If you install #PHPUnit using Composer (which is not the recommended way) then you can now use both PHPUnit 9.6 and PHPUnit 10.5 in projects that depend on either PHP-Parser 4 or PHP-Parser 5.
To everyone who does not already sponsor my #OpenSource work: please consider to do so! If you benefit from using PHPUnit, then it is in your best interest that I am able to continue to work on #PHPUnit.
Adding some tests to a legacy PHP project. Much more challenging than with a brand new codebase, also building the infrastructure is harder when test frameworks assume you're using PSR-4 autoloading etc. I think the payoff is worth it though as it's helping to ensure that a patch to fix an edge case (roughly 1% of records) actually works without regressions.
Two months from now, on February 2, 2024, #PHPUnit 11 will be release.
PHPUnit 11 is the annual major release for 2024 that removes deprecated functionality and lays the foundation for delivering features and improvements throughout the year in PHPUnit 11.1 (April), PHPUnit 11.2 (June), PHPUnit 11.3 (August), PHPUnit 11.4 (October), and PHPUnit 11.5 (December).
Tip: Do not use testdox="true" on #phpunit 10 with #TYPO3 functional tests: bootstrap errors, like DI failures, are then not displayed in detail anymore (just the "E").
ugh, trying for days now to find out why my phpunit tests do not provide coverage for #sonarcloud
Slowly getting the feeling I managed to create a special case of phpunit config, which makes matching the code for the coverage not working in special circumstances.
but running it local with identic versions does work 🙄 #php