I'm a QA engineer who got laid off, so I spent 3 months building a tool that generates Cypress/Playwright test frameworks from one command
Some context: I've spent 10 years in QA automation. Got caught in the layoffs earlier this year. Instead of just grinding LeetCode, I built the thing I always wished existed.
The problem: setting up a Cypress or Playwright framework from scratch takes days. Config files, fixtures, page objects, support files — you lose a week before you write a single real test. Every QA engineer I know has rebuilt this same scaffolding a dozen times.
So I built QA Smith AI. It's a CLI tool. You point it at your app, give it your acceptance criteria (from a Jira ticket, a file, or just pasted in), and it generates a complete production-ready framework — page objects, fixtures, config, and actual tests. One command.
The demo above shows it generate a full test suite from acceptance criteria, start to finish.
It's not launched yet — I'm collecting a waitlist while I finish the payment side. But I'd genuinely love feedback from other builders here, especially:
- Does the "one command, full framework" pitch land, or does it sound too good to be true?
- For anyone who's shipped dev tools — what surprised you most going from "works on my machine" to strangers paying for it?
This is my first real product launch after years of building for other people's companies. Tearing it apart is welcome.
Posted Jun 12, 2026, 11:41 PM UTC