Software Testing Tutorial #29 - What is Exploratory Testing

Summary

This tutorial explains the concept of exploratory testing, a method used in software testing that involves exploring the application without prior documentation or structured test cases. The speaker highlights its unstructured nature, its effectiveness in uncovering bugs that may be missed by traditional testing, and its value when time is limited or early feedback is needed. Key steps like bug classification, creating a test charter, timeboxing, and reviewing results are discussed, providing a practical approach to conducting exploratory testing. It's presented as a useful technique for both interviews and real-world projects.

Takeaways

• 📘 Exploratory testing involves exploring the software without upfront documentation or predefined test cases.
• 🧑‍💻 This testing method was introduced by Cam Kaner in his book 'Testing Computer Software'.
• 🌀 It is random, unstructured, and can reveal bugs that might be missed by structured testing methods.
• ⏳ Exploratory testing is useful when there's a time constraint and structured testing cannot be fully completed.
• 🔄 It is applied when early feedback is needed, allowing key issues to be uncovered early in development.
• 🔍 As testers explore the software, they may find new defects and identify additional test cases that were not initially considered.
• 📝 Exploratory testing often begins by classifying bugs and identifying the modules with the most defects for further testing.
• 📄 Test charters are used in exploratory testing to outline the scope, time limit (timeboxing), and objectives of the test.
• 🕒 Timeboxing is crucial in exploratory testing, ensuring tests are conducted within a specific timeframe to maintain efficiency.
• 🔑 The primary advantage of exploratory testing is its flexibility, as it allows testers to approach the software from various perspectives and uncover defects that structured testing might miss.

Q & A

What is exploratory testing?

Exploratory testing is a software testing technique where testers explore the application without predefined test cases or extensive documentation. Testers interact with the software to identify defects, writing test cases and documenting their findings as they proceed.

Who introduced exploratory testing and in which book?

Exploratory testing was introduced by Cem Kaner in his book 'Testing Computer Software'.

How is exploratory testing different from structured testing?

Unlike structured testing, which involves predefined test cases and formal documentation, exploratory testing is unstructured and random. Testers explore the software freely and document defects as they find them. This approach helps uncover defects that may be missed in structured testing.

When should exploratory testing be used?

Exploratory testing is most useful when there is limited time to test the software, when early feedback is required, or when testers want to discover new test cases and defects. It’s especially helpful for finding issues that structured testing might miss.

What role does the tester's mindset play in exploratory testing?

The tester's mindset is crucial in exploratory testing. Testers need to think from the perspective of end users and other business processes, which helps them explore different paths within the software, potentially uncovering issues that would not be identified through a structured approach.

What is a test charter, and why is it important in exploratory testing?

A test charter is a document used in exploratory testing that outlines what needs to be tested, the time limits for the testing session, and other relevant details. It helps provide a framework for the testing session while still allowing flexibility and creativity.

What is meant by 'time-boxing' in exploratory testing?

Time-boxing refers to setting a fixed time limit for exploratory testing sessions, such as 30 minutes or 1 hour. This ensures that testing remains focused and productive, preventing testers from spending unlimited time on any one task.

What is bug classification in exploratory testing?

Bug classification involves analyzing existing defects in a project to identify the modules or areas with the most issues. These modules are then prioritized for exploratory testing, allowing testers to focus on high-risk areas.

How can exploratory testing help find new tests and defects?

As testers explore the software, they often discover new paths, scenarios, and interactions that weren’t considered during structured testing. This helps in identifying new test cases and finding defects that structured testing might miss.

What are the key steps involved in conducting exploratory testing?

The key steps include bug classification (identifying areas with the highest defects), preparing a test charter (outlining what to test and for how long), time-boxing the testing session, and reviewing the results after the session.