There’s a version of quality assurance that everyone already believes in and almost no one is practicing. Ask a room full of testers what good testing looks like and you’ll get the same answer, more or less… curiosity, judgment, a feel for where the system is lying to you. Ask what they did yesterday and you’ll get something else entirely. A script ran. A checkbox got checked. Nobody investigated anything.
I’ve spent the better part of forty years inside that gap, and I used to think it was a discipline problem. Testers getting lazy, or organizations getting cheap. It isn’t. It’s a design problem, and the design was set decades ago, by people who were solving for throughput because throughput was the thing that was scarce. It worked, for a while. It’s still the operating system underneath most QA functions today. And it’s quietly bankrupting the craft it was built to protect.
That’s the starting point for a white paper I’ve been calling The New Beautiful Testing. It just came back from a peer review cohort I’m genuinely proud of… people who’ve spent careers doing this work and who pushed back hard enough to make the thing better. What emerged isn’t a manifesto. It’s closer to a diagnosis, followed by an architecture.
A few of the ideas, without giving away the mechanics:
There’s what I call the Craft Death Spiral, the slow, self-reinforcing process by which an organization’s testing gets shallower every quarter, each cut justified by the last one, until “testing” means something almost unrecognizable from what it once did.
There’s Verified Fragility, the uncomfortable state where a system passes everything you asked it to and still isn’t safe to touch, because what you asked it was never the right question.
There’s a Verification Tax, the cost that gets paid regardless, either up front by people who investigate, or later, compounded, by everyone downstream of a release that shouldn’t have shipped.
And there’s a way out that isn’t a return to some romantic pre-automation past. I call it the General Contractor model, and it reframes what a QA function is actually for in a world where the tools have changed but the underlying discipline hasn’t.
None of this is theoretical for me. Some of the oral history behind it comes from a project I dissented on years ago, one that got built anyway, then got independently evaluated, then got killed. Being right didn’t feel like winning. It felt like watching a preventable thing happen in slow motion. That’s a large part of why this paper exists.
I’m not going to walk through the whole framework here. That’s what the document is for, and it earned its length the hard way. But if the shape of this problem sounds familiar… if you’ve felt that gap between what your team believes about testing and what your team actually does… it’s worth your time.
The New Beautiful Testing is available now to anyone who wants the full framework right here on QAMeditations.com. Download or subscribe!