Some people do seem convinced that exploration is a bad idea, saying that we can’t work without writing down everything in great detail, or providing a set of steps for testers to follow. So, for those people (who may or may not have concluded that exploratory testing means “no rules, just test”), I have this set of detailed steps to follow:

0. Recognize that exploratory testing doesn’t mean “no rules, just test”, but something more like “you can control the rules and work with them; the rules need not control you”–a point upon which the following steps build.

1. Go here (http://tinyurl.com/4wuhka) and read the blog post. This is my latest summary.

2. Go here, and read the PDF.

3. Go here, and read the PDF.

4. Reflect on what you’ve read.

5. If necessary, repeat steps 0-4 a few times.

6. If you still have questions, ask mb@michaelbolton.net, james@satisfice.com, kaner@kaner.com, or some of the many, many other people who have thought deeply about exploratory approaches for years.

Cheers,

—Michael B.

Btw, could you please summarize your ideas clearly for the people whos only conclusion have been : “Do more exploratory testing – meaning no rules, just test.”