> We lose useful coverage and waste valuable time on keeping tags
> accurate through refactors (or worse, forget to do so).
>
> Tracking tiny per-method details wastes time in realizing (and
> fixing) when people inevitably don't keep them in sync, and time
> lost in finding uncovered code to write tests to realize it was
> already covered but "not yet claimed".
>
> Given all used methods are de-facto and liberally claimed, and
> that we keep the coverage limited to the subject class, this
> maintains the spirit and intent. PHPUnit offers a more precise
> tool when you need it (i.e. when testing legacy monster classes),
> but for well-written code, the class-wide tag suffices.
Ref https://gerrit.wikimedia.org/r/q/owner:Krinkle+is:merged+message:Widen
Change-Id: I60151a0f5a811763fe326e92a18d3dcba8082761
This doesn't alter code coverage, but it puts all the tests in
one place so we can improve them consistently.
Change-Id: I5e2124704aa8dc4b45be17d61fbc2fbd606661b9
2024-03-08 08:11:16 -05:00
Renamed from tests/phpunit/includes/htmlform/HTMLFormFieldTest.php (Browse further)
