In every project (well, nearly every one) there comes the moment, when testing gets squeezed for time. Immediately the next question becomes how to cut back testing in a sensible way.
The immediate reaction of many a tester (especially if she went through some kind formal training) goes a little like this:
Use Risk Based Testing!
I agree but sort of don’t…
A couple of days ago I had one of my epiphanies. (I’m not a genius so something probably just dawned on me ;-))
The question in my mind was “Why do we keep on producing such cr*p software that people just don’t like to use?“. I need to caveat that a little as I solely focus on bespoke development for larger organisations here.
There’s lots of rational reasons why this happens. Examples are:
But there’s one that I actually never thought of listing….. FUN.
Hello Test World 
