That’s not a bug
This is a universal rule: “When ever you’ll take a bug to the programmer, the reply would be that it’s not a bug”. Nothing to blame the programmers here, our first response to any bad happenings in our work is a denial. You tell me that my blog has some flaws, I won’t agree :). I tell my friend that he is on a wrong path in terms of financial management, he would tell me that I am no one to judge financial matters and the list goes on.
The answers that you get in support of that argument arereally nice and here are my top 5:
1. That’s not a bug, it’s a feature
Enough have been said on this and best described in this cartoon:
2. I cannot reproduce it on my machine
Though I didn’t try it :). Reason a Development environment is different from a Testing environment.
3. This is not a legitimate use case
Simply because the suspicion is that Testers are not as knowledgeable about the business case as an actual user would be.
4. I think the test data is corrupt
Only if it is coming from a Client.
5. On latest code, it’s not reproducible
If the code base under question has changed, this can happen but a bad behavior doesn’t go away magically 🙂
What are your favorite excuses that you observed?