8.5. Exploratory Testing in Agile

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

Exploratory testing is a flexible testing approach that combines the learning process of understanding a software application with test case creation and execution all at the same time. Unlike traditional testing, which follows a strict script, exploratory testing allows testers to investigate the software freely, using their creativity and insights to guide their testing effort, rather than merely following pre-written instructions. This means that tester's own curiosity and intuition play a significant role in uncovering problems in the software.

Think of exploratory testing like a treasure hunt in a new city. Instead of following a map, you wander the streets, observing interesting buildings and landmarks, maybe stumbling upon a hidden gem like a quaint cafe. This kind of exploration can reveal exciting discoveries that a set itinerary might miss, just as exploratory testing can uncover unique flaws or usability issues in software that scripted tests might overlook.

● 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 especially beneficial in Agile environments for several reasons. First, it uncovers edge cases—scenarios that happen at the limits of normal functioning—that might not be considered in predefined scripts. This is crucial in Agile, where rapid changes to software can introduce unexpected behaviors. Secondly, it is particularly effective for early-stage software builds or applications with complex user interfaces, where not all functionalities might be fully developed. Lastly, it allows testers to identify usability problems, such as unintuitive workflows or minor bugs, that could affect end-user experience, thus ensuring the product is both functional and user-friendly.

Imagine you're testing a new mobile app that helps users track their fitness goals. If you only follow scripted tests that check standard functions like login or inputting data, you might miss how the app behaves when a user tries to enter invalid information or how it looks when the screen orientation changes. Exploratory testing allows you to interact with the app organically and discover issues that might frustrate users, such as confusing navigation, ensuring that the app is not just functional, but also enjoyable to use.

● 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 guideposts called 'charters' that define specific areas or functionalities to explore during testing. For instance, a charter may instruct testers to examine the checkout process for scenarios involving invalid inputs. Additionally, testers should document their findings by taking screenshots or recording videos, enabling easier communication of issues to developers. Finally, exploratory testing should not stand alone; it can be enhanced by complementing it with automated tests and scripted tests to cover both broad and specific aspects of the application.

Consider a chef who is experimenting with a new recipe. They might have a basic idea of the dish (like a charter) but will taste and tweak the seasonings as they cook and explore new flavors. Similarly, exploratory testing allows testers to adapt and modify their approach based on what they discover, all while still having some automated tests (the tried-and-true recipes) ensuring fundamental functionality remains intact.

--