Some of the common complaints about exploratory testing are that it needs subject matter expertise, it is not structured and it cannot be measured. But the fact is that exploratory testing is self-managed and self-structured. Exploratory testing is not a technique but an approach of exploring software without following a documented steps.<\/p>\n
In continuation to our last post<\/a>, Moin Syed – Principal Consultant – Advisory & Transformation Services at Cigniti Inc. in this post<\/a> provides a detailed overview of exploratory testing framework covering various aspects including best practices.<\/p>\n Exploratory testing can be more of skill-based testing than a role-based testing as people assume. Some of the skills like questioning, observation, critical and lateral thinking help an exploratory tester explore better. The ability to think beyond just a one sentence requirement and related test steps is part of the inherent skill which is a core need for exploratory testers. A well-executed exploratory testing relies on the skills of the person. The tester uses his skills to approach the problem and controls the process. The tester continuously implements the feedback received from the previous test. So we can say that exploratory testing is highly interactive and is an approach that allows in creating test designs when new information is discovered.<\/p>\n Some of the best practices during exploratory testing are to define test charters, test design heuristics, and time boxing. These techniques will put some general guidelines around the testing being done and it gives a structure to define its success.<\/p>\n Test charters give exploratory testing sessions a mission without being authoritarian.<\/p>\n Test charters outline:<\/p>\nSkills Needed for Exploratory Testing<\/strong><\/h3>\n
Structured Exploratory Testing <\/strong><\/h3>\n
Best Practices for\u00a0Exploratory Testing<\/h3>\n
\n