Every day, I notice fewer people sharing their projects here.

A couple of months ago, build in public felt unstoppable: everyone was posting updates, numbers, roadmaps. Now? The hype seems to be fading or maybe makers are just shipping quietly.

I noticed that Product Hunt discontinued the teaser / coming soon section this week, and I m curious if it did help you build genuine traction? 

My take (from hunting PH launches):

Most Playwright failures aren t real bugs - You rerun, you scroll CI logs and eventually retry passes.
That's how another hour gone and productivity wasted. In this process Reviews will stall because no one knows if failure is legit or it's flaky tests.

After years running a QA agency, I kept seeing the same pattern across teams. Red builds full of flaky noise. Custom fixes did not scale. So we turned our playbook into SaaS.

We built @Testdino to solve this problem. It reads your execution reports and highlights what matters most right now.

It consolidates different test runs into a single place, creates role-specific dashboards, and prepares historical trends and key metrics to reduce debugging time and reveal meaningful patterns.
Our machine learning models and customized LLMs, trained on thousands of test runs, tag each test failure as Bug, Flaky, or UI Change with a confidence score.
Everything, including runs, PRs, branches, and environments, is kept in one clear view.

Hi Product Hunt community!

I'm Pratik, founder of Testdino - and this is my first post here!

My story: 12+ years in QA taught me that flaky tests are every developer's nightmare. You know that feeling when your CI fails, you rerun the same test, and it magically passes? Then you spend hours wondering: "Is this a real bug or just being flaky?"

The problem: Teams waste 6-8 hours per week playing detective with test failures. Even with perfect automation, we're still debugging failures manually like it's 2010.