Ross ROSS = Recommend OSS · open-source software intelligence for agents

kubeshop/tracetest

🔭 Tracetest - Build integration and end-to-end tests in minutes, instead of days, using OpenTelemetry and trace-based testing. observed · 2026-10-20

github.com/kubeshop/tracetest · homepage · Go · NOASSERTION (other) observed · 2026-10-20

Health v2 · maintenance only

30/100

  • Activity 16
  • Release rhythm 8
  • Longevity 100

Flags: prerelease_only no_license

How is this computed?

round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-10-21. Adoption (stars, forks) is never an input.

  • gap_med: n/a
  • age_days: 1722
  • days_rel: 714
  • days_push: 504
  • n_releases_24m: 1

Full methodology

Adoption not part of the score

1329 stars · 97 forks observed · 2026-10-20

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded

Tracetest is an open-source trace-based testing tool that builds integration and end-to-end tests on top of OpenTelemetry distributed traces. It lets you assert against both API responses and trace span data across microservices, with a web UI, YAML test specs, a CLI, and CI/CD integrations.

Use cases

  • write end-to-end tests for microservices using OpenTelemetry traces
  • assert on trace span timing like database queries under 100ms
  • test side-effects in distributed systems such as message queues and async calls
  • run trace-based tests in CI pipelines
  • verify quality of OpenTelemetry instrumentation
  • run trace-based tests as synthetic monitors in production
  • integrate trace assertions with existing Cypress, Playwright, k6, or Postman tests

When to choose

  • you have a microservices or event-driven architecture already instrumented with OpenTelemetry
  • traditional input/output tests miss race conditions, bottlenecks, or inter-service failures
  • you want to assert on internal behavior of a transaction, not just the final response
  • you want to build E2E tests quickly via a visual UI or YAML and run them in CI

When to avoid

  • your application is not instrumented with OpenTelemetry and you cannot add tracing
  • you only need simple unit or isolated component tests without distributed tracing
  • you need a fully open-source production-grade self-hosted deployment - the open-source core is hobby-grade and managed/enterprise features are commercial

Facets

application · maturity active

testing e2e-testing tracing monitoring ci-cd testing microservices monitoring developer-tools cli self-hosted cloud cross-platform trace-based-testing opentelemetry distributed-tracing integration-testing synthetic-monitoring observability devops docker kubernetes

10 sources

Member repositories

RepositoryRoleHealth v2
kubeshop/tracetestmain30

For agents

markdown · JSON · MCP: product_card(name="kubeshop/tracetest")

Data as of 2026-10-19T08:05:51.212177+00:00 · Report a problem