I haven’t really been paying much attention to the @covers/@uses annotations when changing the tests, and by now I suspect a lot of them are out of date: there are probably @uses annotations for classes that aren’t actually used anymore, as well as plenty of missing @uses annotations.
I’m not sure how to systematically fix this, because it seems adding --strict-coverage has no effect, at least not for the way I usually run the tests.
it seems adding --strict-coverage has no effect
I guess that flag only has effect when generating coverage reports (which makes sense, I suppose). When using the phpunit.xml.dist file in the repository (see the instructions in the README), strict coverage seems to work fine, and reports loads of tests as risky.
If you as me, you should simply remove all @uses tags. From my experience they are of limited use, add awful clutter to the tests headers, nobody tracks and updates them properly, and they become outdated way to fast. Just make sure a test @covers exactly the one (maybe two or three) classes it should cover, and verify this via a coverage report.
Change 400694 had a related patch set uploaded (by Ladsgroup; owner: Amir Sarabadani):
[mediawiki/extensions/WikibaseQualityConstraints@master] Remove @uses tags
Change 400694 merged by jenkins-bot:
[mediawiki/extensions/WikibaseQualityConstraints@master] Remove @uses tags
Change 401563 had a related patch set uploaded (by Ladsgroup; owner: Amir Sarabadani):
[mediawiki/extensions/WikibaseQualityConstraints@master] Remove the starting slash from @covers tags
Change 401568 had a related patch set uploaded (by Lucas Werkmeister (WMDE); owner: Lucas Werkmeister (WMDE)):
[mediawiki/extensions/WikibaseQualityConstraints@master] Remove @uses from README.md
Change 401568 merged by jenkins-bot:
[mediawiki/extensions/WikibaseQualityConstraints@master] Remove @uses from README.md
Change 401563 merged by jenkins-bot:
[mediawiki/extensions/WikibaseQualityConstraints@master] Remove the starting slash from @covers tags