Clarify deprecation handling in the PhpUnitBridge #7312
Labels
actionable
Clear and specific issues ready for anyone to take them.
bug
good first issue
Ideal for your first contribution! (some Symfony experience may be required)
hasPR
A Pull Request has already been submitted for this issue.
PHPUnitBridge
Status: Needs Review
In https://symfony.com/doc/current/components/phpunit_bridge.html#mark-tests-as-legacy we say that there are four ways to declare a test as legacy:
However, this is not true. Prefix the name of a data provider method with
provideLegacy
orgetLegacy
does not influence the error handling of the test method, but is only useful if your data provider actually triggers deprecations.The text was updated successfully, but these errors were encountered: