Skip to content

Do not document deprecated legacy test mechanisms #7324

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Apr 24, 2017
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 2 additions & 9 deletions components/phpunit_bridge.rst
Original file line number Diff line number Diff line change
Expand Up @@ -74,15 +74,8 @@ in the **Unsilenced** section of the deprecation report.
Mark Tests 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*()``.
Add the ``@group legacy`` annotation to a test class or method to mark it
as legacy.

Configuration
-------------
Expand Down