Recently, my cubie was testing one of our web apps. She got the following:
She wrote up the error and submitted it. It was for a currency amount, and she had put a zero in it. The defect was returned as "works as designed" as the field should never get a zero in it, meaning that the developer decided that a user would never put a zero. He stated it should be closed. She asked me about it.
I explained that:
1) A user should almost never see an ugly error like this. It is poor programming that would produce this.
2) Just how does a zero produce an overflow anyway? That makes very little sense to me, but then again, I don't have access to the code. Could be a calculation problem, I guess, but I'd expect a divide by zero before an overflow.
I guess he thought he could BS away the error rather than fix it. Pathetic.
posted @ Thursday, May 08, 2008 11:12 AM