Skip to main content

Heurism

I'm watching my son, a toddler, at play. He picks up his toy train, a hefty piece of wind-up fisher-price-esque technology, and hurls it at the water bottle. I'll not pass judgement - but suffice to say - the bottle is still standing - several other objects in the room are not. He reaches down with both arms and picks up the train again. He steps a bit further away, turns his back on the bottle, and slings it back over his shoulder. A few more similar attempts end in much the same result, Until finally the killer-move is identified: You stand point-blank over the bottle and drop/throw the train down onto the bottle.

A chip off the old block. I'm glad my son is having fun. But I'm interested - What's he thinking? No, that's not it... How is he thinking? What he's doing has strong parallels with what his father does for a living. I spend much of my time learning how [for example] a tool works or, maybe more often, how they don't work. If that takes the application of a 'surprise' heavy load well that just adds to the fun.

I think back to my recent reading and Rapid Software Testing course. If there's one word that sticks in my mind from both it's: 'Heuristic'. So is he applying heuristics? and if so which ones? He needs to know if he's hit the bottle with the train - that's more of a matter of observation. He clearly has a hypothesis that lobbing the train can 'take-down' that evian bottle (Which he generally disproves - clearly a fan of Popper) - but again thats not really a heuristic.

It's simpler than that. I looked up Heuristic in the dictionary and didn't find much clarification. However, I did notice the word: Heurism. "The educational practice or principle of training pupils to discover things for themselves." - Oxford English Dictionary. My son was learning for himself, he was gaining evidence for himself, empirically. He was building-up his first-hand experience. That's what I do! I can't give you much information until I actually use your system. Let me hurl a few keystrokes at the command line, and I'll give you back some real fact based information. Let me do it a few times, and I'll give you back even more information.

In fact that reminded me of a real technique I use when testing: Bug-compression. If I find a bug - lets say a user-path that has many commands or clicks, I spend a little time 'compressing' the steps - reducing the number of operations or clicks too just a few. This can be valuable in demonstrating that users could reach this 'failure state' more easily than it might at first appear. E.g.: The 'unlikely event' is now only three key presses away from the happy path.

This makes sense, My son's building the store of knowledge that firstly: he can use to generate his own heuristics and secondly: maybe apply the heuristics he's already learned. As testers we need to get into one of those feedback loops, where our actions are giving us more information that helps us find out even more. Get your hands & eyes on the controls, the logs, the database. There's a heuristic right there, built from hands-on experience: "Check the log files for error messages." It's fallible, but none the less, it's been a good way to find oddness and bugs so far.

Comments

Popular posts from this blog

Why you might need testers

I remember teaching my son to ride his bike. No, Strike that, Helping him to learn to ride his bike. It’s that way round – if we are honest – he was changing his brain so it could adapt to the mechanism and behaviour of the bike. I was just holding the bike, pushing and showering him with praise and tips.
If he fell, I didn’t and couldn’t change the way he was riding the bike. I suggested things, rubbed his sore knee and pointed out that he had just cycled more in that last attempt – than he had ever managed before - Son this is working, you’re getting it.
I had help of course, Gravity being one. When he lost balance, it hurt. Not a lot, but enough for his brain to get the feedback it needed to rewire a few neurons. If the mistakes were subtler, advice might help – try going faster – that will make the bike less wobbly. The excitement of going faster and better helped rewire a few more neurons.
When we have this sort of immediate feedback we learn quicker, we improve our game. When the f…

Thank you for finding the bug I missed.

Thank you to the colleague/customer/product owner, who found the bug I missed. That oversight, was (at least in part) my mistake. I've been thinking about what happened and what that means to me and my team.

I'm happy you told me about the issue you found, because you...

1) Opened my eyes to a situation I'd never have thought to investigate.

2) Gave me another item for my checklist of things to check in future.

3) Made me remember, that we are never done testing.

4) Are never sure if the application 'works' well enough.

5) Reminded me to explore more and build less.

6) To request that we may wish to assign more time to finding these issues.

7) Let me experience the hindsight bias, so that the edge-case now seems obvious!

Being a square keeps you from going around in circles.

After a weary few hours sorting through, re-running and manually double checking the "automated test" results, the team decide they need to "run the tests again!", that's a problem to the team. Why? because they are too slow. The 'test' runs take too long and they won't have the results until tomorrow.
How does our team intend to fix the problem? ... make the tests run faster. Maybe use a new framework, get better hardware or some other cool trick. The team get busy, update the test tools and soon find them selves in a similar position. Now of course they need to rewrite them in language X or using a new [A-Z]+DD methodology. I can't believe you are still using technology Z , Luddites!
Updating your tooling, and using a methodology appropriate to your context makes sense and should be factored into your workflow and estimates. But the above approach to solving the problem, starts with the wrong problem. As such, its not likely to find the right ans…