4 ms·
I think what they're saying is that both the code and test will contain the bug, since the bug is in the programmer's understanding rather than just in their co
by icebraining 8y ago
I think what they're saying is that both the code and test will contain the bug, since the bug is in the programmer's understanding rather than just in their coding.
If I understood func(5, 6) should return 9, but the client actually wants 10, no amount of tests I write will reveal the error.
- neo2006 8y agoI don't think that any form of formal specification will solve that issue. The only way to minimize the impact of it is to work on small iterations (agile) and be close to the client. One of the weakness in agile methodologies today is that the client representation (Product owner) is not aware of the client needs or too far from the client point of view.
- sombremesa 8y agoThis is roughly what I meant - there are ways to end up with zero bugs, but writing tests is usually insufficient for achieving such a goal.