This new release comes thanks to a new contributor: thanks @raffaelecarelle! He contributed the support of two native PHPUnit options with a single pull request: --exclude-testsuite and --test-suffix. Both these options allow the user to filter and exclude tests from the execution. This is the full changelog Added --exclude-testsuite option #273, thanks @raffaelecarelle --test-suffix option #273, thanks @raffaelecarelle
This small patch release is fully due to external contributions: thanks @kubawerlos! He contributed two different patches, one to update the .gitattributes exclusion list, the second to fix some constraint on some dependencies that where preventing PHPUnit 11.3 from being installed. This is the full changelog Fix PHPUnit 11.3 compat #260, thanks @kubawerlos Reduce package footprint by updating .gitattributes #261, thanks @kubawerlos
I got a bug report saying that the Symfony PHPUnit Bridge 6.4.8 and 7.0.8 and higher made test runs with Paraunit fail due to a warning. At first I thought that the Symfony error handler was messing with PHPUnit’s again, but in reality it was just making explicit a warning that was already there for ages. This simple patch avoids generating that warning, and makes your CI green again! This is the full changelog
I noticed that, since Paraunit 2, the recap at the end of the execution got very long. This was due to an improper serialization of the logs, where the test name was treated as a generic Test value object instead of a specific TestMethod one, where the class name is shown split form the method name. This had the unintended consequence of not deduplicating the list of files which are printed at the end of Paraunit’s execution, so in case an error or failure was repeated many times (i.
I may have jumped the gun while releasing the PHPUnit 11 compat, and I didn’t check that the CI was actually installing it. Unfortunately there were multiple dependencies still conflicting with it, and Prophecy needed some PRs to be compatible. I filed them and used them in my CI, so that now the compatibility is checked. I needed to do multiple changes to make the CI green, but still no code changes was needed, only a widening of composer.