11 Exploratory Testing

things no one thought about
different purpose than intended
aspect not considered in design
goal to understand the system

no specific test plan
ANY user new to a system might chose to do exploratory testing
might find more errors; don't need no test plan documentation
(but should have some kind of report)

unregulated and unplanned
assumes diligence of tester
defects might be hard to reproduce
hard to say how much testing has been done
(DO NOT USE for safety critical systems)
assumes users recognize defects

guidelines for exploratory
	use your best judgement
	might start with basic functions
	(maybe try breaking the software)
	look for cracks
	try to violate a null pointer