TestDino is highly praised for its Playwright-focused reporting capabilities, offering seamless CI/CD integration and AI-driven insights that enhance test automation efficiency. Users appreciate its compatibility with GitHub Actions and local setups, as well as its clear documentation. The platform's ability to classify failures and provide detailed historical data aids in improving test reliability. TestDino is particularly valued by Playwright users for its intuitive interface and actionable intelligence, making it a strong choice for teams seeking to streamline their testing processes.
Impressive work, Testdino team! I manage Playwright test projects for multiple clients. Do I need to buy a separate subscription for each one?
In our pipeline we run ~1k Playwright tests per commit. what is the expected processing time per run ?
question on retries. if a test fails once but passes on retry, does TestDino count that as flaky?
and if yes, do you expose a “retry tax” metric to show wasted minutes across runs?
@rinkesh_solanki Yes. “Pass on retry” is treated as flaky and it shows up in the flaky counts and trends. We also chart retry trends so you can see how often it happens. A single “retry tax” number is something we’re working on; for now you’ll see retry counts and their impact in the run details and over time in Analytics.
scaling curiosity: if my org has multiple projects across repos, can one dashboard unify them? OR do we create multiple orgs? also, how does billing work in such setups?
@riyaqa Keep one Organization for your company, then create a Project per repo. You’ll get a single place to switch between projects and read their analytics without mixing client data. If you work with clients, set up a separate Organization for each client to keep access and data clean. Billing is per Organization, so one invoice can cover multiple projects. We don’t merge data across different Organizations today; you can switch between them from the header.
🚀 Congrats on the launch! Love how TestDino uses AI to cut through noisy test failures and highlight real bugs vs. flaky tests—this will save teams tons of debugging time. 👏
Thank you @alpesh_vaghasiya2! That’s exactly what we set out to do. If you want to give it a spin, connect a playwright project and you will get labels and trends after your next run. We can share a sample project as well. If anything feels off, tell us and we’ll tune it. 🚀
Finally, a tool that keeps false test failures from slowing us down—TestDino keeps the focus on real quality.
Exactly, Kishan! That's the heart of what we built TestDino for. False positives and flaky tests can kill team momentum and make everyone lose trust in their test suite.
TestDino transforms Playwright test chaos into clarity—automatic failure diagnosis, root-cause insights, and flaky test tracking deliver measurable efficiency gains
Appreciate you breaking it down so clearly @shantilal_matariya - the automatic failure diagnosis and flaky test tracking really are the core pieces that make the difference.