When we started using PHPUnit 10, we dropped the dependency to symfony/phpunit-bridge, and added our own custom DeprecationHandler to replace it.
Quite a few parts of the Symfony code were included in the replacement, to allow BC, including the expectDeprecation() method to be used in tests to check deprecations messages are actually triggered.
In the meantime, PHPUnit evolved and in version 11.0, the expectUserDeprecationMessage() and expectUserDeprecationMessageMatches() methods were introduced with basically the same purpose.
https://github.com/sebastianbergmann/phpunit/blob/11.0.10/ChangeLog-11.0...
expectDeprecation (pun moderately intended), and replace its usage with expectUserDeprecationMessage*DeprecationHandler no longer necessaryNOTE: differently from expectDeprecation, there is no check in PHPUnit that expectUserDeprecationMessage* are only called within deprecation tests (those marked @group legacy or #[IgnoreDeprecations]). Need to be careful about this.
TBD
TBD
Postponed
11.0 🔥
phpunit
Blocked on upstream expectUserDeprecationMessage*() fails when test is run in separate process
https://github.com/sebastianbergmann/phpunit/issues/6102 is fixed upstream, so as soon as a release 11.5.33 hits the road this is actionable again