Skip to main content

Wrong end of the stick

There's a story about air-force scientists during world war 2, that reflects an interesting concept about the things we see and how they can alter our assumptions. The story goes that the allied bombers were suffering great losses during their air-raids of continental europe. The allied scientists got together and anaylsed the damage reports from the engineers tasked with fixing the planes after each raid. (One of the scientists working on these problems was Abraham Wald )

Here is an example of the sort of summary engineering reports they might of been faced with. The report details the parts of the plane and what proportion of aeroplanes had been damaged in that area: (This data is completely made up by me):
15% had damage to 1 or more engines
25% had tail damage
25% had damage to the nose and cockpit area.
35% had damage to the fuselage

The aircraft engineers could only add extra-armour to one part of the plane, any more armour would limit the aeroplane in other ways e.g.: making it an easier target or unable to carry its deadly-cargo. Where would you add the armour? If you wanted to do your best to ensure that plane and its crew returned, where would you place the bet?

The story goes that the answer relies on 2 more pieces of information. Firstly, the flak could affect any part of the aero-plane, and didn't tend to always affect one part more than another. The second, was that the engineers data is not the full picture. It suffers from a [literal] survivorship bias. What about the planes that didn't come back? What parts of the aircraft are not listed in the engineers reports?

For example, the wings are not mentioned above. The idea is that the most critically damaged aircraft never made it back to the engineers. These would never be recorded in the statistics, and so the damage reports tended to show an almost inverted view of what needed to be armoured. That is, if a plane received damage to its wings - it never came home. The wings needed the armour most.

This is a situation I've witnessed in software testing. The phenomenon can exhibit itself in many ways. For example a simple mis-use of metrics, does feature X have 10 bug reports recorded against it? but but feature Y has just 2? Maybe feature Y isn't less-broken but so broken that no-one can use-it well enough to find more bugs. While the 'buggy' feature Y is popular and receives a lot of attention from its users, reporting the quirks and bugs they see.

A more subtle example might be, in a performance test, one server appears to display fewer errors. Maybe that server has the 'right' configuration, or its hardware is better: lets make all our servers like the 'good-one'. But it could be that this server is mis-configured or mis-managed in some way. Perhaps its not taking its fair-share of the load - forcing an overload on the other servers. In this case approaching the results skeptically might in fact save you from mis-interpreting the results, and propagating a 'bad configuration' just because it seemed to help in one scenario.

For a tester, the simple heuristic that your apparent results are just that: apparent, to you. They may in fact represent, as above, an entirely 'negative' image of how the software is actually behaving. Its worth spending some time testing your tests, because how do you know you haven't got the 'wrong end of the stick'?

I hope I haven't trivialised an important albeit dark aspect of european history with this post. I hope I have helped to use the information learned for a better purpose. For those interested in some of the effects of the allied bombing on continental Europe you wish to start reading about the Bombing of Dresden. You may also find articles concerning The Blitz of interest.

Comments

Popular posts from this blog

The gamification of Software Testing

A while back, I sat in on a planning meeting. Many planning meetings slide awkwardly into a sort of ad-hoc technical analysis discussion, and this was no exception. With a little prompting, the team started to draw up what they wanted to build on a whiteboard.

The picture spoke its thousand words, and I could feel that the team now understood what needed to be done. The right questions were being asked, and initial development guesstimates were approaching common sense levels.

The discussion came around to testing, skipping over how they might test the feature, the team focused immediately on how long testing would take.

When probed as to how the testing would be performed? How we might find out what the team did wrong? Confused faces stared back at me. During our ensuing chat, I realised that they had been using BDD scenarios [only] as a metric of what testing needs to be done and when they are ready to ship. (Now I knew why I was hired to help)



There is nothing wrong with checking t…

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, manumatio…

Scatter guns and muskets.

Many, Many years ago I worked at a startup called Lastminute.com (a European online travel company, back when a travel company didn't have to be online). For a while, I worked in what would now be described as a 'DevOps' team. A group of technical people with both programming and operational skills.

I was in a hybrid development/operations role, where I spent my time investigating and remedying production issues using my development, investigative and still nascent testing skills. It was a hectic job working long hours away from home. Finding myself overloaded with work, I quickly learned to be a little ruthless with my time when trying to figure out what was broken and what needed to be fixed.
One skill I picked up, was being able to distinguish whether I was researching a bug or trying to find a new bug. When researching, I would be changing one thing or removing something (etc) and seeing if that made the issue better or worse. When looking for bugs, I'd be casting…