> In that case the return on writing tests to try to shake out those areas is pretty high. I agree, but in that case you shouldn't test for that one specific c

> In that case the return on writing tests to try to shake out those areas is pretty high. I agree, but in that case you shouldn't test for that one specific case that failed, but try to make a test that handles similar issues, or tries catch bugs of the same kind. Of course it depends how far you can push this.