Tuesday, 3 September 2013

Bug reporting



I got the idea for today's cartoon from reading a uTest blog:
http://blog.utest.com/the-repercussions-of-poorly-written-bug-reports/2013/08/

One thing I would like to add about this cartoon (and its message) is that on some occasions all you need to do is point to the bug, or take a screenshot or write one simple sentence for a summary. Sometimes you need a lot more than that. That's all I wanted to add.

I'm still open for more suggestions for the Cartoon Tester book title, please leave a comment with your suggestion/s.
My original idea was calling the book either "Buggy software and other facts about testing" or "Buggy software and other cartoons about testing" but I was kindly recommended to ask my blog readers instead!
Anyone know where I got the idea for those two book tittles... it's of course the greatest book about software testing - have you read it yet?
Posted by Andy Glover

8 comments:

  1. Anonymous4 September 2013 at 12:17

    "Software Testing: Sometimes Cartoonish" - may not be very positive but... hey, gotta have a sense of humor.

    Maybe refer to "Systems Thinking"?

    "Testing Explained in Cartoon Thinking"

    ReplyDelete
  2. Andy Glover5 September 2013 at 00:17

    Cool suggestions. Thanks ThePainAndGainOfEdwardBear!

    ReplyDelete
  3. Mark Gilby5 September 2013 at 00:42

    Testing - Drawing on Experience

    ReplyDelete
  4. Andy Glover5 September 2013 at 05:05

    Nice one Mark, I like it.

    ReplyDelete
  5. James Thomas8 September 2013 at 02:17

    Lessons Learned in Cartoon Testing


    ReplyDelete
  6. Aliya Arshad9 September 2013 at 00:45

    not drawn that bad, by the way :)

    ReplyDelete
  7. Andy Glover10 September 2013 at 12:01

    Thanks for the suggestion James :)

    ReplyDelete
  8. Andy Glover10 September 2013 at 12:02

    Thanks Aliya, I did try really really hard to draw a bad drawing! :D

    ReplyDelete

Subscribe to: Post Comments (Atom)