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

A h̶i̶t̶c̶h̶h̶i̶k̶e̶r̶'s̶ software tester's guide to randomised testing - Part 1

Mostly Harmless, I've talked and written about randomisation as a technique in software testing several times over the last few years. It's great to see people's eyes light up when they grok the concept and its potential. 
The idea that they can create random test data on the fly and pour this into the app step back and see what happens is exciting to people looking to find new blockers on their apps path to reliability.
But it's not long before a cloud appears in their sunny demeanour and they start to conceive of the possible pitfalls. Here are a few tips on how to avert the common apparent blockers. (Part 1) Problem: I've created loads of random numbers as input data, but how will I know the answer the software returns, is correct? - Do I have to re-implement the whole app logic in my test code?
Do you remember going to the fun-fair as a kid? Or maybe you recall taking your kids now as an adult? If so then you no doubt are familiar with the height restriction -…

Betting in Testing

“I’ve completed my testing of this feature, and I think it's ready to ship”
“Are you willing to bet on that?”
No, Don't worry, I’m not going to list various ways you could test the feature better or things you might have forgotten.
Instead, I recommend you to ask yourself that question next time you believe you are finished. 
Why? It might cause you to analyse your belief more critically. We arrive at a decision usually by means of a mixture of emotion, convention and reason. Considering the question of whether the feature and the app are good enough as a bet is likely to make you use a more evidence-based approach.

Why do I think I am done here? Would I bet money/reputation on it? I have a checklist stuck to one of my screens, that I read and contemplate when I get to this point. When you have considered the options, you may decide to check some more things or ship the app. Either could be the right decision.
Then the app fails…
The next day you log on and find that the feature is b…

Software development is in the Doldrums

"Don't get off the boat."

"Seriously, never get off the boat," The instructor said, leaning forward and looking at each of us in turn.

"But surely if it's sinking..." We reply, somewhat confused and slightly incredulous. We've seen Titanic, we think to ourselves, we know how this sea survival stuff works...

"OK" He concedes, If things get really bad, "Get on the life raft if you can step-up from the boat to the life raft".

"But, But... the yacht is like 37ft long, Do we want to wait until that whole boat is lower than the life-raft? When less than 1ft of the yacht is above the surface? Meanwhile all the time the life raft is just there... floating happily alongside."

"Pretty much, yes," he said nodding.


That was about 15 years ago. Not much has changed since. The reasons are manifold. Firstly, the yacht is a decent shelter. The thin plastic of a legal minimum life-raft isn't going to protect you fro…