TestTrackingDiagrams 2.0.147-beta
See the version list below for details.
dotnet add package TestTrackingDiagrams --version 2.0.147-beta
NuGet\Install-Package TestTrackingDiagrams -Version 2.0.147-beta
<PackageReference Include="TestTrackingDiagrams" Version="2.0.147-beta" />
<PackageVersion Include="TestTrackingDiagrams" Version="2.0.147-beta" />
<PackageReference Include="TestTrackingDiagrams" />
paket add TestTrackingDiagrams --version 2.0.147-beta
#r "nuget: TestTrackingDiagrams, 2.0.147-beta"
#:package TestTrackingDiagrams@2.0.147-beta
#addin nuget:?package=TestTrackingDiagrams&version=2.0.147-beta&prerelease
#tool nuget:?package=TestTrackingDiagrams&version=2.0.147-beta&prerelease
Test Tracking Diagrams
Effortlessly autogenerate PlantUML sequence diagrams (or Mermaid) from your component and acceptance tests. Tracks HTTP requests between your test caller, your Service Under Test (SUT), and its dependencies, then converts them into diagrams embedded in searchable HTML reports and structured data files.
Example Output
Each test that makes HTTP calls through the tracked pipeline automatically produces a sequence diagram showing the full request/response flow between services.
How It Works
- Intercept — A
TestTrackingMessageHandler(DelegatingHandler) is inserted into the HTTP pipeline, logging every request and response with tracking headers. - Collect — All logged entries are held in the static
RequestResponseLogger, capturing method, URI, headers, body, status code, and service names. - Generate — At the end of the test run,
PlantUmlCreator(orMermaidCreator) groups logs by test ID and converts them into sequence diagram code. - Report —
ReportGeneratorcombines the diagrams with test metadata to produce HTML reports and structured data files.
Quick Start
dotnet add package TestTrackingDiagrams.xUnit3
See the Quick Start guide for full setup instructions.
Supported Frameworks
| Framework | Package |
|---|---|
| Core library | TestTrackingDiagrams |
| xUnit v3 | TestTrackingDiagrams.xUnit3 |
| xUnit v2 | TestTrackingDiagrams.xUnit2 |
| NUnit v4 | TestTrackingDiagrams.NUnit4 |
| MSTest v3 | TestTrackingDiagrams.MSTest |
| TUnit | TestTrackingDiagrams.TUnit |
| BDDfy | TestTrackingDiagrams.BDDfy.xUnit3 |
| LightBDD | TestTrackingDiagrams.LightBDD.xUnit3 / .xUnit2 / .TUnit |
| ReqNRoll | TestTrackingDiagrams.ReqNRoll.xUnit3 / .xUnit2 / .TUnit |
Extensions
| Extension | Package |
|---|---|
| Azure Cosmos DB | TestTrackingDiagrams.Extensions.CosmosDB |
| EF Core (Relational) | TestTrackingDiagrams.Extensions.EfCore.Relational |
| Redis | TestTrackingDiagrams.Extensions.Redis |
| Local PlantUML (IKVM) | TestTrackingDiagrams.PlantUml.Ikvm |
Use Cases
- Debugging failed tests — see the exact HTTP call that returned an unexpected response
- Living documentation — HTML reports and data files that stay in sync with your tests
- AI-assisted analysis — feed deterministic PlantUML to AI tools for accurate reasoning
- PR reviews — sequence diagrams make HTTP interaction changes immediately visible
- Onboarding — new team members can browse reports to understand service interactions
- CI integration — surface results in GitHub Actions / Azure DevOps job summaries
Documentation
For full documentation, see the Wiki.
Key pages:
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net8.0 is compatible. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. net9.0 is compatible. net9.0-android was computed. net9.0-browser was computed. net9.0-ios was computed. net9.0-maccatalyst was computed. net9.0-macos was computed. net9.0-tvos was computed. net9.0-windows was computed. net10.0 is compatible. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
-
net10.0
- Microsoft.AspNetCore.Mvc.Testing (>= 10.0.5)
-
net8.0
- Microsoft.AspNetCore.Mvc.Testing (>= 8.0.25)
-
net9.0
- Microsoft.AspNetCore.Mvc.Testing (>= 9.0.14)
NuGet packages (36)
Showing the top 5 NuGet packages that depend on TestTrackingDiagrams:
| Package | Downloads |
|---|---|
|
TestTrackingDiagrams.PlantUml.Ikvm
Local PlantUML rendering via IKVM for TestTrackingDiagrams. Generates diagrams without requiring a remote PlantUML server. |
|
|
TestTrackingDiagrams.BDDfy.xUnit3
BDDfy + xUnit v3 extensions for tracking service interactions (HTTP, database, cache, events, and more) in your tests and converting them into PlantUML sequence diagrams. |
|
|
TestTrackingDiagrams.xUnit2
xUnit v2 extensions for tracking service interactions (HTTP, database, cache, events, and more) in your tests and converting them into PlantUML sequence diagrams. |
|
|
TestTrackingDiagrams.NUnit4
NUnit 4 extensions for tracking service interactions (HTTP, database, cache, events, and more) in your tests and converting them into PlantUML sequence diagrams. This is the renamed successor to TestTrackingDiagrams.NUnit3. |
|
|
TestTrackingDiagrams.xUnit3
xUnit v3 extensions for tracking service interactions (HTTP, database, cache, events, and more) in your tests and converting them into PlantUML sequence diagrams. |
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last Updated |
|---|---|---|
| 2.22.18 | 0 | 4/23/2026 |
| 2.22.16 | 0 | 4/23/2026 |
| 2.22.15 | 0 | 4/23/2026 |
| 2.22.14 | 0 | 4/23/2026 |
| 2.22.12 | 0 | 4/23/2026 |
| 2.22.11 | 0 | 4/23/2026 |
| 2.22.10 | 0 | 4/23/2026 |
| 2.22.9 | 4 | 4/23/2026 |
| 2.22.8 | 10 | 4/23/2026 |
| 2.22.7 | 115 | 4/22/2026 |
| 2.22.6 | 113 | 4/22/2026 |
| 2.22.5 | 153 | 4/22/2026 |
| 2.22.4 | 159 | 4/22/2026 |
| 2.22.3 | 155 | 4/22/2026 |
| 2.22.2 | 162 | 4/22/2026 |
| 2.22.1 | 186 | 4/22/2026 |
| 2.22.0 | 178 | 4/22/2026 |
| 2.21.2 | 211 | 4/22/2026 |
| 2.21.1 | 196 | 4/22/2026 |
| 2.0.147-beta | 319 | 4/18/2026 |