autotel-vitest

Create parent spans for each Vitest test with OpenTelemetry tracing.

7|3|Updated Nov 26, 2025

Search Tags:#vitest #testing #diagnostics #tracing #otel

Ready to run

npx skills add https://github.com/jagreehal/autotel --skill autotel-vitest

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: autotel-vitest
Source: https://github.com/jagreehal/autotel/tree/main/packages/autotel-vitest/skills/autotel-vitest
Command: npx skills add https://github.com/jagreehal/autotel --skill autotel-vitest

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill enables automatic tracing in Vitest tests by instrumenting each test with a parent span, making test executions and instrumented code filterable and traceable in OTLP backends.

Core Features & Use Cases

Per-test tracing: Creates a dedicated span for each test allowing detailed trace analysis.
Global setup integration: Sets up automatic init() invocation for seamless span creation.
Use Case: Run unit tests with trace visibility in observability tools such as Jaeger or Honeycomb, enabling easier debugging and performance profiling.

Quick Start

Use the autotel-vitest skill to automatically create trace spans during your Vitest test runs.

Frequently Asked Questions about autotel-vitest

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I add OpenTelemetry tracing to Vitest tests?▼

OpenTelemetry tracing in Vitest is automated by creating a parent span for each test, making executions and instrumented code filterable in trace backends. A global setup initializes the tracer for seamless span creation.

Can I trace HTTP requests during Vitest test execution?▼

Yes, cross-process context propagation for HTTP requests is supported during Vitest test execution. Parent spans created for each test maintain the trace context, allowing you to monitor instrumented HTTP calls in observability tools.

Does Vitest support automatic span creation for observability tools like Jaeger?▼

Vitest supports automatic span creation through this instrumentation, sending traces to OTLP backends like Jaeger or Honeycomb. A global setup invokes tracer initialization, generating dedicated spans for detailed performance profiling.

What is the best way to debug Vitest test performance using OpenTelemetry?▼

The best way to debug Vitest performance is by instrumenting each test with OpenTelemetry parent spans. This provides detailed trace analysis in observability tools, enabling you to filter test executions and profile instrumented code.

Do I need a global setup to initialize OpenTelemetry tracing in Vitest?▼

Yes, a global setup is required to initialize OpenTelemetry tracing in Vitest. It automates the init() invocation to ensure seamless span creation and proper tracer initialization for each test run.