A library to create a trace of your node app per Google's Trace Event format.
OpenTelemetry Tracing
Get v8 stack traces as an array of CallSite objects.
A library to create a trace of your JS app per Google's Trace Event format.
OpenTelemetry Node SDK provides automatic telemetry (tracing, metrics, etc) for Node.js applications
Trace the original position through a source map
Datadog APM tracing client for JavaScript
OpenTelemetry Jaeger propagator provides HTTP header propagation for systems that are using Jaeger HTTP header format.
OpenTelemetry Collector Trace Exporter allows user to send collected traces to the OpenTelemetry Collector
OpenTelemetry Collector Exporter allows user to send collected traces to the OpenTelemetry Collector
OpenTelemetry Collector Exporter allows user to send collected traces to the OpenTelemetry Collector using protobuf over HTTP
OpenTelemetry Web Tracer
Analyze the output of tsc --generatetrace
Error.captureStackTrace ponyfill
OpenTelemetry instrumentation for `knex` database SQL query builder
Hardhat Tracer plugin
OpenTelemetry AWS Xray propagator provides context propagation for systems that are using AWS X-Ray format.
OpenTelemetry instrumentation for `dataloader` data fetching layer
OpenTelemetry Google Cloud Trace Exporter allows the user to send collected traces to Google Cloud Trace.
OpenTelemetry Zipkin Exporter allows the user to send collected traces to Zipkin.
Node.js binding for libdatadog
Utils for collecting telemetry data from Sanity CLI and Sanity Studio
OpenTelemetry instrumentation for `redis` database client for Redis
OpenTelemetry instrumentation for the `amqplib` messaging client for RabbitMQ
A replacement of the #[test] attribute that initializes tracing infrastructure before running tests.
Supporting procedural macro crate for test-trace.
Evaluate dot notation and arbitrary expressions in format! macros
TestInternals patches Test::Unit::TestCase to allow testing of private methods, as well as variables. The stack trace is also available, including the ability to check that specific parameters were sent to a method. This results in cotton candy goodness for all.
Create traces from RSpec tests using OpenTelemetry or your own tracing library
datadog-ci is a Datadog's Test Optimization library for Ruby. It traces tests as they are being executed and brings developers visibility into their CI pipelines.
Cucumber and RSpec extension that allows to test filesystem operations without leaving any trace on your system.
Parser for Jasmine Spec Files
Automatically generates traces for test cases
RSpec integration for Mergify CI Insights: OpenTelemetry tracing, flaky test detection, and test quarantine.
OpenTracing compatible Tracer implementation to be used in tests in Ruby
A set of [mustache] templates extending [tla-trace-filter] -tool to create a self extracting achieve for API traces generated, when model checking formal models created by [tla-Sbuilder] -tool. Also includes Ruby classes to extract test cases from archive extract. Use case: Formal models, built using [tla-sbuilder], and model checked using [TLA+tools]], can generate /API Traces/, which represent end-to-end scenarios executing across system services in the formal model. An API Trace is composed of steps, with each step giving 1) a (formal) system state before the API call, 2) the API call exercised together with (formal model) value bindings of request parameters, 3) API response returned, and 4) the (formal) system state after the API call. A API Trace can be mapped to /Unit Tests/ on implementation with each Unit Test corresponding a step in the API Trace. After executing each of the individual Unit Tests, the aggregate result can be interpreted as an execution of a "virtual" System Test - considerably easier than managing the execution a System Test as a single unit. The purpose of =tla-trace-arch= GEM is create a self extracting archive, which can be safely distributed to system service developers for extracting API Trace Steps to create unit tests for the service being developed by the developer. Ref: - https://github.com/jarjuk/tla-trace-filter - https://mustache.github.io/mustache.5.html - https://github.com/jarjuk/tla-sbuilder - http://research.microsoft.com/en-us/um/people/lamport/tla/tools.html
Spectracer traces RSpec and Minitest dependencies to determine which specs to run based on git changes. It builds a dependency map during test execution, then uses this data to run only the tests affected by your changes.
A Rails engine providing comprehensive observability for LLM-powered applications. Features include session tracking, trace analysis, prompt management, cost monitoring, and optional chat/agent testing UI (with RubyLLM integration).
Ruby's contemporary test coverage tools all lie, exaggerating coverage through false-positives and creating a false sense of security; minitest-coverage tries to address this. Coverage Analysis Tools rely on tracing facilities built into ruby’s VM. You run your tests, and collect data. Seems simple, but that’s a very flawed approach that buffers your coverage numbers up falsely. I’ve witnessed false coverage by as much as 60%, but it could be even worse. Worse, the tracing facilities currently make it impossible to get truly accurate numbers. Even so, they can be improved to be much more accurate.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.