🤖 Update Mock Benchmark Results

[thomhurst]

Automated Mock Benchmark Update

This PR updates the mock benchmark documentation with the latest results from the Mock Benchmarks workflow.

Benchmarks Produced

Individual benchmark artifacts are available for download:

• mock-benchmark-MockCreation
• mock-benchmark-Setup
• mock-benchmark-Invocation
• mock-benchmark-Verification
• mock-benchmark-Callback
• mock-benchmark-CombinedWorkflow
• mock-benchmark-summary (aggregated overview)

Libraries Compared

Libraries are discovered dynamically from the benchmark output. See the generated summary.json for the full list.

Changes

• Updated mock benchmark data in docs/static/benchmarks/mocks/latest.json
• Regenerated mock benchmark documentation in docs/docs/benchmarks/mocks/
• Updated mock benchmark summary in docs/static/benchmarks/mocks/summary.json

Workflow Run

• Run ID: 27663334837
• Triggered: schedule

---

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

[claude]

Code Review

This is an automated benchmark data refresh PR — date stamps updated, benchmark numbers refreshed from the 2026-06-17 CI run, and a minor JSON schema evolution (new Gen2 GC field added to entries). Overall the PR is clean and does exactly what it says.

Observations

Schema evolution (JSON): The new run adds a "Gen2": "-" field to many benchmark entries that previously omitted it. This is fine — it reflects the benchmark tool now capturing Gen2 GC data — but it's worth confirming the documentation renderer handles optional fields gracefully (e.g. no broken table columns if Gen2 is sometimes absent).

Performance variance worth monitoring: TUnit.Mocks' Verification benchmark shows a ~27% regression (635 ns → 810 ns) and Verification (Multiple) jumped ~23% (1,123 ns → 1,381 ns). These could be run-to-run noise on a shared CI runner, but they're larger swings than most other metrics. If the automated workflow doesn't already alert on statistically significant regressions between runs, that would be a useful addition — right now a real regression could slip in unnoticed across these automated merges.

Missing newline at end of file: docs/static/benchmarks/mocks/latest.json ends without a trailing newline (\ No newline at end of file). Minor, but worth fixing in the generator script.

Positive: The automation is well-structured — separate artifact per benchmark category, a summary artifact, consistent date/timestamp updates across all files, and Mermaid chart axis ranges recalculated to match the new data. The PR description is clear and useful.

No blocking issues. The PR is good for what it is.

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