BracketBoard

The Problem

BracketBoard is a tournament bracket builder I designed, built, and maintain myself. As a solo developer, every change risked silently breaking an existing flow, and manual click-through testing didn't scale as the product grew. I wanted the same safety net I build for clients: automated coverage that catches regressions before users ever see them, so I can keep shipping fast without breaking what already works.

The Approach

• ✓Built a Playwright e2e framework covering BracketBoard's core flows — bracket creation, seeding, and match progression.
• ✓Seeded test data API-first instead of bootstrapping through the UI, keeping the suite deterministic and fast.
• ✓Wired it into GitHub Actions for CI-driven regression on every push, so nothing merges without a green suite.

The Results

• ✓Manual regression dropped from hours to minutes.
• ✓Every push runs the full suite in CI — I ship solo with the confidence of a team behind me.
• ✓Dogfooding the exact automation practices I bring to client engagements: proof I run my own product the way I'd run yours.