Exploratory testing: Difference between revisions

Revision as of 21:27, 6 October 2006

Revision as of 19:55, 12 October 2006

Line 1:

'''Exploratory testing''' is an approach in [[software testing]] with simultaneous learning, [[test design]] and test execution. SinceWhile itthe hassoftware ais highlybeing situationaltested, structurethe ittester canlearns seem,things tothat thetogether casualwith observer,experience thatand it[[creativity]] hasgenerates nonew structuregood attests all.to run.

==History==

ItExploratory istesting alsohas knownbeen asperformed for a long time, and has similiarities to [[ad hoc]] testing]]. 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 [[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''. Exploratory testing can be as disciplined as any other intellectual activity.

==Description==

Exploratory testing seeks find out how the software actually works, and to ask questions about how it will handle difficult and easy cases.

The testing is dependent on the testers skill of inventing [[test case]]s and finding [[software bug|defects]]. The more the tester knows about the product and different [[test method]]s, the better the testing will be.

To further explain, comparison can be made to the antithesis [[scripted testing]], which basically means that test cases are designed in advance, including steps to reproduce and expected results. These tests are later performed by a tester who compares the actual result with the expected.

When performing exploratory testing, there are no exact expected results; it is the tester that decides what will be verified, critically investigating the correctness of the result.

In reality, testing almost always is a combination of exploratory and scripted testing, but with a tendency towards either one, depending on context.

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.

[[Session-based test]]ing is a method specifically designed to make exploratory testing auditable and measurable on a wider scale.

==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.

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.

When repeting exploratory tests, they will not be performed in the exact same manner, which can be an advantage if it is important to find new errors; or a disadvantage if it is more important to know that exact things are functional.

==Usage==

Exploratory testing is extra suitable if [[software requirement|requirements]] and [[Program specification|specifications]] are incomplete, or if there is lack of time. The method can also be used to verify that previous testing has found the most important defects.

It is common to perform a combination of exporatory and scripted testing where the choice is based on [[Risc-based testing|risk]].

An example of exploratory testing in practice is [[Microsoft]]s verification of [[Windows]] compatibility.

==External links==

*[http://www.istqb.org/fileadmin/media/SyllabusFoundation.pdf ISTQB: Certified Tester, Foundation Level Syllabus]

*[http://www.satisfice.com/articles/et-article.pdf Exploratory Testing Explained by James Bach]

*[http://www.context-driven-testing.com The Seven Basic Principles of the Context-Driven School]

==See also==

*[[Software testing]]

*[[Context-Driven School]]

*[[Test case]]

*[[Test script]]

*[[Ad hoc testing]]

*[[Session-based test]]ing

*[[ScenarioContext-Driven testSchool]]ing

{{soft-eng-stub}}

[[Category:Software testing]]

[[nl:Exploratory testing]]

[[sv:Utforskande testning]]