🤖 Update Benchmark Results

[thomhurst]

Automated Benchmark Update

This PR updates the benchmark documentation with the latest results from the Speed Comparison workflow.

Benchmarks Produced

Individual benchmark artifacts are available for download:

• benchmark-DataDrivenTests
• benchmark-AsyncTests
• benchmark-ScaleTests
• benchmark-MatrixTests
• benchmark-MassiveParallelTests
• benchmark-SetupTeardownTests
• benchmark-BuildTime
• benchmark-summary (aggregated overview)

Runtime Benchmarks

• AsyncTests
• DataDrivenTests
• MassiveParallelTests
• MatrixTests
• ScaleTests
• SetupTeardownTests

Build Benchmarks

• BuildTime
• 2026-05-06
• Ubuntu Latest • .NET SDK 10.0.203

Changes

• Updated benchmark data in docs/static/benchmarks/latest.json
• Updated historical trends in docs/static/benchmarks/historical.json
• Regenerated benchmark documentation in docs/docs/benchmarks/index.md
• Updated benchmark summary in docs/static/benchmarks/summary.json

Workflow Run

• Run ID: 25410255088
• Triggered: schedule
• Date:

---

🤖 This PR was automatically created and will be merged automatically once CI checks pass.

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}

[claude]

Code Review

This PR is an automated benchmark documentation update and does not contain any source code changes. All 336 additions and 336 deletions are confined to documentation files under docs/.

What's Changed

• Updated benchmark dates from 2026-05-05 to 2026-05-06
• Refreshed performance numbers across all benchmark categories (AsyncTests, BuildTime, DataDrivenTests, MassiveParallelTests, MatrixTests, ScaleTests, SetupTeardownTests)
• Updated historical trend data in docs/static/benchmarks/historical.json
• Updated docs/static/benchmarks/latest.json and summary.json

Benchmark Highlights (2026-05-06 run)

Runtime improvements vs prior day:

• TUnit AsyncTests: 512.9 ms → 502.8 ms (~2% faster)
• TUnit AOT AsyncTests: 121.4 ms → 120.4 ms (stable)

BuildTime regression to note:

• TUnit build time increased from 1.418 s → 1.992 s (~40% slower than yesterday's run), and is now slower than all competitor frameworks in this category. This is likely CI noise given the single-day delta, but worth monitoring over time if the trend continues.

No Action Required

Since this is fully automated (source-gen, reflection, AOT, and dual-mode concerns are not applicable here), there are no code correctness, architecture, or performance issues to review. The changes are mechanical data refreshes generated by the Speed Comparison workflow.

No issues found. The PR is safe to merge as-is. ✅

[claude]

Code Review

This PR is an automated benchmark documentation update and does not contain any source code changes. All 336 additions and 336 deletions are confined to documentation files under docs/.

What's Changed

• Updated benchmark dates from 2026-05-05 to 2026-05-06
• Refreshed performance numbers across all benchmark categories (AsyncTests, BuildTime, DataDrivenTests, MassiveParallelTests, MatrixTests, ScaleTests, SetupTeardownTests)
• Updated historical trend data in docs/static/benchmarks/historical.json
• Updated docs/static/benchmarks/latest.json and summary.json

Benchmark Highlights (2026-05-06 run)

Runtime improvements vs prior day:

• TUnit AsyncTests: 512.9 ms -> 502.8 ms (~2% faster)
• TUnit AOT AsyncTests: 121.4 ms -> 120.4 ms (stable)

BuildTime regression to note:

• TUnit build time increased from 1.418 s -> 1.992 s (~40% slower than yesterday's run), and is now slower than all competitor frameworks in this category. This is likely CI noise given the single-day delta, but worth monitoring over time if the trend continues.

No Code Review Concerns

Since this is fully automated (source-gen, reflection, AOT, and dual-mode concerns are not applicable here), there are no code correctness, architecture, or performance issues to review. The changes are mechanical data refreshes generated by the Speed Comparison workflow.

No issues found. The PR is safe to merge as-is.