Content deleted Content added
Corrections to oversimplified use of the term Exploratory. Added external link to a seminal work on Exploratory Testing by James Bach and Cem Kaner. |
No edit summary |
||
Line 1:
'''Exploratory testing''' is the tactical pursuit of software faults and defects driven by challenging assumptions. It is an approach in [[software testing]] with simultaneous learning, [[test design]] and test execution. While the software is being tested, the tester learns things that together with experience and [[creativity]] generates new good tests to run.
==History==
Line 13:
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 & James Back<ref>http://www.testingeducation.org/a/nature.pdf</ref>, Exploratory testing is more of a mindset than a methodology. They also say show it crosses a spectrum from slightly exploratory (slightly ambiguous or vaguely scripted testing) to highly exploratory (freestyle exploratory testing).
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.
| |||