3 ms·
I agree that with you that "some errors are expensive and some are not," but you don't know which category a bug falls under (cheap/expensive) until after the f
by gabriel 18y ago
I agree that with you that "some errors are expensive and some are not," but you don't know which category a bug falls under (cheap/expensive) until after the fact. So making that decision of what (or what not) to test isn't always so black and white.
- kschrader 18y agoAlso, a bug might be cheap now, but when it breaks a year down the road and no one knows what happened, it's going to be a big problem.
- timcederman 18y agoIt depends on the context. I've had some very simple fixes/updates I've wanted to put in production that I knew were incredibly low risk, and anything that could go wrong could not possibly be catastrophic, only to be vetoed and told to go through a very expensive testing process.
- richcollins 18y agoYes you do. When you are making a prototype errors aren't expensive. When you are modifying code that customers are already paying you lots of money for errors are expensive.