Unit Tests

Unit Tests in Buddy - live test results, flaky and slow test detection, GitHub checks, and test analytics for your CI/CD workflows.

Unit Tests in Buddy turn raw test output into live, browsable results. Instead of waiting for the whole suite to finish and then digging through build logs, you get results streamed as the tests run, grouped into sessions, with the failing, flaky and slow tests called out for you.

The setup has two halves. In Buddy you create a test suite in the project settings, which gives you a suite token. In your test runner you add a Buddy reporter (or produce a JUnit XML file and send it with the Buddy CLI), and results start landing in the suite. From there it works the same no matter where the tests ran - a Buddy pipeline, a GitHub Actions workflow, or your own machine.

On top of the results, every session is tied to a commit and branch, so you get full test history, GitHub checks on commits and pull requests, and analytics that show how test performance changes over time. Permissions are inherited from pipelines, so there is nothing extra to configure for your team.

Info
Looking for UI regressions rather than assertions? See Visual Tests - snapshot comparison against approved baselines.

In this section

Page What it covers
Overview What Unit Tests in Buddy are and the benefits over reading raw test logs.
Setup & Reporters Create a test suite in the project and configure the reporter for your testing framework.
Pipeline Integration Use the Collect test results option in a build action to report results from a Buddy pipeline.
Results & Analytics Browse sessions, read result summaries, and spot flaky and slow tests.
GitHub Integration Send results from GitHub Actions and enable checks on commits and pull requests.
Permissions Permission levels inherited from pipelines, and notification configuration.
Troubleshooting Common problems - missing results, token and Node.js version issues - and best practices.