Testing journey - research, projects, conferences and article library

Michal Buczko - Quality Adventures

Subscribe

BowSmith

QA or the Highway 2025: the conference was one stop on a three-week research trip

QA or the Highway 2025: the conference was one stop on a three-week research trip

In 2025 I went back to Columbus, but the conference wasn't really the destination. It anchored a three-week US road trip that doubled as user research for an app I hadn't shipped yet.

BowFest 2026: what a field full of archers told me that no test suite could

BowFest 2026: what a field full of archers told me that no test suite could

BowFest 2026: what a field full of archers told me that no test suite could

I lost my favourite tool and shipped faster anyway

I lost my favourite tool and shipped faster anyway

Fable was the best tool in my stack. Then it went unavailable, and I had to give the architect seat to Opus Max on short notice.What I got was faster hand-offs. This is the post about why — and why I think losing the tool made the work better, not despite the constraint but because of it.

BowSmith, one feature, fully orchestrated: the case study

BowSmith, one feature, fully orchestrated: the case study

This is one feature in BowSmith, shipped end-to-end through Opus Max (architect) → Opus (orchestrator) → Sonnet (workers), with the numbers. Not a toy. A feature I'd have budgeted the better part of a week for if I'd built it by hand.

Where the three-tier stack was overkill: an honest retrospective

Where the three-tier stack was overkill: an honest retrospective

Not a victory lap the opposite. Where the stack was overkill, where the hand-off cost more than it saved, and the one-question filter I now run before I stand up the architect tier at all.

The RPIQ loop: where the architect tier actually sits

The RPIQ loop: where the architect tier actually sits

That methodology is the loop I've been running long before any of these models existed: Research → Plan → Implement → Quality. RPIQ. This post maps the stack onto it — and shows why the mapping, not the model, is the thing worth keeping.

CAST part 1: How a QA professional with zero iOS experience built a production app using AI – and what I learned about the future of software delivery

CAST part 1: How a QA professional with zero iOS experience built a production app using AI – and what I learned about the future of software delivery

I have spent 20 years in software testing and quality assurance. I knew almost nothing about iOS development. Zero Swift experience. Yet here I am, 18 months later, with a production-ready iOS app approaching alpha launch.