Exploratory testing: Difference between revisions

Content deleted Content added
linking and MOS:AMP
Line 4:
 
== History ==
Exploratory testing has always been performed by skilled testers. In the early 1990s, [[ad hoc]] was too often synonymous with sloppy and careless work. As a result, a group of test methodologists (now calling themselves the [[Software testing controversies|Context-Driven School]]) began using the term "exploratory" seeking to emphasize the dominant thought process involved in unscripted testing, and to begin to develop the practice into a teachable discipline. This new terminology was first published by [[Cem Kaner]] in his book ''Testing Computer Software'' <ref name=Kaner7-11>Cem Kaner, ''Testing Computer Software'', TAB Books, Blue Ridge Summit, PA, 1988. p. 6, 7-11.</ref> and expanded upon in ''Lessons Learned in Software Testing''.<ref>
{{cite book
|last = Kaner
Line 22:
In reality, testing almost always is a combination of exploratory and scripted testing, but with a tendency towards either one, depending on context.
 
According to [[Cem Kaner]] &and [[James Marcus Bach]], exploratory testing is more a [[mindset]] or "...a way of thinking about testing" than a methodology.<ref>Cem Kaner, James Bach, ''Exploratory & Risk Based Testing'', [http://www.testingeducation.org/a/nature.pdf www.testingeducation.org], 2004, p. 10</ref> They also say that it crosses a continuum from slightly exploratory (slightly ambiguous or vaguely scripted testing) to highly exploratory (freestyle exploratory testing).<ref>Cem Kaner, James Bach, ''Exploratory & Risk Based Testing'', [http://www.testingeducation.org/a/nature.pdf www.testingeducation.org], 2004, p. 14</ref>
 
The documentation of exploratory testing ranges from documenting all tests performed to just documenting the [[software bug|bugs]]. During [[pair testing]], two persons create test cases together; one performs them, and the other documents.