About

I didn’t come to software testing through a computer science degree or a textbook definition of QA. I came to it through curiosity, through asking hard questions, and through caring deeply about whether things actually work—for real people, in the real world.

Before I was a tester, I was a pastor (still ordained, still serving where I can). I’ve spent years sitting with people in hard moments, listening for what’s not being said, and helping communities pay attention to what matters. That background still shapes the way I approach testing. I believe quality is about more than just clean builds—it’s about trust, communication, and human experience.

I’ve been working as a test engineer for several years now, mostly in startups and mission-driven tech companies. I specialize in mobile testing (iOS and Android), API testing, end-to-end automation, and exploratory testing—the kind that asks not just “Does this meet the spec?” but “What happens if I push here?” I’ve built native test frameworks, debugged flaky CI pipelines, documented edge cases nobody expected, and advocated for users who couldn’t speak for themselves.

I’m currently working at a sports and event ticketing platform, helping improve the reliability of our fan-facing mobile app. I’m also learning more about AI-assisted testing, test strategy at scale, and how to build systems that support real collaboration across engineering teams.

I started Testing Tester because I wanted a place to reflect—not just on what works technically, but on what this work means. What it asks of us. What it reveals about us. What it’s like to care about quality in a world that mostly wants to ship faster (although I do love delivering on time!).

You won’t find hype here. Just honest notes from the field—tools I’ve tried, questions I’m sitting with, and the occasional post about the deeper stuff: burnout, motivation, purpose, and the quiet glue work that holds teams together.

If any of that resonates with you, I hope you’ll stick around.

— Beau