Skip to main content

All ketchup bottles are not red.


I often have problems in finding the ketchup bottle from our refrigerator. At some point I started to notice this, and eventually realized why I did not find it. It was because I was looking for something red, but the Heinz ketchup bottle isn't actually red but transparent instead. So after it has been used for a while (I have a three year old son so it doesn't last full long), it becomes mainly transparent in color. And when I start to look for the ketchup, I can't find it because I'm searching for something red.

Today I had a short discussion with my wife which wen't about like this:
Wife: Do you know where's the ketchup?
Me: The bottle isn't red, try looking for a transparent bottle.
Wife: Oh there it is.

You get the lesson already? Well I have another close experience of similar kind.

Last week I was taking part in Helsinki testing day as a test lab assistant. I was responsible for my own stand where I had created a few testing tasks for an open-source web shop. While trying to teach people hovering about some testing related lessons, I was also experimenting with the tasks. My devilish plan was that I had created tasks for testing same areas of the app but with a different story behind the task, wanting to see how it effects people.

One of the tasks was to test a product review function, out of which which I had noticed a small issue in slightly testing it. I had created two tasks:
1. a test case with execution steps for testing the function
2. a story that went: "We have received complaints from product review section. It seems same people are doing reviews on the same products many times, which seems a bit odd.. Could you please investigate what might cause this?"

The two people running the first task, didn't really find anything to report from it. The three people running the second one found multiple issues in the function, many that I hadn't, part of them pretty solid and some maybe less so. I think that this happened (yea I know that the statistical amount of testers isn't enough to make this kind of assumption but why let that get in the way of a good story) because in the second case they thought they knew that there was a specific issue in it.

So into the lesson then: If you think you know that there is a problem of certain sort, it's a lot easier to find the problem. If you are looking for red ketchup bottle, it's a lot easier to find the red ketchup bottle. But remember --- all ketchup bottles are not red.

Comments

Popular posts from this blog

Testers doing test automation - is that the most important thing for you to do right now?

I've been thinking quite a lot about tester's moving to do test automation.  Lately beause of these three things: 1.  European testing conference , a great testing conference I attended couple of weeks ago. It is very cool due to many things; the way the speakers get compensated, the focus on the conferring side of conferences making it very easy for people to discuss stuff, the way the talks are chosen, and because there are also a lot of developers joining. So anyway when I was talking with several of the attendees, it was a bit strange how it was easier for me to talk about the product development as a whole with the developers, where as with the testers it more naturally moved into talk of automation and tools. Also on the open space, I think the majority of the topics pitched was automation or tool related. And quite little on the process or on the customer facing side of product development.  2. In my company there are a lot of different products and...

Testing drunk

(My first blog writing ever.) I've been thinking a long time that it's funny how many bugs I find by accident. Try to do something, make a mistake and boom - a bug is found.  Making the mistakes intentionally doesn't quite work - that's why they are called accidents I guess.. So I've thought of ways to make myself more prone to accidents, coming up with an apparent one; testing drunk. TUI (testing under the influence). So this I gotta try. More to come on that later.

Six reasons why testers should do code reviews

I have had quite a lot of discussions about code reviews. Quite many also with testers, by which I have understood that many do not do those. I will not start arguing here on whether code reviews are good/important or not. But I will list a few things why I think testers would benefit of doing them. 1. Code is the only documentation that is up to date . If you really want to know how something really functions, you want to be able to see and read the code. 2. Knowing more about the thing done enables you to do better testing . You can spot things that you should definitely test, and things that you probably don't need to test that much. Like extra things added by coder, usage&modifications of existing functions, data types, etc. And to arguments thinking that one loses their "independence" as a tester by knowing too much, I would worry a lot less about that than about testing stuff that you have no idea on how it has been built. 3. Improve logging . I obse...