7 ms·
How do you tell that the calculations were done correctly? Presumably you have some way of doing that. Then, why don't you apply that way to the output? You do
by StavrosK 5y ago
How do you tell that the calculations were done correctly? Presumably you have some way of doing that.
Then, why don't you apply that way to the output? You don't need tests if you only need to do it once.
- pigeonhole123 5y agoChecking that the code outputs what you think it does is a pretty low bar to clear. The fact that you can think of higher bars doesn't invalidate the value of checking this.
- stonemetal12 5y ago>How do you tell that the calculations were done correctly? Presumably you have some way of doing that. Isn't that what we are discussing, how to tell if a piece of code works? You could do a formal proof that the code works (which is long and tedious) or you can test it (less long and tedious but less rigorous). >You don't need tests if you only need to do it once. It doesn't matter how many times you plan on running it. What counts is how much we value the output. I wouldn't bet $20 that untested code works correctly.