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

Can Gen-AI understand Payments?

When it comes to rolling out updates to large complex banking systems, things can get messy quickly. Of course, the holy grail is to have each subsystem work well independently and to do some form of Pact or contract testing – reducing the complex and painful integration work. But nonetheless – at some point you are going to need to see if the dog and the pony can do their show together – and its generally better to do that in a way that doesn’t make millions of pounds of transactions fail – in a highly public manner, in production.  (This post is based on my recent lightning talk at  PyData London ) For the last few years, I’ve worked in the world of high value, real time and cross border payments, And one of the sticking points in bank [software] integration is message generation. A lot of time is spent dreaming up and creating those messages, then maintaining what you have just built. The world of payments runs on messages, these days they are often XML messages – and they ...

What possible use could Gen AI be to me? (Part 1)

There’s a great scene in the Simpsons where the Monorail salesman comes to town and everyone (except Lisa of course) is quickly entranced by Monorail fever… He has an answer for every question and guess what? The Monorail will solve all the problems… somehow. The hype around Generative AI can seem a bit like that, and like Monorail-guy the sales-guy’s assure you Gen AI will solve all your problems - but can be pretty vague on the “how” part of the answer. So I’m going to provide a few short guides into how Generative (& other forms of AI) Artificial Intelligence can help you and your team. I’ll pitch the technical level differently for each one, and we’ll start with something fairly not technical: Custom Chatbots. ChatBots these days have evolved from the crude web sales tools of ten years ago, designed to hoover up leads for the sales team. They can now provide informative answers to questions based on documents or websites. If we take the most famous: Chat GPT 4. If we ignore the...

Manumation, the worst best practice.

There is a pattern I see with many clients, often enough that I sought out a word to describe it: Manumation, A sort of well-meaning automation that usually requires frequent, extensive and expensive intervention to keep it 'working'. You have probably seen it, the build server that needs a prod and a restart 'when things get a bit busy'. Or a deployment tool that, 'gets confused' and a 'test suite' that just needs another run or three. The cause can be any number of the usual suspects - a corporate standard tool warped 5 ways to make it fit what your team needs. A one-off script 'that manager' decided was an investment and needed to be re-used... A well-intended attempt to 'automate all the things' that achieved the opposite. They result in a manually intensive - automated process, where your team is like a character in the movie Metropolis, fighting with levers all day, just to keep the lights on upstairs. Manual-automation, manu...