Why I built six automation kits (and what I wish I’d had on day one)
A senior SDET shipping production-ready Playwright, Selenium, and Cypress automation kits — across TypeScript, C#, Python, and Java — that I wished existed earlier in my career.
##A framework born from real production pain
20+ years in QA. Started as a manual tester, moved into automation, led automation teams, then settled into SDET work — the role where you write the framework other engineers test against. I’ve seen good test automation save companies millions in production bugs, and I’ve seen bad test automation get ripped out three times in five years. These kits are the patterns that actually held up.
Obsessive about structure. I can’t leave a directory messy, and I write docs that explain not just what but why. Test architecture is genuinely fun for me — the kind of work where I want every choice to have a note, every edge case a section, every CI step a comment. The kits reflect that: they’re the framework I wish someone had handed me on day one of a hard project.
Tired of the two extremes. Most QA tooling content is either too academic — Selenium docs that explain every API and no patterns — or too marketing-fluff — vendor SaaS promising AI-powered codeless utopia for $200/seat/month. I wanted a third thing: real production frameworks, written by someone who’s shipped them, sold at a price a senior engineer can expense without a meeting.
I build what I wished I had. Every kit is the framework I wish had been waiting for me when I joined a new team and inherited a flaky Selenium suite from 2014. Today there are six kits live — Playwright Pro in TypeScript and C#, Cypress Pro in TypeScript, and Selenium Pro in Python, Java, and C#. Each one is opinionated, documented, and ships with passing CI on day one.
If you’ve ever inherited a flaky test suite and wanted to throw your laptop into the sea — these kits are for you.