Trace the original position through a source map
OpenTelemetry instrumentation for Better Auth - Add distributed tracing to your authentication flows with a single line of code
OpenTelemetry instrumentation for the Resend Node.js SDK
A TypeScript decorator for OpenTelemetry tracing
Braintrust extension for pi. Includes automatic tracing for pi sessions, turns, LLM calls, and tool executions to Braintrust.
Lambda client library that supports hybrid tracing in node js
vtex plugin abtest
A JavaScript library to diff two images. Uses the Longest-Common-Subsequence algorithm to allow content to shift.
Provides functionality related to source maps.
vtex plugin test
vtex plugin whoami
Give a regex, get a robust predicate function that tests it against a string.
vtex plugin edition
Helper functions
test for inclusion or exclusion of paths using globs
Pure JS implementation of CRC32 https://en.wikipedia.org/wiki/Cyclic_redundancy_check
A pure JS implementation SHA256.
SHA256 wrapper for browsers that prefers `window.crypto.subtle` but will fall back to a pure JS implementation in @aws-crypto/sha256-js to provide a consistent interface for SHA256.
A high-level API to automate web browsers
Pure JS implementation of CRC32-C https://en.wikipedia.org/wiki/Cyclic_redundancy_check
Middleware wrapper for Next.js Route Handlers that executes requests within an AsyncLocalStorage context.
A high-level API to automate web browsers
Cross platform children list of a PID
vtex plugin deploy
this crate lets us use #[traced_test] to automatically configure sane default tracing for a rust test
this crate helps us configure tracing for a rust project. It is designed to be used with the `traced-test` crate
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.
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.
MOS6502 Workbench packages a tested 6502 CPU emulator together with an assembler, disassembler, Intel HEX support, runnable examples, and an optional terminal UI for tracing execution.