49cc733a03
> 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: I28312ced932898a32b53a8dfc1be12ba165c79c4 |
||
|---|---|---|
| .. | ||
| EtcdConfigTest.php | ||
| HashConfigTest.php | ||
| MultiConfigTest.php | ||
| ServiceOptionsTest.php | ||
| SiteConfigurationTest.php | ||