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:

original source:

http://globalnerdy.com/wordpress/wp-content/uploads/2007/12/bug_vs_feature.gif

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?

4 responses to “That’s not a bug”

  1. SamreenM says :

    #5 .. and it is bound to come back in next code changes

    Like

  2. H Hamid says :

    I believe there is a sixth scenario to this situation as well. In a few teams, where a defect backlog remains unattended for several weeks\months, testers and\or users eventually get used to of using a faulty and buggy application. Eventually, the bug loses it’s essence and becomes an acceptable behavior or a familiar way in which an application works. That’s why you really need to keep the backlog active and rolling – 🙂

    Like

Trackbacks / Pingbacks

  1. Can Testers and Programmers be friends? « KnowledgeTester - February 14, 2013
  2. Bug finding heuristics | Knowledge Tester - December 18, 2013

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s