Interactive tool · Part 4
Executing a run is not clicking around until something breaks. It is running known cases against a known build and recording what actually happened, with the right status, every time. Read each case, reveal what the app did, and mark it. Passed is not the only honest answer, and Blocked is not Failed. I will coach you on the call a careful tester makes.
App under test
Load a case, step through the mock app state, then record the status from what you observed. The point is not to guess the right answer. It is to practise the discipline of evidence first, status second.
Start the first action to observe the app.
PreconditionsGuest user, store seeded with the eight launch products.
Expected resultAll eight products show, each with an image, a product name and a price.
Actual result (observed)All eight products render correctly, each with an image, name and price.
PreconditionsGuest user on the gallery page.
Expected resultThe Ackee Patty product detail page opens.
Actual result (observed)The page navigates to a 404 "Page not found" screen instead of the product detail page.
PreconditionsGuest user, store seeded with the eight launch products.
Expected resultEvery product shows its correct image.
Actual result (observed)Seven products show an image. "Sorrel Punch" shows a broken-image placeholder on the gallery, though the image loads on its own detail page.
PreconditionsGuest user on a product detail page.
Expected resultA confirmation shows and the cart count goes from 0 to 1.
Actual result (observed)A confirmation toast appears and the cart count updates to 1.
PreconditionsGuest user with one item in the cart.
Expected resultThe order is placed and a confirmation number is shown.
Actual result (observed)The payment sandbox is down in staging, so the card step returns "service unavailable". You never reach order confirmation.
PreconditionsGuest user with one item in the cart.
Expected resultThe gift-card payment flow opens.
Actual result (observed)Gift cards are not part of this release. The feature is off behind a flag and the option is not shown.
Field guide
You ran the case and the actual result matched the expected result. Nothing to report.
You ran the case and the product behaved wrongly. This is the only status that should come with a bug report.
You could not run the case to its end because something was in the way. Record what blocked it. It is not a product defect.
The case was consciously not run, usually because it is out of scope for this build. Honest, as long as it is a decision and not an accident.
