Introducing TestNod: Test Analytics Your CI Doesn't Give You

Continuous integration tools are great at answering one question: did this build pass or fail? Unfortunately, that's a single data point. It doesn't tell you that your checkout flow has failed four times in the last two weeks and passed on retry every time. It doesn't tell you your suite is running much slower than it did a month ago. Getting that information typically means tracking CI test runs over time, and nobody has time for that.

I've spent the better part of two decades working on web applications, and a good chunk of that time has involved keeping automated test runs humming along and CI pipelines running smoothly. Over the years, I noticed that most teams, especially those working at startups and smaller organizations, don't have a clear picture of the health of their test automation processes. They know when tests are failing, but they don't notice the smaller details that make automated test suites turn into a hindrance on the team's performance.

That's what TestNod is for.

Introducing TestNod

TestNod is an automated test analytics service that ingests your JUnit XML results and tracks patterns across builds. Over time, it surfaces flaky tests, flags performance regressions, and shows you pass rate trends. Instead of treating each CI run as an isolated event, it connects hundreds of test runs and shows you what's actually happening with your test suite.

I'm building TestNod because I kept running into this gap with my own projects and clients. We have plenty of tools to run tests and report whether they pass or fail, but nothing lightweight existed to answer questions like "is our test suite getting worse?" without a bunch of manual work. I wanted something I could point a CI pipeline at and get useful data back within a few builds.

How Does TestNod Work?

TestNod is built to be the simplest way to analyze the health of your test suite. All you need to do is add a step to your CI pipeline (we'll have ready-made integrations for GitHub Actions, CircleCI, Jenkins, and GitLab CI) and configure your tests to output JUnit XML reports. After each test run, your JUnit XML report gets sent to TestNod. That's all there is to it. There are no agents to install, no code changes to your test suite, and no need to introduce new test frameworks. Most of today's popular testing libraries (RSpec, pytest, Playwright, etc.) can produce JUnit XML out of the box, so you're just a two-minute config change away from getting started.

Once results start flowing in, you get a dashboard with trends across your projects, and alerts when something needs attention. You'll get notifications when flaky tests pop up, when your test suite slows down over time, and when your pass rate begins to drop. These are the kind of things you'd catch if you had time to review every build, and catching them early is the difference between a five-minute fix and a week-long cleanup.

Sign Up to Get Early Access

TestNod is currently in development, with early access opening by the end of June 2026. If you want to be among the first to try it, drop your email on the waitlist. I'll also help early users get set up personally, so if you've got a test suite that's been giving you trouble, this is a good time to get in.