diff options
author | Timo Tijhof <krinkle@fastmail.com> | 2023-07-24 05:29:29 +0100 |
---|---|---|
committer | Krinkle <krinkle@fastmail.com> | 2023-07-24 20:35:53 +0000 |
commit | ace8eb018feebe8774d9dfdc121e77feba4ca9b7 (patch) | |
tree | f8eef40ca83847d53ec9903fdcd156dee0dcdc7f /tests/phpunit/includes/diff | |
parent | e8e7cb2d9388b5aa1e772540b42c7773f8ce1091 (diff) | |
download | mediawikicore-ace8eb018feebe8774d9dfdc121e77feba4ca9b7.tar.gz mediawikicore-ace8eb018feebe8774d9dfdc121e77feba4ca9b7.zip |
skins: Widen `@covers` annotations in unit tests
Follows-up I7555c9b6b510, I6d845bdfbb80, I69b5385868, I4c7d826c7e,
I1287f3979ab, which widened the `@covers` annotations of other suites:
> We lose useful coverage and spend valuable time keeping these tags
> accurate through refactors (or worse, forget to do so).
>
> I've audited each test to confirm it is a general test of the
> subject class, where adding any called methods would be an accepted
> change, thus widening it is merely a no-op that clarifies intent
> and reduces maintenance. I am not disabling the "only track coverage
> of specified subject" benefits, nor am I claiming coverage in
> in classes outside the subject under test.
>
> Tracking tiny details per-method wastes time in keeping references
> in sync during refactors, time to realize (and fix) when people
> inevitably don't keep them in sync, time lost in finding uncovered
> code to write tests for only to realize it was already covered but
> not yet claimed, etc.
Change-Id: I98d2ecc9870d893845c14e09b15fa19f4f258250
Diffstat (limited to 'tests/phpunit/includes/diff')
0 files changed, 0 insertions, 0 deletions