QA architect, automation builder, and former lab tech.

I'm Robert Boles — a senior SDET with 14 years turning messy enterprise releases into something teams can actually trust. I've cut a regression cycle in half, built the QA governance other teams run on, and brought AI into test generation without losing the plot. This site is where that work gets generalized into something you can reuse.

Why this site exists

This is a public knowledge base for practical QA systems — written by someone who does this at enterprise scale in property & casualty insurance, not someone narrating theory. The goal is to turn 14 years of field experience into reusable guidance: risk-based regression, governance models, root-cause analysis, release readiness, and metrics that drive decisions instead of theater.

It's also a builder laboratory. Side projects like Vox Mana show how I think about data contracts, source governance, visual QA, and keeping AI-assisted work from drifting.

What I write about

Risk-based regression and release readiness
Test automation architecture that survives change
QA governance, operating models, and RCA
AI-augmented test generation, without losing control
Metrics and dashboards leaders actually read
Builder notes, handoffs, and Codex workflows

The short version

Fourteen years in QA — from automation tester to senior SDET and QA architect across enterprise property & casualty insurance (policy, claims, integrations, rating & quoting). I've compressed a regression cycle from roughly two months to one, stood up the test-services governance other teams run on, and built the dashboards leadership uses to make release calls.

Before tech: a U.S. Air Force medical laboratory technologist — Staff Sergeant, Secret Clearance — where triage, quality control, and staying calm under pressure became habits I never unlearned. B.S. in Network Security (CAE/NSA-endorsed). ISTQB certified.

Operating principles

How I think about quality

These principles guide the articles, projects, and templates on the site.

Confidence is built, not declared.

A green status only matters when the evidence behind it is understood.

Automation is a signal system.

The value of automation is not the number of tests. It is the speed and clarity of feedback.

Documentation should recover context.

Good handoffs make future work safer because they preserve why decisions were made.