Why I’m sharing this again
I wrote this post in 2014 for the AppRiver Developer blog. The site went away after their first acquisition, and this mnemonic stayed with me.
Back then, I wrote as a tester. I have worn different hats since then, and in all subsequent roles, my context-driven test experience positively influenced and deepened dialogue. This mnemonic was helpful with teammates, my upline, and direct reports. My takeaway: test mnemonics are for everyone.
Anyone who raises a concern faces the question a tester faces. So, why should we care? A mnemonic like HICCUPPS gives you a quick way to check your own thinking before you speak. It also offers shared language to connect your concern to something your teammates already value.
The post below is almost exactly as I wrote it. I’ve only made the mnemonic easier to spot. Afterwards, I share what I’d add today: connection through explainability. And as usual, there is a musical accompaniment! 😉
Hiccups, sugar, and bug advocacy (2014)
When I was a little kid, I would occasionally get hiccups that rocked my diaphragm so badly my shoulders ached. “Popsicle” Grandma called during one of these uncomfortable bouts. I answered the phone with an embarrassingly audible gasp. I heard her smile through the phone as she spoke with her soothing southern accent, “You know what will get rid of those? A tablespoon of sugar under the tongue will fix you right up.” Scooping straight from the sugar canister was against the rules in our house, but with her encouragement, I decided to risk it. I tried the purported antidote, and she was absolutely right.
How do you remedy uncertainty about whether or not you found a bug? When I find a bug, I need to be really sure that I actually found an issue or potential problem, so there is no doubt in the minds of the reader of the bug report. I need to clearly, concisely, and convincingly communicate to the developer and product management teammates why I think there is a problem, so they want to fix it right away! One technique I use to determine if I found a bug is an internalized list of test oracles described in Michael Bolton’s article, Testing without a Map [PDF]. I use this list, originally created by James Bach, to examine general consistency heuristics:
- History – Is this version of the system consistent with prior versions?
- Image – Is this consistent with an image our organization wants to project, with our brand, or with our reputation?
- Comparable Products – Is the system consistent with systems that are in some way comparable? This includes products in the same product line, competitive products, services; or products not in the same category, but process the same data; or alternative processes or algorithms.
- Claims – Is the system consistent with things important people say about it in writing (help documentation and marketing materials) or in conversation (hallway and coffee mess chatter).
- Users’ Desires – Is the system consistent with ideas about what reasonable users want?
- Product – Are elements of the system (or product) consistent with comparable elements in the same system?
- Purpose – Is the system consistent with explicit and implicit uses to which people might put it?
- Statutes – Is the system consistent with laws or regulations relevant to the product or its use?

Image Photo by Pea on Unsplash
I use this list to help me figure out if there is a fly in the sugar bowl, so to speak. If I cannot relate the issue to one or more of these consistency heuristics, then I can put the issue to rest, and not waste anyone’s time. On the flip side, I am usually very effective in getting bug changes made since I can explain why the bug matters using one or more of these oracles. As Bolton explains in Oracles [PDF], multiple oracle heuristics may apply, and some of these may contradict one another: A product owner’s decision on what to do about the problem can be influenced by which oracles are applied. Since our role as testers is to provide credible information, we may choose to use different oracles to temper our test framing or bug advocacy.
Test findings can trigger the following emotions: fear, anxiety, and excitement. Interestingly, these emotions can cause hiccups. Over time and with practice, this list can serve as a useful tool to double-check your logic and grow your skills and confidence in the art and science of bug advocacy.
What I’d add today: connection through explainability
The oracles list extends to FEW HICCUPPS. E is for Explainability: “We expect a system to be understandable to the degree that we can articulately explain its behaviour to ourselves and others”. As shared via Bolton:
Aleksander Simic, in a private message, suggests that the explainability heuristic extends to more members of the team than testers. If a programmer can’t explain code that they must maintain (or worse, has written), or if a development team has started with something ill-defined and confusion is moving slowly through the product, then we have reason to suspect, investigate, or report a problem. I agree with Aleksander. Any kind of confusion in the product is an issue, and issues are petri dishes for bugs.
Over the years, I’ve leaned on explainability. Connection is the part I did not have words for in 2014. When you can explain why something matters or might matter, people lean in instead of bracing, and over time, that builds trust between teams. Here are a few real-world examples:
- (E, H) Because of the tremendous turnover and layoffs in engineering, lack of documentation, uncertainty around the codebase, and recent adoption of AI-assisted coding, you ask, “Help me/us understand the logic you developed for this piece of the pipeline. How about you walk us through it and we whiteboard it together?” Outcome: We surface assumptions that turn out to be invalid. We discover fundamental flaws. We collectively grow our system knowledge, avoid adding to the fear, uncertainty and doubt (and the bugs) in this area, and avert churn and rework.
- (H) When you “walk the floor” and notice something really weird in the logs coming from your authentication and authorization microservice. The log weirdness was not happening prior to the deployment. Outcome: You share this finding, and voilà, you have uncovered a security issue that is patched immediately and prompts a blameless post-mortem.
- (H ,I ,U) When you notice in the UAT environment that the UI flow is inconsistent with the previous version; the last step is now confusing to you, someone intimately familiar with the flow. The confusion is compounded because you see that someone has introduced a third-party 3P app into the flow. What was the rationale for introducing the change? While yes, it ‘still works’, you are worried that in the wild, the support team is going to see an uptick in call volumes. Also, it looks bad to have a 3P competitor’s branded logo component in the UI. You are pretty sure the COO is going to frown at this. Outcome: C-suite has the team roll back the undesirable change.
Whether you’re filing a bug, pushing back on a requirement, or flagging a risk to leadership, two questions help:
- Which oracle(s) apply here?
- Who cares about that, and how do I explain it to them?
If you can’t answer the first, you might have a preference rather than a problem. If you can answer both, you are more likely to facilitate an informed stakeholder decision.
What mnemonic do you keep in your head? I’d love to hear it.
Further reading & listening
- Michael Bolton’s extension of his HICCUPPS oracle list blog post, FEW HICCUPPS.
- Cem Kaner’s Bug Advocacy: How to Win Friends, Influence Programmers, and SToMP BUGs [PDF].
- For your listening pleasure, fun funk-rock & soul from Nikka Costa’s, “Everybody Got Their Something” [YouTube], [Spotify]
P.S. Understanding, and through it connection, is my ‘something.’ My ‘why’.