I’m going to keep this post quite short. It’s a thought I’ve been having for a while now.
Here goes with the impact statement: Test Techniques are actually just activities that relate to some context of a testing mission.
Think about it…
Take “load testing”, or “accessibility testing”, or “function testing”, or “security testing”, or any of the other 120 different test techniques (which Dan North mentioned in his keynote talk at the Agile Testing Days conference last year). They all relate to a specific purpose of testing. A mission for that test… The “technique” is just a label for the activity.
Initially, when I heard Dan mention about there being over 120 different techniques, I thought “Wow! I’d be pushed to be able to name 50…”. But taking the terminology of each technique out of the equation and thinking about the activity relating to whatever the context of each of your specific testing missions, 120 seems like quite a low number.
So, I would say that at the heart of being a good tester is the ability to take the software that you are testing and think laterally about the many different types of test missions that are relative to the software and that are important to your stakeholders, rather than try and run through a set list of “test techniques”.