Exploratory Testing: Features and Appliance

by Nataliia Vasylyna | September 20, 2016 7:00 am

The testing types list seems to be endless and, moreover, some of them have very similar characteristics. Many “green” testers cannot realize the fine line between ad-hoc testing[1] and exploratory testing, for example, or divide usability testing from user interface testing.

Exploratory testing[2] – the category of testing, distinguished by the way of execution.

What Are the Main Peculiarities of This Software Testing Type?

• Learning the specification
• Creating the test cases
• The product examination is performed at the same time.

The key purpose of exploratory testing is to consider in depth the product under test and to use the received knowledge for finding the bugs.

When Exploratory Testing Should Be Performed?

• Lack of time for learning the specification;
• Not enough time for creating test cases;
• The absence of human resources;
• Wish to vary the test process;
• Examination of the specified object properties.

The preparation for exploratory testing like any other testing, for example, functional testing or regression testing[3], should include the scope of the testing procedure and the answers to such questions as “Why should we test this product?” “How should we test it?” “What issues do we expect to find?”

The results of exploratory testing should present the estimation of test coverage, test run log, the execution date and the name of the responsible specialist, the found bugs, the list of the faced issues and the possible one, other questions, and tasks which may occur through the testing.

Related Posts:

• Exploratory Testing: Benefits, Techniques, and Applications[4]
• How to Find More Bugs with Exploratory Testing[5]
• A New Approach to Exploratory Testing[6]

Source URL: https://blog.qatestlab.com/2016/09/20/exploratory-testing-features/

---