Yet more Monty Python & Software Testing

I drift in and out of Monty Python analogies for Software Testing now and then. Here's a previous reference <link>.

Whilst falling asleep the other night I remembered a Phil Kirkham post about Monty Python and my comment on it, so I thought I'd indulge myself and do a little bit of Monty Python - Software Testing analogising(?) - just for therapy :)

Here's the "Life of Brian" based comment I made:

Coordinator: Crucifixion? 

Prisoner: Yes. 

Coordinator: Good. Out of the door, line on the left, one cross each. 

[Next prisoner] 

Coordinator: Crucifixion? 

Mr. Cheeky: Er, no, freedom actually. 

Coordinator: What? 

Mr. Cheeky: Yeah, they said I hadn't done anything and I could go and live on an island somewhere. 

Coordinator: Oh I say, that's very nice. Well, off you go then. 

Mr. Cheeky: No, I'm just pulling your leg, it's crucifixion really. 

Coordinator: [laughing] Oh yes, very good. Well... 

Mr. Cheeky: Yes I know, out of the door, one cross each, line on the left. 

Or, as applied to testing...

Coordinator: Scripted test?

Tester: Yes

Coord: Good. Other there on the shelf, one scripted test case each.

[Next Tester]

Coordinator: Scripted test?

Tester: Er, no, an exploratory approach please.

Coord: What?

Tester: Yes, they said I could come and do some testing with my eyes open.

Coord: Oh, I say, that's sounds very nice. Well, off you go then.

Tester: No, I'm just joking my PM gets scared if we don't follow the script.

Coord: Oh, well in that case...

Tester: Yes I know, over there, one scripted test case each.

Life of Brian is a rich source:

Spectator I: I think it was "Blessed are the cheesemakers". 

Mrs. Gregory: Aha, what's so special about the cheesemakers? 

Gregory: Well, obviously it's not meant to be taken literally; it refers to any manufacturers of dairy products.

Or, as applied to testing...

Tester I: I think it was "Blessed are the certified".

Tester II: What's so special about the certified?

Tester III: Well, obviously it's not meant to be taken literally; it refers to any arbitrary label or categorisation.

There's lots of potential in the Meaning of Life too:

Three Project Managers (PM) and a management consultant (MC) discuss the state of affairs:

PM#1: Ah! Morning Perkins.

PM#2: Morning.

PM#1: What's all the trouble then?

PM#2: Test reports in disarray. During the night.

PM#1: Hm. Not nice numbers eh?

PM#2: Yes.

PM#1: How's it feel?

PM#2: Stings a bit.

PM#1: Mmm. Well it would, wouldn't it. That's quite a lot of extra information you've got there you know.

PM#1: Yes, real beauty isn't it?

All: Yes.

PM#1: Any idea how it happened?

PM#2: None at all. Complete mystery to me. Woke up just now... one piece of detailed analysis too many.

:

PM#1: Hallo Doc.

MC: Morning. I came as fast as I could. Is something up?

PM#1: Yes, during the night old Perkins (PM#2) had his test progress reports disrupted.

:

MC: Any headache, bowels all right? Well, let's have a look at this test report of yours then. [Looks at sheet] Yes... yes... yes... yes... yes... yes... well, this is nothing to worry about.

PM#2: Oh good.

MC: There's a lot of it about, probably a virus, keep warm, plenty of rest, and if  you're reporting progress remember to stick to statistics.

PM#2: Oh right ho.

MC: Be as right as rain in a couple of days.

PM#2: Thanks for the reassurance, doc.

:

MC: Jolly good. Well, must be off.

PM#2: So it'll just sort itself out then, will it?

MC: Er... I think I'd better come clean with you about this... it's... um it's not a virus, I'm afraid. You see, a virus is what we doctors call very disruptive. So it could not possibly have made a positive impact on the quality of these reports. What we're looking for here is I think, and this is no more than an educated guess, I'd like to make that clear, is some multi-cellular life form the genu *bonus extertus*. What we management consultants, in fact, call a good tester.

All: A good tester...!!

:

PM#3: A good tester - on this project?

PM#1: Hm...

PM#3: A good tester on this project...?

PM#1: Ah... well he's probably escaped from a zoo.

And remember don't be complacent in testing:

A tester has been asked for his certification in testing:

Tester: "I didn't expect a kind of Spanish Inquisition." 

Certification advocate: "Nobody expects the Spanish Inquisition! Our chief weapon is surprise...surprise and fear...fear and surprise.... Our two weapons are fear and surprise...and ruthless efficiency.... Our *three* weapons are fear, surprise, and ruthless efficiency...and an almost fanatical devotion to the certification syllabus.... Our *four*...no... *Amongst* our weapons.... Amongst our weaponry...are such elements as fear, surprise.... I'll come in again."

I was working on the dead parrot and test tool vendors, but it got messy - so I'll stop there!

Testing Style: "Eyes Wide Shut" vs "Eyes Wide Open"

 #softwaretesting #qa #testing ;

What's your approach to testing?

What first impressions do you get from "eyes wide shut" and "eyes wide open" as applied to testing?

Let me do a quick mind-dump, word association thing - the order below is exactly how it turned out - I then went back to add a bit of detail between the bullet-points. You'll have to excuse the odd Monty Python moment...

Eyes Wide Shut

• Parrot

I suspect I was primed by the recent video interview with James Bach about bucanneer testing and parrots.

• Rote

Following word-for-word - no deviation.

• Led

Following and willing to be led. Whilst this may be good and necessary in some test activities, I think this is in the minority of cases.

• Sheep

Probably primed by Rob Lambert's recent agricultural reference (actually a serious post!)

• Blind

Not looking around.

• Sensory deprived

Not using all information inputs.

• No questions

Just follow the guide/script/instructions even if it doesn't make sense.

• Lemming

Can lead to the black swan event of all "eyes wide shut" testers.

• Same-old same-old

No change, never change, comfort zone, safe. Perfect candidate for automation.

Eyes Wide Open

• Searching

Using the script/test idea as a guide - an incomplete map.

• Alert
• Observant
• All senses in use

These three are very similar - when the tester is switched on and ready to react, think ahead and even pre-empt.

• In the zone

When all senses are engaged and the tester is questioning the product it's similar to the sporting equivalent of being "in the zone".

• Feedback

The tester is questioning to give good feedback. Nobody expects the Spanish Inquisition. Questioning is our main tool, questioning and feedback, ohh...

• Exploratory

Map-making in real time!

• Investigative

The best of journalistic and scientific investigation - following-up on previous experience, hints and clues with the information in front of you.

• Ideas

The activity generates new ideas - either for further testing, how to solve test problems, feedback on the product or how to improve the product.

Note, I don't consider this as scripted vs non-scripted. I consider it more "good testing" vs "not-good testing" (I place no other emphasis on it than that...)

There are some cases where scripted testing is necessary (even a legal requirement) and others where it's needed as a guide.

My take on buccaneer testing and parrots - they are different species and unless the parrot is supposed to do everything-by-rote then it's the "eyes wide shut" case. I've got another take that I'll expand on in another post.

Of course, if the parrot is a Norwegian Blue then it definitely ain't dead and it's actually very good testing! :-)

Do your own word association and see what you come up with!

Monty Python and Software Testing Myths

After reading a post on Matt Heusser's blog mentioning a discussion on "Zero Defect Software" I immediately started thinking of this as one of the "Holy Grails" of software development.

This was then a natural progression (for me) to then start thinking about the film "Monty Python and the Holy Grail", Holy hand-grenades to battle the things stopping us from reaching "ZDS", Monty Python in general and other silly analogies, etc, etc.

There! You've just seen divergent thinking in action!

Use of analogy?

The monty python films & sketches tackle sacred beliefs, assumptions & taboos - things you shouldn't question the truth of.

But, can you say that to a software tester?

Yes, but don't expect them to not question what's put in front of them - as long as the questioning is about learning, understanding the different perspectives/applications and not just being critical for the sake of it!

So, monty python, ZDS and holy grails started me thinking about "testing myths" and how I might apply elements from their work to help achieve or dispell those myths.

It's seems unlikely to say that software testers can learn from Monty Python, but I think I'm seeing some parallels (it's not exactly proof by contradiction, more dis-proof by absurdity!)

For anyone not familiar I've attached some Monty Python youtube search 

options so you can view at your leaisure..

Myths and the Monty Python Answers

• Zero Defect Software

MP: The holy hand-grenade can be used to combat obstacles to getting there!

(youtube search:  monty python and the holy grail holy hand grenade)

• Quality can be tested into the product

MP: This is the dead parrot sketch. "No it's not dead it's just resting" - no matter how serious the bugs/flaws it can be denied/improved afterwards.

(youtube search: monty python dead parrot sketch) 

• Test Certifications are necessary for testers

MP: This is the King Arthur discussion with the peasants on systems of government - he is king because of the lady of the lake, no other logical reason or demonstrated ability.

(youtube search: monty python and the holy grail systems of government) 

• Testing is Easy / Anyone can be a tester

MP: Maybe this is the Life of Brian syndrome - an innocent passer-by is mistaken for the messiah. Ignorance and misinformation play a part in incorrect conclusions.

• It's possible to test everything

MP: Could be the same answer as for "testing is easy". As a different answer: This is the Mr Creosote approach to eating - he doesn't get full, eating and eating until he eventually explodes. (Yes, it's not possible to "test everything")

• Testers are the Gatekeepers of Quality / Quality Police

MP: "Nobody expects the Spanish Inquisition!" If you try and ship early we'll get out the comfy chairs!

(youtube search: monty python spanish inquisition)

And finally...

For all those unicorn questions Monty Python's The Life of Brian has a good answer for tolerance: "Blessed are the cheesemakers!"

Remember, the ideas are silly, but then so are the myths - what a perfect match!

I extracted some of the myths from Renjini S. & TestingGeek.

Got any "new" myths? Maybe there's a need for a follow-up...