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

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. Testing is gambling with your time to find information about the app. 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

Test Engineers, counsel for... all of the above!

Sometimes people discuss test engineers and QA as if they were a sort of police force, patrolling the streets of code looking for offences and offenders. While I can see the parallels, the investigation, checking the veracity of claims and a belief that we are making things safer. The simile soon falls down. But testers are not on the other side of the problem, we work alongside core developers, we often write code and follow all the same procedures (pull requests, planning, requirements analysis etc) they do. We also have the same goals, the delivery of working software that fulfills the team’s/company's goals and avoids harm. "A few good men" a great courtroom drama, all about finding the truth. Software quality, whatever that means for you and your company is helped by Test Engineers. Test Engineers approach the problem from another vantage point. We are the lawyers (& their investigators) in the court-room, sifting the evidence, questioning the facts and viewing t

XSS and Open Redirect on Telegraph.co.uk Authentication pages

I recently found a couple of security issues with the Telegraph.co.uk website. The site contained an Open redirect as well as an XSS vulnerability. These issues were in the authentication section of the website, https://auth.telegraph.co.uk/ . The flaws could provide an easy means to phish customer details and passwords from unsuspecting users. I informed the telegraph's technical management, as part of a responsible disclosure process. The telegraph management forwarded the issue report and thanked me the same day. (12th May 2014) The fix went live between the 11th and 14th of July, 2 months after the issue was reported. The details: The code served via auth.telegraph.co.uk appeared to have 2 vulnerabilities, an open redirect and a reflected Cross Site Scripting (XSS) vulnerability. Both types of vulnerabilty are in the OWASP Top 10 and can be used to manipulate and phish users of a website. As well has potentially hijack a user's session. Compromised URLs, that exp