One of the things you’ve probably noticed when you’ve been software testing for a while, and particularly when you’ve been testing the same product for any length of time, is that your brain starts to settle into some established ways of thinking about the software you’re testing.
After a while, you already know where lots of the more challenging areas of your product are, and when you begin to do some testing you make a beeline for those areas because they’ve already proven themselves to be the most fertile hunting grounds for juicy bugs.
But how did you get into that area of the system? What route did you follow, and what might you have missed along the way?
What if instead of making that beeline - you branched off in a completely different direction? What might you find instead?
For some testing inspiration, why not download the "60 Power Heuristics to a Testing Groove" eBook by Simon Knight!
