I've been a frontend dev for a few years now, and there's a pattern I kept seeing across almost every small team I worked with.
New feature ships. Everyone's happy. Then three days later something completely unrelated breaks and nobody caught it.
Not because the QA testers didn't know what to test. They did. They had the test cases written, they understood the flows, they knew exactly what needed a smoke test after every deploy.
The problem was always the same: automating that required Playwright or Selenium, and that was "a dev thing". And the devs were busy shipping the next feature. So the smoke tests stayed manual, got skipped when things got hectic, and eventually everyone just hoped nothing broke between sprints.
I watched this happen enough times that I started building something about it.
What I built
Flow Testing is a drag-and-drop builder that lets anyone; QA testers, PMs, whoever does the clicking create and run real Playwright tests without writing code. You connect nodes visually (navigate, click, fill, assert) and it runs against real browsers under the hood.
What's working today:
- Visual canvas with nodes for navigate, click, fill, assert
- Runs on actual Playwright (Chromium, Firefox, Webkit)
- Trace viewer with screenshots and network logs when something fails
- API mocking for edge cases
- AI Agents (Planner, Generator & Healer) still improving
Why I'm posting this
The product has a paid plan but I'm more interested in finding people who will actually use it and tell me what's broken, what's missing, or what doesn't make sense.
If that's you, free month on me. Just reach out.
https://flowtesting.io
Top comments (0)