Content deleted Content added
m Fixed a tag I broke |
m WP:CHECKWIKI error fix for #61. Punctuation goes before References. Do general fixes if a problem exists. - using AWB (11756) |
||
Line 1:
'''Exploratory testing''' is an approach to [[software testing]] that is concisely described as simultaneous learning, [[test design]] and test execution. [[Cem Kaner]], who coined the term in 1984,<ref>
While the software is being tested, the tester learns things that together with experience and [[creativity]] generates new good tests to run. Exploratory testing is often thought of as a [[black box testing]] technique. Instead, those who have studied it consider it a test ''approach'' that can be applied to any test technique, at any stage in the development process. The key is not the test technique nor the item being tested or reviewed; the key is the cognitive engagement of the tester, and the tester's responsibility for managing his or her time.<ref>Cem Kaner, ''[http://www.kaner.com/pdfs/QAIExploring.pdf A Tutorial in Exploratory Testing]'', p. 37-39, 40- .</ref>
Line 34:
Another major benefit is that testers can use [[deductive reasoning]] based on the results of previous results to guide their future testing on the fly. They do not have to complete a current series of scripted tests before focusing in on or moving on to exploring a more target rich environment. This also accelerates bug detection when used intelligently.
Another benefit is that, after initial testing, most bugs are discovered by some sort of exploratory testing. This can be demonstrated logically by stating, "Programs that pass certain tests tend to continue to pass the same tests and are more likely to fail other tests or scenarios that are yet to be explored."
Disadvantages are that tests invented and performed on the fly can't be reviewed in advance (and by that prevent errors in code and test cases), and that it can be difficult to show exactly which tests have been run.
Line 56:
| year = 2008
| url = http://www.kaner.com/pdfs/QAIExploring.pdf
|
| accessdate = October 23, 2010}}</ref>
The approach can also be used to verify that previous testing has found the most important defects.<ref name=Bach-ETE />
|