6 ms·
The tragedy he mentions aren't 100% code coverage. It's more about people using the wrong tools for the job and using 100% coverage as an indication that every
by xutopia 9y ago
The tragedy he mentions aren't 100% code coverage. It's more about people using the wrong tools for the job and using 100% coverage as an indication that everything is fine.
100% coverage for my team means that we were intentional about our code. It's not hard at all to have 100% coverage in a Ruby application as it is possible to do a lot with very little code.
Furthermore it allows us to bring in a junior on the team because we know they have a safety net.
Also for the record we do code reviews and are very thoughtful about the code we write. 100% coverage does not stop the possibility of some bugs inserting themselves somewhere.
- snarf21 9y agoExactly this. One problem with TDD, etc. is that you are limited by the quality of your tests. 100% means nothing if you don't have a try/catch around a cache lookup that could should never fail but could and not get handled.
- bluGill 9y agoNo, that isn't a limitation with TDD. That is a limitation of imagination, and can happen to any programmer. (proving the code correct is most likely to catch this - but even that can fail in some cases) TDD just means that when discover the bug and add the missing try/catch you don't accidentally break something else.