3 ms·

Not to mention you have 2^100 states of on/off (~1.2676506e+30)

• hinkley 8y ago
  I work on that project. Every time some idiot starts talking about 'code coverage' my face turns red. Our code coverage is 1e-10%. Don't talk to me about this 70% bullshit.
  • inetknght 8y ago
    Said with less vitriol: It's not just code coverage that matters. It's the code path selection that matters. If you have a ton of branches and you've evaluated all of them once then yeah you sure might have 100% "coverage". But you have 0% path selection coverage since a single invokation of your API might choose true branch on one statement, false branch on another statement, and a second invokation might choose false branch on the first and true on the second. While the code was 100% tested, the scenarios were not. What happens if you have true/true or false/false? That's not tested. There's a term for this but I forgot what it is and don't care to go spelunking to find it.
    • piaste 8y ago
      > There's a term for this but I forgot what it is and don't care to go spelunking to find it. Happy path?
      • inetknght 8y ago
        Not quite what I meant, but that's another good description
    • mosheroperandi 8y ago
      > There's a term for this but I forgot what it is and don't care to go spelunking to find it. sqlite calls this "branch coverage" https://www.sqlite.org/testing.html#statement_versus_branch_coverage https://www.sqlite.org/testing.html#statement_versus_branch_...