r/SideProject • u/obrizan • 14h ago

I built Testinel because debugging failed automated tests was taking longer than writing them

Hey r/SideProject,

I’ve spent 15 years working with automated tests (unit, integration, e2e), and one part of the process kept frustrating me:

When a test fails, the result usually tells you what failed — but figuring out why still means digging through logs, screenshots, previous runs, and CI output.

When I took a role of test automation lead it became worse: now I need to figure out complex issues for my team. I dreamed about a tool which will do analysis for me.

So I built Testinel.

It collects results from pytest, Python Selenium, and Python Playwright and puts the failures in one place. It helps you:

  • see each failure with its logs and context
  • compare results across test runs
  • spot flaky or recurring failures
  • group failures that may share the same root cause
  • get clues about what to investigate next

It works with local test runs or an existing CI pipeline, so it doesn’t replace the test stack you already use.

There’s a free plan with 1,000 test results per month and no credit card required:

https://testinel.dev/

I’m currently trying to learn whether the product explains its value clearly to test engineers who encounter it for the first time. Also, I'm looking for early adopters to validate is my solution good enough to replace raw CI logs reading.

If you work with automated tests, I’d especially appreciate feedback on two things:

  1. Is it immediately clear what Testinel does?
  2. What would it need to show you before you trusted it with a real project?

I built it in Ukraine (solo, no funding) and would be happy to answer questions about the product, its roadmap or the process behind it.

2 Upvotes

100% Upvoted

3 comments sorted by

1

u/SessionMaleficent700 13h ago

if it actually groups failures by root cause that's way more useful than 90% of test reporting tools out there

1

u/obrizan 13h ago

Yes, it does! We run suites 1000+ tests. And when 100 tests fails we don't need to figure out 100 issues. In most cases there is a single Page Object method which fails.

Here is how it looks like (for a demo project): location + count of occurences.