Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Clarify deprecation handling in the PhpUnitBridge #7312

Closed
Labels
PHPUnitBridgeStatus: Needs ReviewactionableClear and specific issues ready for anyone to take them.buggood first issueIdeal for your first contribution! (some Symfony experience may be required)hasPRA Pull Request has already been submitted for this issue.
@xabbuh

Description

@xabbuh

Inhttps://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:

There are four ways to mark a test as legacy:

  • (Recommended) Add the@group legacy annotation to its class or method;
  • Make its class name start with the Legacy prefix;
  • Make its method name start with testLegacy instead of test;
  • Make its data provider start with provideLegacy or getLegacy.

However, this is not true. Prefix the name of a data provider method withprovideLegacy orgetLegacy does not influence the error handling of the test method, but is only useful if your data provider actually triggers deprecations.

Metadata

Metadata

Assignees

No one assigned

    Labels

    PHPUnitBridgeStatus: Needs ReviewactionableClear and specific issues ready for anyone to take them.buggood first issueIdeal for your first contribution! (some Symfony experience may be required)hasPRA Pull Request has already been submitted for this issue.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions


      [8]ページ先頭

      ©2009-2025 Movatter.jp