Automated test analytics for CI with JUnit XML

TestNod is a service that gathers the data generated from your automated test runs and analyzes them over time, helping you spot flaky tests, catch regressions, and see how performance changes over time. It takes JUnit XML reports that your automated test framework produces and turns them into a long-term history you can keep track of.

TestNod also automatically detects issues like flaky tests, performance regressions, and skipped-test creep. It sends you and your team alerts when these issues cross thresholds you set, so you can address them before they become bigger problems.

How TestNod analyzes your automated tests

Setting up TestNod is a matter of configuring your automated test framework to output JUnit XML reports and adding a step to upload them to TestNod. Once your test runs are in TestNod, it analyzes the data and produces the insights and alerts described below.

What it does

Results show up in your organization's dashboard after the first upload:

• See what's changed between test runs. The test run page shows new failures, newly fixed tests, slowdowns, and added or removed cases compared to a baseline run on the same branch and tags.
• Group test failures together. When several tests fail with the same normalized error inside one run, they show up as a single failure pattern rather than dozens of look-alike rows.
• Notice when something drifts. Performance regression, flakiness, and skipped-test-creep detection run automatically against new runs, and alert you when they cross thresholds you set.

How it fits in your CI

Your existing test step will need to write a JUnit XML file (or multiple files when running in parallel or across multiple runners). Add a step to upload the JUnit XML files to TestNod using your project token.

Where to start

If you haven't signed up for TestNod yet, you'll need to do that first. TestNod is currently in private beta, so you can request an invite on the TestNod homepage. Once you have access, you can create a project and get your project token to start uploading test runs.

Jump to the Quickstart documentation for step-by-step instructions on how to set up your first test run with TestNod. After your first run is uploaded, take the Test run page tour to familiarize yourself with all the insights and data TestNod provides.