🤖 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-05
• 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: 25351601452
• 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

PR: Automated Benchmark Update (2026-05-05)
Status: Already merged — review for record.

---

This is a clean, automated documentation-only PR. No logic changes, no source code touched.

What was updated

• Date stamps advanced from → across all benchmark markdown files
• Benchmark numbers refreshed in tables and Mermaid chart axis bounds
• JSON data files (, , ) updated with new run data

Notable results

TUnit continues to outperform all compared frameworks on async test execution (~512 ms vs NUnit ~705 ms, MSTest ~611 ms, xUnit3 ~760 ms). Build time improved noticeably (~1.42 s vs previous ~1.83 s), likely due to CI machine variance rather than a code change.

Observations

• No issues found. The automated pipeline correctly regenerated all dependent files consistently (markdown, JSON, chart axes).
• Codacy also reported 0 issues.

Nothing to address here. ✓