2 ms·
If it seems like a poor argument against testing, that's because it's not meant to be one! It's meant to be an argument against the notion that "production code
by the_af 9y ago
If it seems like a poor argument against testing, that's because it's not meant to be one! It's meant to be an argument against the notion that "production code tests the tests". It's also an argument for making sure your tests are effective.
> Naturally, if you write bad tests then they won't be effective
But how can you tell if your tests are effective, i.e. if you wrote "good tests"? Production code alone is not enough; you cannot tell if a test is green because everything is ok or because it's buggy/incomplete. You must introduce some degree of quality control in your test code.