Wednesday 7 April 2010

Fix them bugs, now!


  1. You introduced me with a new bug advocacy technique - AIDA


  2. Always happy to help out, although I wasn’t the first one to come up with this idea. I can’t for the life of me remember which test blog/article I originally heard about it.

    Do search on web for examples of AIDA. E.g. For the action, there are a number of options/methods: “Dual positive suggest”, “Concession method”, “silent methods”.

  3. Too much time spent for one bug :( I'm not sure that's good idea to rebuild project because of one fix until it isn't showstopper, but I like this approach in general!

  4. Remember you can use all or parts of this approach when completing a bug report – this shouldn’t take too much time. When entering the subject line, keep in mind that you should enter something short and snappy that will get the attention. For interest and desire suggestions, have a look at Kem Kamer’s bug advocacy training ( – it’s very good!

  5. Hi Andy,
    great slides, collegues think i am nuts, cause i giggle in front of the monitor.
    Suggestion: Put one more slide, where he goes to next "smelly" (oh, i love that one) and does the same, hrhr.
    Btw. "Tester" can be substituted with any stake holder... hehe.


  6. Well, I find it unethical to have severity of defect reduced to entice developer in to fixing it.
    Personally I would not mind discussing it with developer but only after having raised it in defect database.

  7. I have seen testers log extreme boundary scenarios and wish list as defects. They just want to log defects because their increments are linked to the number of defects they uncovered.