Test Analytics
Test Analytics
Track test results, flaky tests, and duration trends from your CI pipelines.
Everr can parse verbose test output from your CI workflow logs and generate OpenTelemetry trace spans for each test. This enables test result tracking, flaky test detection, failure analysis, and duration trends — all from data you're already producing.
How it works
- Your CI workflows run tests with output that includes individual test results
- Everr ingests workflow logs for your workspace
- The
testlogstotracesconnector parses the log output and identifies test results - Each test becomes a span with attributes like name, result, duration, and framework
- The dashboard surfaces this data through the Tests Overview feature
Supported frameworks
| Framework | Flag | Status |
|---|---|---|
| Go tests | go test -v | Supported |
| Rust tests | cargo +nightly test -- --report-time -Z unstable-options | Supported |
| Vitest | --reporter=verbose | Supported |
More test frameworks will be supported in the future.
Requirements
The key requirement is that your test command must emit individual test results so Everr can parse them into per-test spans. For Go and Vitest this means enabling verbose reporters; for Rust, run tests on a nightly toolchain with --report-time if you want per-test durations in addition to pass/fail results.
Span attributes
Each test span includes the following attributes:
| Attribute | Description |
|---|---|
everr.test.name | Test name (e.g. TestParseConfig or renders login form) |
everr.test.result | Result: pass, fail, or skip |
everr.test.duration_seconds | Test execution duration in seconds |
everr.test.framework | Test framework (go, rust, or vitest) |
everr.test.package | Go package path or Vitest file path |
everr.test.is_suite | Whether this span groups child test spans |
everr.test.is_subtest | Whether this is a subtest/nested describe |
everr.test.parent_test | Parent test name for subtests |