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

Periodical retrospectives are lame

  "You got nothing, not a single thing?! Well lets just end this here then." I remember well when I said this, being very frustrated. About ten years ago I had been working as a Scrum master for a team some months, and putting quite a lot of effort into planning our scrum teams sprint retrospectives. Lot of work also because I felt we were not getting too much out from them; not very good discussions, very few actions, and even the few actions we did come up with did not stick.  And then it happened: a retro where none of the participants came up with anything to say about the sprint. Regardless of the retro topic boxes, reading of books on retrospectives, getting inspiration from tools like retromat.org, having them in different places, using all kinds of different formats and rainbow coloured post-it notes. Not a single thing. Blank.  So then I said the words, out of frustration, mainly to myself. Why couldn't I get this thing everyone is so hyped about to work? After t

I don't report bugs

I don't report bugs . Bug is such a loaded word that people understand very differently, that instead of using it and explaining what I mean by it I rather just use other words. Like observations, thoughts, surprises, ideas, alternatives, or something similar. (And no I don't use fault, defect, or error either). Bug has also quite a negative connotation. "Reporting a bug" is kind of like telling someone that they've been served. And as we are actually giving away the gift of information, why wrap it in such a nasty package? And maybe more importantly it is very likely that whatever you might have to say is wrong. If not plain wrong, then at least incomplete. So I like to approach the kind of situations with the assumption that I am probably wrong. Cutting off anything that might sound arrogant makes stuff quite a lot easier. Especially after you realise later on that you have been wrong. I leave plenty of observations unreported . I don't want to waste

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.