Tuesday 10 December 2013

What came first?

Yesterday marked Grace Hopper's 107th birthday. She was one of the first computer programmers and is famous for spotting the first ever bug (a moth to be precise). My question is, did the bug come first which then lead to testers doing testing or was it other way round? I think testers came first otherwise the bug would have never been 'raised'. You need someone (i.e. a tester) to identify an issue or a problem which can then be confirmed as a bug (or something else like a new feature!).

I have two NEWS items:
1st) I will be leading a workshop in May 2014 at Test Bash 3 about being creative as a tester and visualising the testing which can help with test planning and design as well as reporting. More details here: http://www.ministryoftesting.com/training-events/be-creative-a-visual-testing-workshop/

2nd) The 1st draft of the Cartoon Tester book is nearly ready. You can follow the progress here: https://leanpub.com/thecartoontester

3rd) This isn't news, but don't forget to follow The Cartoon Tester Facebook page :) https://www.facebook.com/cartoontester


  1. Surely the bugs came first...? We just didn't know they were there until someone pointed them out!
    But you're right, that does beg the question, is a bug a bug if it hasn't been raised?

    Also, this cartoon is both disgraceful and hilarious!

  2. Hi Iain,
    I guess my thinking behind this is that's only a bug if somebody thinks it's a bug. Similar to the definition of quality it's value to some person. The bug only exits because a person (in this case a tester) believes it devalues the software in some way, so with this reasoning, the person is first, then the bug.

    My wife walked past the computer, saw the cartoon and was shocked!
    The problem I have is that I don't think through my cartoons. It's a tester and a bug sharing a bed, what's disgraceful about that!