Secret Jargon of Software Testing

Malfunctional Testing: when the application makes sure you can’t see a single part of it behaving as expected

User Refusal Testing: the unmissable bursts of anger by users irked by approaching deadlines and receding functionalities

Disintegration Testing: getting ready to the sad truth that the arrival of a new application will destroy anything that had been working beforehand

Quality Lack-of Testing: making sure no part of the software package is fit for human interaction

Undress Rehearsal: planning to revert to a previous, working version of the software as the new one will invariably fail the call of duty

Dress Rehassle: more bursts of anger by users duped into weekend work despite knowing that nothing will perform

Digression Testing: the time passed in vague chit-chatting whilst awaiting confirmation that the application really, definitely does not work

Data Emigration: packing up all attempts at installing a new software package, in order to concentrate to a different pipedream application

And finally…

Hindrance Desk: the group of people whose main aim is to make you listen to muzak on the phone before providing misleading information

===========

And here’s more: Loser Acceptance Testing, Test Mythodology, Dysfunctional Testing, Capability Maturity Muddle, Test Automation, Risk-based Testing, Black Box Testing, Fragile Development, Delusability Study, Fenestration Testing, Hard Disk Figmentation, all by Steve Green.

(originally posted on 12 April 2005)