TimeAssertions 0.9.0

Prefix Reserved
dotnet add package TimeAssertions --version 0.9.0
                    
NuGet\Install-Package TimeAssertions -Version 0.9.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="TimeAssertions" Version="0.9.0" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="TimeAssertions" Version="0.9.0" />
                    
Directory.Packages.props
<PackageReference Include="TimeAssertions" />
                    
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 TimeAssertions --version 0.9.0
                    
#r "nuget: TimeAssertions, 0.9.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 TimeAssertions@0.9.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=TimeAssertions&version=0.9.0
                    
Install as a Cake Addin
#tool nuget:?package=TimeAssertions&version=0.9.0
                    
Install as a Cake Tool

TimeAssertions

NuGet License: MIT .NET

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

Framework-agnostic rendering helpers and test infrastructure for the TimeAssertions package family. The actual FakeTimeProvider and TimeProvider-aware DateTimeOffset assertion APIs ship in the framework-specific adapter packages (currently TimeAssertions.TUnit).

Most users want TimeAssertions.TUnit, not this package directly. This package only ships the shared rendering helpers; the adapter package adds the assertion entry points your test framework expects.


What's in this package

  • TimeRenderingHelpers: formatting utilities for elapsed durations and time budgets in failure-message context. Pure, allocation-conscious.
  • ObservableTimeProvider: a TimeProvider decorator that tracks the timers created against it (ActiveTimerCount, ActiveTimers, NextTimerDueTime) and counts their callback fires (TimerFireCount, cumulative and surviving disposal) so adapter packages can assert on timer-disposal, leak, pending-due-time, and fire-count behavior without advancing the clock. Reflection-free, AOT-compatible, thread-safe.
  • ActiveTimerInfo: a readonly record struct describing a tracked timer's schedule (DueTime, Period) and its fire count (TimesFired), returned by ObservableTimeProvider.ActiveTimers.
  • TimelineRenderer / TimelineEvent: render a sequence of timestamped events as deterministic, snapshot-friendly text.

Test-framework adapters

Package Test framework Status
TimeAssertions.TUnit TUnit Available now
TimeAssertions.NUnit NUnit Possible if there is demand
TimeAssertions.xUnit xUnit Possible if there is demand
TimeAssertions.MSTest MSTest Possible if there is demand

If you'd find a non-TUnit adapter useful, open a feature request: adapters are not built proactively.

Installation

dotnet add package TimeAssertions.TUnit

TimeAssertions comes transitively. You don't need to install it directly unless you're building your own adapter package.

Stability

The public surfaces above are semver-bound. Breaking changes require a major version bump. The exact text format of TimeRenderingHelpers output is not stable and may gain extra detail or change formatting in any release.

License

MIT. Copyright (c) 2026 John Verheij.

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 TimeAssertions:

Package Downloads
TimeAssertions.TUnit

TUnit-native fluent time-assertion DSL on FakeTimeProvider plus assertion-level timing budget chain extensions via [AssertionExtension]. Provides Assert.That(fakeTime).HasAdvancedExactly(...) / HasAdvancedApproximately(...) / HasUtcNow(...) / HasUtcNowApproximately(...), Assert.That(timestamp).IsRecent(...) / IsBeforeNow(...) / IsAfterNow(...), and the cross-cutting Assert.That(value).IsX().And.WithinTimeBudget(TimeSpan) / WithinTimeBudgetCapturing(TimeSpan, Action<TimeSpan>) on any TUnit assertion chain. Composes with sibling assertion packages without a binary dependency. AOT-compatible, trimmable, no reflection.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
0.9.0 761 6/12/2026
0.8.1 1,618 6/6/2026
0.8.0 165 6/5/2026
0.7.0 250 6/4/2026
0.6.0 156 6/3/2026
0.5.0 245 5/19/2026
0.4.0 359 5/13/2026
0.3.0 176 5/12/2026
0.2.0 183 5/7/2026
0.1.0 163 5/6/2026

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

Minor release. Adds fire observation to `ObservableTimeProvider`: a count of how many times timer callbacks ran, next to the existing leak and pending-due assertions. Purely additive. Also corrects stale guidance in the docs.

### Added

- **`Assert.That(time).HasTimerFiredCount(int expected)`**, **`HasNoTimerFired()`**, and **`HasTimerFiredAtLeast(int count)`** assert how many times timer callbacks fired across every timer the provider created. `ObservableTimeProvider` now wraps each timer callback to count its fires. The count is cumulative and is not reset on disposal. With a `FakeTimeProvider`, a fire is counted each time test code advances fake time past a due or period boundary, which keeps the count deterministic. `ObservableTimeProvider.TimerFireCount` (cumulative) and `ActiveTimerInfo.TimesFired` (per timer) expose the same data on the framework-agnostic core.
- `ObservableTimeProvider.CreateTimer` now validates that the callback is non-null up front (`ArgumentNullException`), matching the rest of the surface, instead of deferring to the inner provider.

### Fixed

- Once a periodic timer fires, `NextTimerDueTime` (and the `HasNextTimerDueApproximately` / `HasPendingTimerDueWithin` assertions) now report the timer's period, since that is when the next callback is due. A fired one-shot timer is disabled and drops out of the pending-due calculation. Previously the due time stayed frozen at its creation value until an explicit `Change`.
- Corrected stale documentation that claimed the package "deliberately does not ship its own polling assertion": it has shipped `HasNoActiveTimersEventually` and its count-targeted siblings since `0.7.0`/`0.8.0`. The README and the `ActiveTimerAssertions` XML docs now point to those overloads for the asynchronous disposal race, reserving generic `Eventually` for arbitrary conditions.

### Changed

- Bumped `PackageValidationBaselineVersion` from `0.7.0` to `0.8.1` on both packages so ApiCompat strict-mode validates `0.9.0` against the most recently published baseline. The new members are recorded as additive differences in `CompatibilitySuppressions.xml`.