TracingAssertions 0.2.0

Prefix Reserved
.NET 10.0 This package targets .NET 10.0. The package is compatible with this framework or higher. 
dotnet add package TracingAssertions --version 0.2.0
                    


                    

                
NuGet\Install-Package TracingAssertions -Version 0.2.0
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package. 
<PackageReference Include="TracingAssertions" Version="0.2.0" />
For projects that support PackageReference, copy this XML node into the project file to reference the package. 
<PackageVersion Include="TracingAssertions" Version="0.2.0" />
                    


                            Directory.Packages.props
                        

                    

                
<PackageReference Include="TracingAssertions" />
                    


                            Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package. 
paket add TracingAssertions --version 0.2.0
                    


                    

                
#r "nuget: TracingAssertions, 0.2.0"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package. 
#:package TracingAssertions@0.2.0
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package. 
#addin nuget:?package=TracingAssertions&version=0.2.0
                    


                            Install as a Cake Addin
                        

                    

                
#tool nuget:?package=TracingAssertions&version=0.2.0
                    


                            Install as a Cake Tool

TracingAssertions

NuGet License: MIT .NET

Scope: Test projects only. Not intended for production code.

Framework-agnostic core for the TracingAssertions package family. The TUnit-native fluent assertion entry points ship in the adapter package TracingAssertions.TUnit.

Most users want TracingAssertions.TUnit, not this package directly. Install this core directly only when authoring a non-TUnit adapter or when you only need the span-capture primitive.

What's in this package

  • SpanCapture: a disposable, per-test capture that starts a raw ActivityListener (sampling AllDataAndRecorded) over one or more ActivitySources matched by name and collects the stopped System.Diagnostics.Activity spans. ForSource(name) / ForSources(names) create one (with overloads taking an ActivitySamplingResult since v0.2.0 to capture under a chosen sampling level), Captured exposes the collected spans in completion order, and Dispose() detaches the listener. Use it with a using statement for per-test isolation.
  • Query helpers on the capture: FindByOperationName(name), FindByOperationNameAndTag(name, tagKey, tagValue) (tag compared by invariant ToString), and ChildrenOf(parent) (direct children in the same trace).

No OpenTelemetry SDK, no exporter pipeline, and no NuGet runtime dependency (System.Diagnostics.DiagnosticSource is in the shared framework). AOT-compatible, trimmable, no runtime reflection.

Install

dotnet add package TracingAssertions.TUnit

The core (TracingAssertions) comes transitively; install it directly only when authoring a non-TUnit adapter for the assertion family.

License

MIT throughout. No runtime dependencies beyond the BCL.

Product Compatible and additional computed target framework versions.
.NET 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. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

  • net10.0

    • No dependencies.

NuGet packages (1)

Showing the top 1 NuGet packages that depend on TracingAssertions:

Package Downloads
TracingAssertions.TUnit

TUnit-native OpenTelemetry distributed-tracing (Activity / span) assertions for .NET tests: fluent Assert.That(activity) entry points for operation name, tag existence and value, status, and single-hop parent/child and same-trace relationships. Span capture is a raw ActivityListener over an ActivitySource. Builds on the TracingAssertions framework-agnostic core. AOT-compatible, trimmable, no runtime reflection in the assertion path, and no NuGet runtime dependency.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
0.2.0 347 6/14/2026
0.1.2 1,393 6/6/2026
0.1.1 155 6/5/2026
0.1.0 256 6/4/2026
0.0.1 150 6/4/2026

View the rendered release notes: https://github.com/JohnVerheij/TracingAssertions.TUnit/releases/tag/v0.2.0

Minor release. Adds span and capture assertions for ASP.NET Core span testing, plus a sampling-control capture overload. Purely additive.

### Added

- **Span assertions:** `Assert.That(span).HasKind(ActivityKind)` (for example `Server` for an inbound request span), `IsRoot()` (no parent), `HasEvent(name)`, and `HasExceptionEvent()` (the OpenTelemetry `"exception"` event). The event assertions list the span's event names on failure.
- **Capture assertions:** `Assert.That(capture).HasNoSpan(operationName)` (the inverse of `HasSpan`, for asserting an operation was never traced) and `HasSpanCount(int)`.
- **`SpanCapture.ForSource(name, ActivitySamplingResult)`** and **`ForSources(ActivitySamplingResult, params string[])`** capture under a chosen sampling result. The existing parameterless forms still force `AllDataAndRecorded`. A lower result (for example `PropagationData`) lets a test exercise code that branches on `Activity.IsAllDataRequested`, with the documented caveat that an activity's effective sampling is the maximum across all active listeners, so this takes effect only when the capture is the sole listener.

### Changed

- Bumped `PackageValidationBaselineVersion` from `0.1.0` to `0.1.2` on both packages so ApiCompat strict-mode validates `0.2.0` against the most recently published baseline.