CombinedWorkflow Benchmark
Full workflow: create → setup → invoke → verify — comparing TUnit.Mocks (source-generated) against runtime proxy-based mocking libraries.
Last Updated
This benchmark was automatically generated on 2026-06-27 from the latest CI run.
Environment: Ubuntu Latest • .NET SDK 10.0.301
📊 Results
Full workflow: create → setup → invoke → verify:
| Library | Mean | Error | StdDev | Allocated |
|---|---|---|---|---|
| TUnit.Mocks | 2.057 μs | 0.0399 μs | 0.0373 μs | 6.23 KB |
| Imposter | 2.982 μs | 0.0588 μs | 0.1215 μs | 15.71 KB |
| Mockolate | 1.714 μs | 0.0327 μs | 0.0321 μs | 7.36 KB |
| Moq | 406.602 μs | 2.5636 μs | 2.3980 μs | 36.16 KB |
| NSubstitute | 17.790 μs | 0.1040 μs | 0.0922 μs | 26.89 KB |
| FakeItEasy | 18.321 μs | 0.1303 μs | 0.1155 μs | 25.52 KB |
🎯 Key Insights
This benchmark compares TUnit.Mocks (source-generated) against runtime proxy-based mocking libraries for full workflow: create → setup → invoke → verify.
Methodology
View the mock benchmarks overview for methodology details and environment information.
Last generated: 2026-06-27T03:27:29.619Z