3 ms·

If you're looking for an article with substance and a similar bent (functional specifications driving decisions on test granularity), I'd try this one: https:/

• benterix 3y ago
  This one is much more substantial and the author has some excellent points like the futility of aiming at 100% coverage.
  • h0l0cube 3y ago
    My favorite hot take from that article is that if a functional test can't exercise a piece of code, delete it. That is, if the code can't be exercised in normal usage of your program, it serves no purpose. One retort might be that sometimes code defends against malicious actors who, say, have direct access to private endpoints etc., but if you're defending against such threats, either that requirement drives your functional spec (e.g. banking infrastructure) or maybe you're taking things a little too far.
    • fefe23 3y ago
      That does sound like an intriguing way to think about the issue. Thanks for pointing it out to me!