Sorry Azad, I don't agree ad-Hoc testing to be loss of time. Most of the time we do ad-Hoc testing to see if we are not missing any thing. And you will find very help and agree with me that Test Case are just not enough to say application is bug free. Many times we miss any test case scenarios which you can include once you start doing ad-Hoc testing. Also small budget project prefer ad-Hoc testing.
I will say in reveres that ad-Hoc testing can save your time..
Please add your valuable comments.
If you're doing ad hoc testing, then how would you know which is a bug and be sure that you are not missing anything.
Ad-hoc testing should be done in a controlled manner then only it will bring you results otherwise it is a waste time.
Just banging your keyboard without using your brain to learn anything about the product will not find you any bugs.
Actually this topic is a controversial topic. I think more than 90% members will disagree like you. I want say for live (in market) vs. demo (in developing period) project testing. Ad-hoc testing in live site may not bring anything fruitful which can happen for demo projects. For small projects test case may cover all the inputs……..Actuall currently I am doing ad-hoc and I am irritated.
I think you really really need to define what you mean by 'ad hoc' testing
Please let us know what your definition of it is and how you are doing it and why you find it 'irritating'
Okay, do you recognise any of the skills and techniques described here:
There's a lot of information there, if you're short of time, you might want to start with this blog post:
If you're finding that you run out of ideas pretty fast, and that your testing isn't particularly fruitful, then I'd suggest picking one or two of the resources up there and trying to apply them in your next session. It sounds rather like you're getting frustrated because you're just trying to throw yourself at the product under test without any kind of structure or analysis to help you - which is going to be pretty exhausting!
+1 for Annas post - Michael & James are really pioneering testing without (much) pre-planning.
They glean a lot of their info from Cem Kaner, who arguably conceptualised the term "Exploratory Testing" which formalises ad-hoc testing.
Also, dont forget James Whittaker who is taking the idea of exploratory testing tours to all new levels... (personally I feel he has taken the tour concept in a new direction by using terms & ideas which need translating in order to be understood by non-testers.)