Home

Welcome to the Kronikol wiki. This wiki contains the full documentation for configuring, customising, and extending Kronikol.

For an overview of the project, see the README.

Upgrading from 4.x? Migrating to v5 lists what 5.0.0 changed and how to keep the 4.x behaviour. Upgrading from 3.x? Migrating to v4 lists what 4.0.0 changed and how to keep the 3.x behaviour.

Kronikol was published as TestTrackingDiagrams until 3.0.0 (May 2026); it is the same project, renamed. The TestTrackingDiagrams.* NuGet packages are the old identity and are no longer updated - install Kronikol.*.

🔍 Search this wiki — full-text search over all 98 pages. The collapsible “Pages” list in the sidebar matches page and heading names, not page content.

• How-To Guides — Task-oriented recipes (redacting tokens, tracking dependencies, CI setup, etc.)
• FAQ — Quick answers to common questions
• Filtering and Redacting Diagram Content — Fix wide diagrams, hide sensitive data, reduce noise

• Quick Start (xUnit)
• Framework Integration Guides
• Playwright Adapter — browser-driven E2E: per-test identity headers on every request
• ProxyTap Extension — out-of-process capture for backends you cannot instrument
• Ingesting External Captures — the NDJSON format and kronikol ingest
• Ingesting from Jest — a Node service under Jest: its calls, steps, assertions, retries and its spans' internal flow, with no change to the service or the tests
• OTLP Extension — capture the OpenTelemetry spans your services already export
• Exporting to OpenTelemetry — kronikol export pushes captured traffic to an OTLP collector as spans
• CTRF output — GenerateCtrfReport and kronikol ctrf put the run in Common Test Report Format, for CI tooling that already reads it
• Service Card: kronikol card writes service.json: a run's parties, every operation between them with why each call was made, and a hash a service catalogue or an indexer compares to tell whether that behaviour changed (5.21.0)
• Capture-Time Redaction — keep secrets out of every data file
• CosmosDB Extension
• EF Core Relational Extension
• Redis Extension
• OpenTelemetry Extension
• PlantUML IKVM (Local Rendering)
• Tracking Dependencies
  • Faking Dependencies (HTTP Tracking)
• Tracking Custom Dependencies
• HTTP Tracking Setup
• Generated Reports
• Report Configuration
• Component Diagrams (C4-style)
• PlantUML Browser Rendering — client-side rendering on Web Workers, plus the note payload JSON/YAML toggle
• Inline SVG Rendering
• Internal Flow Tracking
• Diagram Customisation
• Content Formatting
  • DiagramFocus (Field Highlighting)
• Tags and Attributes: the tags each framework gives a feature and a scenario, the happy path and the endpoint
• Excluding Requests
• Excluded Headers
• Event Annotations
• Service Bus Tracking Patterns
• Multi-Host Test Architectures
• Background Thread Correlation
• Large Response and Diagram Handling
• CI Summary Integration
• CI Artifact Upload
• Merging Parallel Reports
• Cross-Run History — the append-only ledger a run reads and appends to, so Failures.md, the CTRF document, the pointer and kronikol query history say whether a failure is a regression, has been failing since a particular run, or flips (3.9.0); kronikol history gate fails the build on what is new, with quarantine, rename aliases and CTRF/Allure imports (3.10.0); a sparkline and verdict for every scenario and a History section (3.11.0), drawn on a labs page beside the report from 4.6.0, with ShowScenarioHistory and ShowHistorySection to put them in the report and $flaky in its search; and merge --history (3.11.0)
• Querying Reports — kronikol query: debug a run without reading a report of tens of megabytes — including aggregating a field across every call (values) — and the AI agent skill that uses it, which kronikol init-agents installs into any repository; with no tool installed and no network, the query.cs every run writes beside its report runs the same engine (3.32.0)
• PlantUML Server Configuration
• Example Project
• API Reference