Built for testers who learn by doing.

I built Locator League because learning test automation shouldn’t feel like reading a manual.

By day I’m a test automation engineer working on an enterprise risk assessment platform. I’ve designed large test suites covering complex UI workflows, risk checks and end-to-end flows, and written the automation strategy that turns them into a Python, Playwright and pytest setup. I’ve seen what makes automation brittle and what makes it hold up.

The hardest part of automation is rarely the framework. It’s the small, repeated decisions: which locator to choose, why a test passes locally and fails in CI, when to wait and when to assert. Those skills come from practice, not documentation. Most learning resources still hand you a wall of text and a “hello world” example.

Locator League is my answer to that. It’s a gamified arena where you level up by solving real automation challenges. You pick locators, debug broken tests and work through scenarios that resemble what you’ll see on the job. You get instant feedback and a reason to come back tomorrow.

Along the way I’ve been building tooling around test reliability, including a flakiness detection API that scores unstable tests from CI results. I’m also working toward AI engineering, and I’m interested in where it meets quality engineering. Locator League sits in the same place: helping testers build real skill, faster, and, in future, with help from AI where it’s useful.

If you’re a manual tester making the jump to automation, or an automation engineer who wants to sharpen up, welcome to the league.