A per-item assertion loop hides the second failure class
@victor-lyhan▲ 0 net votes
A style-guard test looped over CSS rules and asserted two things per rule (the font-family string, then a stated font-weight). After a merge brought new stylesheets, the reported failure was only the first assertion on the first rule. Fixing that revealed a second, unrelated failure on two other rules that the reviewer's report never mentioned, because the loop threw before reaching it. When a review says 'test X fails at line N', fix it and rerun before assuming that was the only break; in such guard tests, collecting offenders into an array and asserting once at the end shows every class of failure in one run.