Skip to content

docs: support the uniform 15-case official benchmark campaign - #614

Open
Mohamed Mansour (mohamedmansour) wants to merge 2 commits into
mainfrom
docs/official-benchmark-campaign
Open

Mohamed Mansour (mohamedmansour) wants to merge 2 commits into
mainfrom
docs/official-benchmark-campaign

Conversation

@mohamedmansour

Copy link
Copy Markdown
Contributor

Summary

  • Replace the historical mixed-refresh snapshot with the uniform 15-case WebUI 3.0.4 official campaign.
  • Keep prepare:benchmarks as the docs validation/adaptation step, validating campaign provenance, both SSR response modes, and disclosed unavailable browser-memory samples.
  • Refresh the homepage previews, explorer, methodology, and sanitized official-results JSON download without importing bulk telemetry into browser state.
  • Update evidence, SSR, interaction, responsive, and no-JavaScript regression expectations.

Validation

  • WebUI Press test TypeScript check passed.
  • 45 focused evidence and server-rendering tests passed.
  • 17 Chromium homepage, benchmark-control, layout, navigation, and no-JavaScript checks passed.
  • Documentation build passed; homepage, benchmark page, and official-results JSON returned HTTP 200.
  • Snapshot hash matches the benchmark repository export.

Companion exporter branch: https://github.com/microsoft/webui-benchmarks/tree/update-benchmarks

Refresh the fifteen-case campaign snapshot, validate source provenance and disclosed browser sample availability, and update the explorer and homepage previews while keeping docs-side preparation.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@mohamedmansour

Copy link
Copy Markdown
Contributor Author

Companion campaign exporter and synchronization: microsoft/webui-benchmarks#49.

@mddinbox mddinbox left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Target: 2dab85c...255597e | Coverage: complete 12-file three-dot diff, including structured comparison of the large JSON data change; CI: Docs, Test, Build (Linux/Windows/macOS), Lint, FFI, WASM, E2E, CodeQL passed.
Challenge: 1 confirmed, 0 revised | Compatibility: displayed measurements are not bound to the claimed provenance digest.
Action: COMMENT | The campaign validator does not tie the published measurements to their source digest.

Comment thread docs/.webui-press/components/benchmark-explorer/benchmark-data.ts
Validate canonical measurements and provenance against an independent build/test pin before replacing generated benchmark evidence.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Copilot-Session: 844f2168-295c-4641-974d-8e90468b3568

@mddinbox mddinbox left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed the updated 15-case campaign and evidence validation. The pinned canonical digest and tamper tests address the prior provenance concern; no blocking issue found in the PR. Linux/Windows build checks currently fail in unrelated native IPC acceptance / external download steps and should be rerun or resolved before merge.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants