Problem/Motivation
During the annotation-to-attribute test metadata migration, we converted no longer supported @covers annotations to @legacy-covers.
Proposed resolution
On class level metadata, we can map @legacy-covers to #[CoversClass], #[CoversMethod], #[CoversFunction], #[CoversTrait] attributes.
In this issue target Unit, Functional, FunctionalJavascript and Build tests. In a follow up, target Kernel tests (that are not yet converted to test attributes).
Remaining tasks
User interface changes
Introduced terminology
API changes
Data model changes
Release notes snippet
Comments
Comment #2
mondrakeComment #3
mondrakeComment #5
mondrakeComment #6
mondrakeComment #7
mstrelan commentedLooked at the first two files, aren't we losing some annotations that haven't been converted yet here?
Comment #8
mondrake#7 done, thanks!
Comment #9
needs-review-queue-bot commentedThe Needs Review Queue Bot tested this issue. It no longer applies to Drupal core. Therefore, this issue status is now "Needs work".
This does not mean that the patch necessarily needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.
Consult the Drupal Contributor Guide to find step-by-step guides for working with issues.
Comment #10
mondrakerebased
Comment #11
mstrelan commentedCan confirm my concerns in #7 have been addressed. Have read through the MR and confirmed a one-to-one mapping of annotation to attributes here.
Comment #12
catchThis looks good, nice that we can get rid of @legacy-covers again pretty easily.
Committed/pushed to 11.x, thanks!
Comment #16
mondrakeon class level, yes; on method level, it's a challenge.