Explaining Exploratory Testing with a Real-Life Scenario:
A Child Sent to Buy a Product at the Market
Exploratory testing is like going shopping for groceries without a specific list. Here’s how it works in simple terms:
Scenario: A Mother Sending Her Child to Buy Milk at the Market
Background: A mother sends her child to the local market to buy a carton of milk. This task involves several steps, choices to make, unforeseen issues, and potential unexpected situations, much like exploratory testing in software.
Step 1: The Task
Before the child leaves, the mother gives a brief overview of the task: “Go to the market and buy a carton of milk.” This is similar to setting a goal for exploratory testing. The child knows the main objective but not every detail of how to achieve it.
Step 2: Prepare for the Task
- The child ensures he has money with him in order to execute the task.
- The child is aware of the goal and some requirements to achieve it but remains open to exploring different paths to achieve it.
- The child thinks of which market he should go to and other alternatives
Step 3: Explore the Market
- Upon arriving at market, the child starts looking for stores that sell milk and also pays attention to signs, prices, and other products.
- The child notices the layout of the market, which shops have discounts, and where the dairy section might be.
- The child might ask a shopkeeper for directions or check different brands of milk to compare prices and quality.
This exploration is akin to exploratory testing, where the tester navigates through the application without a strict script, observing and interacting with various elements.
Step 4: Make Decisions on the Fly
The child faces several decisions:
- Choosing the Shop: The child sees multiple shops selling milk. Which one looks the most reliable?
- Choosing the Product: The child sees different types of milk, some are liquid while others are powdered milk. Which one looks the most reliable?
- Evaluating Options: Some cartons are cheaper but near their expiration date. Should the child buy a fresh but more expensive one?
These decisions are like the tester deciding which areas of the software to explore deeper based on initial findings. If you find a part of the application that seems confusing, you spend more time testing it to understand its behavior.
Step 5: Handle Unexpected Situations
The child encounters an unexpected situation: the usual brand of milk is out of stock or the only type of milk available is powdered . The child has to decide:
- Alternative Solution: Should they buy a different brand, or call the mother for advice?
This mirrors handling unexpected issues in exploratory testing, where the tester finds bugs or behavior that wasn’t anticipated and needs to decide how to proceed. If you encounter an error or something that doesn’t work as expected, you try different ways to reproduce it. You might find features that weren’t documented or that behave differently than anticipated.
Step 6: Completing the Task
Finally, the child buys a carton of milk, perhaps not exactly as initially planned but with all necessary considerations made. They return home with the milk and inform the mother about their experience, including any issues faced.
- You finish the session with valuable insights about how the application works, what issues need to be addressed, and potential areas for improvement.
- Your findings help improve the overall quality of the software.
#Exploratorytesting #SoftwareTesting #QualityAssurance,
#TestersJourney,
#TestingMindset #QACommunity,
#TestingWisdom #QaTechBro