feat(marquette): add typed test-run evidence entries#3196
Merged
Conversation
Adds lazy @vizejs/marquette/test-run and /test-run/validate entries: a fully documented record model with literal-preserving authoring that checks suite target references and the candidate selection against the recorded identifiers, and deterministic validation that shares its VIZE_MARQUETTE_1xx codes, paths, messages, and ordering with the Rust implementation via the shared fixtures. The record schema ships from /test-run/schema, and builds enforce 1 KiB authoring and 4 KiB validation gzip budgets.
|
Warning Review limit reached
Next review available in: 9 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (14)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
vize
@vizejs/fresco
@vizejs/musea-mcp-server
oxlint-plugin-vize
@vizejs/rspack-plugin
@vizejs/unplugin
@vizejs/vite-plugin
@vizejs/vite-plugin-musea
@vizejs/musea-nuxt
@vizejs/nuxt
@vizeui/core
commit: |
Contributor
PR BenchmarkBase:
Raw run timesCompile SFC
Lint
Format
Type check (1T)
Type check (max)
|
Contributor
Detailed Test ReportCommit: Area Summary
Test InventoryTotal tracked cases: 9457 across 1463 files.
Files
Comment truncated at 64000 characters. Open the workflow run for the full job log. |
Contributor
Tool BenchmarkMeasured: 2026-07-21T09:42:26.334Z
Fairness notes:
Commands: gh workflow run tool-benchmark.yml --ref <branch> -f file_count=3000 -f check_file_count=500 -f vite_file_count=1000 -f nuxt_file_count=250 -f large_blocks=300 -f runs=3 -f warmups=1 -f commit_results=true
node bench/generate.mjs 3000
node bench/compare-tools.mjs --input bench/__in__ --vize-bin target/release/vize --runs 3 --warmups 1 --check-file-count 500 --vite-file-count 1000 --nuxt-file-count 250 --large-blocks 300 --runner-label "blacksmith-32vcpu-ubuntu-2404" --out tool-benchmark-summary.md --json tool-benchmark-results.json --doc performance-blacksmith.mdVariant details and raw run timesSFC compile
Large SFC compile
Large SFC type check
Lint
Format
Type check
Vite build (end-to-end)
Nuxt SPA build (end-to-end)
|
This was referenced Jul 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Final step for #3146, on top of #3189/#3191/#3194/#3195: the TypeScript side of the test-run evidence contract as lazy
@vizejs/marquetteentries./test-run— fully documented record model plus literal-preservingdefineTestRunEvidence, which checks suite target references and the candidate selection against the identifiers recorded in the same object. 514 B gzip against a 1 KiB budget./test-run/validate— deterministic validation sharing itsVIZE_MARQUETTE_1xxcodes, paths, messages, and ordering with the Rust implementation, including the calendar-exact timestamp rule and once-per-suite-id diagnostics from fix(marquette): reject impossible dates and dedupe suite-id diagnostics #3193. 3.5 KiB gzip against a 4 KiB budget./test-run/canonical— canonical serialization with schema-ordered properties and sorted executions, Web Crypto SHA-256 fingerprints, andtest-run:<sha256>admission-id construction/parsing. Proven byte-identical to Rust againsttests/fixtures/test-run-evidence/valid.canonicalandvalid.sha256. 1.6 KiB gzip against a 2 KiB budget./test-run/schema— ships the crate's record schema, copied by the existing build step.Cross-language conformance runs on both sides of the shared fixtures: Rust via
tests/test_run_conformance.rs(#3195) and TypeScript via the package tests here.Part of #3146
Need help on this PR? Tag
/codesmithwith what you need. Autofix is enabled.