This week I am in Toronto taking Rapid Software Testing from Michael Bolton. Every time I talk with Michael he makes my brain hurt, so I am quite enjoying three solid days of him!
That is not however what I would like to talk about today. What I would like to talk about is this: Do you even need to test your product?
[Startlement! Amazement! Disbelief!]
Who says you need to test?
Why do you think you need to test?
I believe there are no good practices, or bad practices, or best practices. Which means there are contexts in which testing is not useful. The Rule Of At Least Three ("If you cannot come up with at least three plausible explanations for something, you do not understand it well enough / There are always at least three whatevers-are-being-discussed confirms this must be the case.
Let's brainstorm a bit, shall we?
If we widen the scope a bit, there are oodles of reasons you might not want to do certain types of testing:
So: do you really need to test? Do you really need to do all of the testing you thought you did? Let me know: Michael dot J dot Hunter at microsoft dot com.