Testifly launch
AI-powered end-to-end full web testing in minutes
212 followers
AI-powered end-to-end full web testing in minutes
212 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

CloudflareDeploy serverless functions globally in seconds
Promoted



Can we schedule the tests just like we have a feature in Claude of "scheduled tasks"? If not, then this would be a good feature to add.
Yes @himani_sah1.
Testifly can run your tests on a schedule that you set, for example, every hour or every night. When a scheduled run fails, you get a Slack alert with a video and a root-cause report.
Congrats. Say if a test fails due to temporary network issue, not because there is a bug in the product. In this case, does Testtifly retry before reporting the issue?
@iamanantgupta Yes. We retry every failed test on the spot. If it keeps failing, Testifly investigates the root cause and gives you options, including "there was a temporary glitch in my app." The test runs again at its next scheduled time, for example, the next day. If the glitch is gone and it passes, the issue is marked as resolved.
Screenshots or video recording will always tell you more about the bug than a long error message. Good job on having that feature!!
Thank you! @shubham_ai_product_specialist, we agree. Every failed (and passed) test includes a video recording and a root-cause report, so you can see what the user saw and why it broke without re-running anything locally.
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
Including a video with each test failure is a great touch. Congrats on the launch!
Thanks @kylee
How does Testifly know which user flows are important enough to test automatically?
Congrats @amihay_schwarz1 & team.
Thanks for sharing @rohanrecommends :)
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.