Testifly launch
AI-powered end-to-end full web testing in minutes
85 followers
AI-powered end-to-end full web testing in minutes
85 followers
From URL to fully automated end-to-end web testing in minutes! Testifly makes end-to-end web testing fast, stable, and low-maintenance. After providing your URL and logins, Testifly creates reliable tests in minutes using AI that understands real user flows and adapts to UI changes. No long setup, no brittle scripts, fewer flaky failures. Built on modern browser automation and designed for real production apps, CI pipelines, and fast-moving teams.
This is the 2nd launch from Testifly launch. View more

Testifly
Launching today
CTOs and founders with small teams and no time or resources to test and maintain. Connect your web app and Testifly does the rest. Discovers flows, writes tests, self-heals, explains failures with video. Zero prompting. Zero maintenance. 30-day free trial.









Free Options
Launch Team / Built With

AWS Startup AdvisorPersonalized AWS guidance that meets you where you’re already building
Promoted



Hey Product Hunt! 👋 I’m Amihay, founder and CEO of Testifly.
Testifly is for CTOs, founders and small teams that ship a web app without a dedicated QA person, and want their time to go to building. It’s also for QA testers, developers and product managers who are tired of writing and fixing tests. If you’ve ever said “I hope this deploy didn’t break anything,” this is for you.
The problem
I’ve worked in software for 25 years. On almost every project, I saw the same thing: we never got a good return on our testing investment.
We spent a lot of time writing test automation. Then the code changed and the tests broke. One test took a week to turn green again. In that week, another test turned red.
Then AI came, and it was chaos in a different way. It wrote tests that were not relevant. When a test failed because of a real bug, the AI “fixed” the test to match the bug instead of reporting it. And it created about 2,000 tests that nobody could manage.
The solution
So we built Testifly 🚀 - an autonomous AI QA solution for web apps. You connect your web app, and that’s it. Testifly does the testing work for you.
Before and after
Before: testers wrote test cases by hand, fixed them after every change, and argued about who owns the red tests.
After: Testifly does it all for you, and you don’t write or maintain anything.
Why not just use your own AI coding agent?
You can ask a coding agent to write tests. But you still own them afterwards: you prompt it, review what it wrote, and fix what breaks. The maintenance work comes back to you.
With Testifly, that part is handled:
No prompting, reviewing or babysitting. It does the whole cycle.
When a test fails, it tells you something may be broken.
You can stay focused on building. Your time goes to the product, not to a test suite.
What you get
It finds your user flows on its own
It creates the tests
It runs them on every deploy and on a schedule
It keeps the tests up to date when your app changes - QA with zero maintenance
Testifly catches broken signups, failed forms and regressions, without adding work for you or your team.
Try it - free to start, no credit card required 👉 https://testifly.dev/product-hunt
🎁 PH special: upgrade to a paid plan today and get your 2nd month free.
What I’d love from you 💬
Please try Testifly on your own app and tell us what worked, what broke and what is missing.
And one question: what is your single biggest challenge with testing today? The more detail the better. Your answers will directly shape what we build next!
Thank you to our team, who worked hard to get here. Thank you to @rohanrecommends for hunting us. And thank you to the Product Hunt community for giving new products a chance.
I’ll be here all day to read and answer every comment. We’re still early, and I’m excited about what comes next.
Amihay
Founder & CEO, Testifly
@rohanrecommends @amihay_schwarz1 Can it handle complex user flows and catch bugs after every update?
@shivam_kushwaha16
Yes. Testifly finds your app's flows by itself, including multi-step ones behind login (username/password, SSO, magic link). It then runs the tests on every release and environment and can block your deployment through CI/CD. It updates tests as the UI and features change, distinguishes real regressions from harmless changes, and provides a video and root-cause report for each failure.
My biggest one is probably the break that only shows up in production. Last week a deploy of ours went out without its production env file, and our checks let a blank AI key straight through. The deploy said success but new signups were broken. I only caught it because I had an agent sign up as a brand new user in a real browser.
@simon_moxon
That failure is exactly what Testifly is built to catch. A green deploy only means the code shipped. It doesn't mean signup works. Testifly signs up as a new user in a real browser, as your agent did, and fails if the flow breaks. A blank AI key would have failed that signup test right after the deploy.
You can also run Testifly against production on a schedule, using keep-alive tests. It checks the signup flow every few minutes or hours, not only at deploy time. If it breaks, you get a Slack alert with a video and a root-cause report, so you find out in minutes, not days.
Testifly can't see your env file or your deploy config. It checks what a real user would experience, and that's where this kind of bug shows up.
Hi,
A couple of questions:
How are use cases defined? Automatically?
What are the limitations of using it?
I have a 2fa system. Is it an issue?
Does it require to know the site internals? The source code itself?
Hey Product Hunt! 👋 I’m Eyal, co-founder and CMO at Testifly.
@amihay_schwarz1 covered the product, so I’ll add the angle I know best.
I’ve been in B2B SaaS marketing for about 13 years. More than once, I watched a campaign bring good traffic to a signup page that was broken after a deploy. Nobody noticed for days. The budget was spent, and the leads were gone.
That’s a big part of why Testifly clicked for me. We also built it the way I believe software should be sold: self-serve, great customer support, no demo long demos or sales call. Just connect your app and see for yourself how it can help you.
🚀 Try it out. It's free to start and no credit card required 👉 https://testifly.dev/product-hunt
🎁 PH special: upgrade to a paid plan today and get your 2nd month free.
I also want to thank @rohanrecommends for his advice, feedback and support on this launch.
I’ll be around all day with Amihay. Questions, feedback, or “this didn’t work on my app” - all welcome 🙏
Eyal
Co-founder & CMO, Testifly
Keeping a history of what a test used to expect would matter here. It would give the team a way to check that a real regression hasn't become the new passing result.
The concern is fair @oleksii_sekundant. A tool that heals itself could, in theory, accept a broken result as the new normal.
Testifly's design guards against this. When a test fails, it separates a UI change (a moved button, a new selector) from a real behavior change (a wrong checkout total). It heals only the first kind. The second kind is flagged as a regression and stays red until someone looks at it. Each run also keeps its video and root-cause report, so you can see what happened and when.