Framework
A Comment Cannot Block a Story
A proposal to raise QA findings as story comments instead of tracked issues. It works for discussion and quietly breaks everything else — because a comment has no status and blocks nothing.
More posts
Field Notes
The Safest Story in the Sample
Two stories were picked as the safe baseline in a documentation audit because both had 100% approved coverage. One turned out to be the most defect-dense item in the sample.
Framework
A Guess With a Test Case Number
A checkbox that saves to the Account instead of the Order produced a false pass on the next run. Three ways sandbox state decides your result before step one.
Field Notes
The Bug That Only Appears When You Change Your Mind
A step discount came out duplicated — but only after deleting a promotion and a product and rebuilding the cart with a different bundle. The forward path was clean every time.
Field Notes
Correct by Coincidence
A discount amount is stored using the configured VAT rate. The approval check uses 20 hardcoded in Apex. Identical today, divergent the day an admin edits the config.
Framework
Read the Design Document Against Itself First
One technical design excluded a channel in §15.8 and advertised support for it in §16, and specified two mutually exclusive mechanisms as both in scope. Self-contradiction needs no environment to find.
Framework
Same Word, Different Flow
Cancel and Terminate sounded like one journey. Different actor, different entry point, different charging rules — and a test written with the wrong actor passes for the wrong reason.
Framework
The Negative Test That Can Never Fail
Two negative tests that looked mandatory and were worthless — one because the invalid state was architecturally unreachable, one because the rule was enforced by training, not by the system.
Framework
A Bug's "Done" Status Never Closes the Root Cause
Two defects recurred on seams that were already in the pattern bank. Both earlier fixes were applied at data level, and the RCA item was closed the moment the ticket went Done. What a real closure rule looks like.
Framework
Every Rendered Output Is Its Own Assertion
The same line item disappeared from an email and a PDF. Four porting bugs turned out to be one missing assertion. When a value fans out to several targets, each target is a separate test.