The Mystery of Exploratory Testing

by Nataliia Vasylyna | November 26, 2015 12:17 pm

In software testing sphere, there is an interesting suggestion that every checking type is actually exploratory testing[1]. To find out whether it is true, one should know all peculiarities and details of this testing type.

Unlike functional testing or usability testing, there is no need for the specialists from software testing company to prepare test scenario beforehand for exploratory testing execution. Testers have no limitations in searching for bugs. The results depend on specialists’ imagination.

Exploratory testing starts with defining the charter of testing procedure. It can be done by tester himself or by test lead. Every testing type, for example, system testing[2], is focused on the end user. Because of that, the specialist is able to constantly enhance and develop the product.

Examples of Testing Charter

• Find out and check all claims in the product manual.
• Define the ways of files corruption.
• Check the product integration with external apps.
• Check all possible ways of data entry.
• Test UI against Windows interface standards.
• Check the product performance in a specific file type.

The combination of exploratory and automated testing[3] provides more effective results. Recorded exploratory tests can be transformed to automated ones. If there is any failure with automated test, the exploratory principle helps to find the reason of incorrect work. Successful automated tests provide the further exploration of different issues and product components.

Related Posts:

• 3 Main Points of Exploratory Testing[4]
• Why is Exploratory Testing Underestimated?[5]
• What to Know About Exploratory Testing?[6]

Source URL: https://blog.qatestlab.com/2015/11/26/exploratory-testing-mystery/

---