🤖 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-26
• Ubuntu Latest • .NET SDK 10.0.300

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: 26426037121
• Triggered: schedule
• Date:

---

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

[claude]

Code Review: Automated Benchmark Update

This PR is a fully automated daily benchmark data refresh — no production source code changes are involved.

Summary of Changes

• 14 files updated under docs/ only (markdown + JSON data)
• Date bumped from 2026-05-25 → 2026-05-26 across all benchmark docs
• Historical entry for 2026-02-28 pruned (expected rolling-window behaviour)
• Fresh benchmark measurements across 7 categories

Benchmark Highlights

TUnit shows improvements in most runtime categories vs the previous day's run:

• DataDrivenTests: -5.8% (497 → 468 ms)
• SetupTeardownTests: -4.0% (542 → 521 ms)
• AsyncTests: -3.6% (535 → 516 ms)

The MSTest ScaleTests result dropped ~14% in one day (539 → 463 ms) — almost certainly CI runner noise rather than a real change, since no code was modified.

No Concerns

The changes are exactly what they should be: mechanical, auto-generated documentation updates. All JSON files are internally consistent, labels are correct (automated, documentation, ignore-for-release), and no logic/API/snapshot files are touched.

The pre-existing missing trailing newline on JSON files is cosmetic and pre-dates this PR.

✅ LGTM — clean automated update, nothing to action.

[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.}