3 ms·
>And 100% coverage is for sissies Depends on your project and the cost of failure. I once worked on a system that would automatically instruct semi-truck driv
by ShabbyDoo 17y ago
>And 100% coverage is for sissies
Depends on your project and the cost of failure. I once worked on a system that would automatically instruct semi-truck drivers to move their vehicles hundreds of miles. I spend over a week building tests for transactionality/concurrency edge cases to make sure that two trucks could not be instructed to go to the same place in error. Worth it? Yup. Should you test all possible behaviors of a utility script that, if broken, can just be re-run? Probably not.
- gokhan 17y agoIt sure depends on the project type, I was talking about projects of HN people. For my site, for example, I have broken the signup process twice so I now have a couple of tests for it, unit + watin. But I won't bother with writing tests for, say, privacy settings.