Exploratory testing: Difference between revisions

Content deleted Content added
Doab (talk | contribs)
Expanded on Definition in first paragraph
IQDave (talk | contribs)
No edit summary
Line 1:
'''Exploratory testing''' is the ad hoc 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 19:
==Benefits and drawbacks==
The main advantage of exploratory testing is that less preparation is needed, important bugs are found fast, and is more intellectually stimulating than scripted testing.
 
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 the current series of scripted tests before focussing in on or moving on to exploring a more target rich environment.
 
Another major benifit is that most bugs after initial testing are discovered by some sort of exploratory testing. Programs that pass 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 the tests 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.