// the find
rakyll/go-test-trace
Go test with tracing.
A drop-in wrapper around `go test` that turns your test run into an OpenTelemetry trace, so each test/subtest shows up as a span you can view in Honeycomb or any OTLP backend. Useful for spotting flaky or slow tests in CI, especially ones with parallel/paused subtests where plain `go test -v` output is hard to read.
Two ways to get traces: running as a real `go test` wrapper (accurate timings) or piping `go test -v` output through `-stdin` for retrofitting into existing CI without changing the invocation. Supports `-traceparent` so a test run's spans can be attached to a larger CI pipeline trace instead of floating on their own. Exports plain OTLP, so it's not locked to Honeycomb despite the example — any OTel collector destination works.
No commits since May 2023 and the example collector config mixes the old OpenCensus port (55680) with OTLP 4317, which suggests it hasn't been touched since the OTel collector's config format moved on — expect to rewrite the collector.yaml yourself. The `-stdin` mode is explicitly called out as less accurate on timestamps, which undercuts the main selling point (tracing) for anyone who can't run it as a true wrapper. It's a single main.go plus a parser file with no indication it handles `go test`'s JSON output format (`-json`), so it's parsing text output by hand — fragile against future Go test output changes. No godoc, no versioned releases on the repo, and only 18 forks/389 stars after ~4 years suggests it never got real adoption or hardening beyond the original author's use case.