Only remove @covers when target exists

[samsonasik]

@TimelessTron this should ensure only remove when attribute group added.

Ref rectorphp/rector#9183 (comment)

[samsonasik]

It seems cause phpunit notice:

https://github.com/rectorphp/rector-phpunit/actions/runs/15180236245/job/42688052509?pr=494#step:5:35

@TimelessTron could you verify the use of @covers ::__construct on class level is correct, if no, we can just remove it as it won't be changed to attribute anyway

[samsonasik]

Let's remove @covers ::__construct on class level, it should be on method if needed.

[samsonasik]

@TimelessTron I tested manually on phpunit 10, and it seems still remove whole @covers

+     #[\PHPUnit\Framework\Attributes\CoversClass(\App\SomeException::class)]
      final class SomeTraitTest extends TestCase
      {
-        /**
-         * @covers \App\OtherStuff::Inject
-         * @covers \App\SomeException
-         */
-         public function testYourThinks(): void
+        public function testYourThinks(): void
          {}

[samsonasik]

this one seems can cover it, I am thinking of moving CoversTrait and CoversMethod to phpunit 11 rule tho, but that will be need in separate PR

[samsonasik]

I rolled back remove @covers ::__construct on class level to avoid regression 7da389b

[samsonasik]

Let's merge so we have faster feedback.

[samsonasik]

Github status is delay https://www.githubstatus.com/