Skip to main content

The Hunky-dory Hypothesis

"If we just run it with this data, and it looks Ok, we'll know it works" the architect says expectantly, "Right?"

"You're right, We might see 'it work'", "How would that help?" I answer.

"Well errh, it works, so we can put it live tomorrow."

We've seen this situation before; it can arrive in conversation like the above, or from a review of Acceptance Test results or in a host of other forms. The premise is: everything is fine, we've done the work - we have evidence everything is done and working.

But, how can demonstrating that the application can 'work' help? How will seeing the acceptance test results as 'green' help? That might sound nonsensical, but seriously: how does it help our customer make the decision to ship [or not]? Or help them distribute people and resources better? It may seem that telling them 'its all hunky-dory' is news and good news at that, but it isn't. It can be reassuring, but often it actually harms our understanding of the situation we are in.

Lets take a step back. The code has been pair-programmed, checked by the developers, unit tested and peer reviewed. They believe it's good, their supervisor/reviewer thinks its great. The acceptance tests are all green and emitting a warm fuzzy feel good glow. The project manager, program manager and technical architect are all confident in their designs and plans - they're good - the software is ready to ship tomorrow. The vested parties believe and hence in their view, know, its good to go. A few cursory checks (see above 'test case') is all that is required. So how will confirming their view help? They're already convinced, they already know.

Their view is often the default for programmers, system administrators, those without a testing background or those with a vested interest in seeing the system shipped tomorrow. Their mental image of the software is like a clean sheet of paper, its blank, unblemished, all shiny and new. This spotless canvas also reports no information. No shadows, no ambiguities no feedback whatsoever. If during my testing, I confirm the 'hunky dory' hypothesis, I'm effectively painting white paint on my canvas.

But if during our testing, we find a problem, an area of ambiguity, or an outright bug - We increase our knowledge of the system under test. By filling in these gaps in our knowledge, We are painting a picture of how our system looks under various conditions. This image, albeit a 'Negative', provides the detail that was previously missing from our knowledge. Without this image we are blind to the potential problems and can not see the risks, let alone be able to mitigate them.

Good testing delivers information that helps us disprove our illusions. This process is invaluable in obtaining accurate knowledge of the risks associated with a software release. In a culture where software is considered innocent, until it crashes or loses you money, good testing can help overcome the group-think that often leads to poor software in live environments.

Comments

  1. I've had conversations like that more times than I care to think about. I'm afraid that each time it happens, some folks think that I'm either being pedantic, negative or intentionally trying to ruin their schedule. Excellent first sentence in the last paragraph. Solid post.

    ReplyDelete
  2. It's only a month ago since I learnt that term: honky-dory. And now you've written a splendid piece about it. Thanks, Pete!

    ReplyDelete

Post a Comment

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…

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…