8.5.3. QA Strategy

🔍 What is Exploratory Testing? Exploratory testing is simultaneous learning, test design, and execution, where testers explore the application without predefined scripts.

Exploratory testing is a type of testing where testers actively engage with the application to learn about it while simultaneously designing and executing tests. Unlike traditional testing, where specific test cases are written beforehand, exploratory testing allows testers to adapt and respond to how the application behaves in real-time, which can lead to discovering unforeseen bugs or issues.

Think of exploratory testing like a detective solving a mystery. Instead of following a rigid script or checklist (like a predetermined list of suspects), the detective investigates the scene, gathers clues, and interacts with witnesses, allowing them to uncover new and unexpected evidence that could lead to a resolution.

🎯 Why it’s valuable in Agile: ● Uncovers edge cases that scripted tests may miss ● Ideal for early-stage builds and UI-rich applications ● Helps find usability issues, confusing workflows, and minor glitches

Exploratory testing is particularly beneficial in Agile environments because it allows for flexibility and adaptability. It can effectively uncover edge cases that may not be addressed by traditional scripted tests. This approach is especially useful during the early stages of software development or when testing features rich in user interfaces, as it enables testers to identify usability issues, confusing workflows, and minor glitches that could negatively impact user experience.

Consider a new restaurant's menu testing. If you only follow a fixed formula for food reviews (like a scripted test), you might miss out on how the ambiance affects diners’ experiences. However, if you explore and taste the dishes in various settings, you might discover that some combinations work better than others, leading to a more refined and enjoyable dining experience.

🧩 QA Strategy: ● Use charter-based sessions (e.g., “Explore cart checkout flow for invalid inputs”) ● Record observations and raise issues with screenshots/videos ● Combine with automated and scripted testing

To effectively implement exploratory testing, QA teams can use 'charter-based sessions' that focus on specific areas of the application, such as testing how the shopping cart behaves with invalid inputs. During these sessions, testers should document their observations and any issues they encounter, ideally including screenshots or videos for clarity. This form of testing works best when combined with automated tests and scripted tests to ensure comprehensive coverage of the software's functionality.

Think of exploratory testing as a guided tour of a new city. While being given a charter (a map with points of interest), the guide can explore the unique and obscure spots (like hidden coffee shops) not mentioned in the typical tourist brochures (which are like scripted tests). By documenting these discoveries, the visitors get a richer experience and a more complete view of what the city offers.

--