-
Notifications
You must be signed in to change notification settings - Fork 1
feat: visual regression guard for the Pixi client #133
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
c605ad7
07f7d93
3f66729
635fac4
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -28,7 +28,11 @@ | |
| "prepare": "husky", | ||
| "baseline:visual-compare": "node scripts/compare-rendering.mjs", | ||
| "sites:generate": "node scripts/generate-site-resources.mjs", | ||
|
Owner
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. [P2] Make the visual commands build the client they are checking Both advertised commands consume dist/, but neither npm script builds it; the checker only verifies that dist/index.html exists. Because dist is gitignored and persists locally, npm run pixi:visual-check can report a perfect 0% delta after a Pixi source change while testing an older build, and pixi:visual-update can record references from stale code. CI happens to run build first, but the documented standalone commands are not trustworthy. Please add build prehooks for both check and update (as test:e2e already does) or have the harness build/serve current sources itself. |
||
| "sites:check": "node scripts/generate-site-resources.mjs --check" | ||
| "sites:check": "node scripts/generate-site-resources.mjs --check", | ||
| "prepixi:visual-check": "npm run build", | ||
| "pixi:visual-check": "node scripts/pixi-visual-check.mjs", | ||
| "prepixi:visual-update": "npm run build", | ||
| "pixi:visual-update": "node scripts/pixi-visual-check.mjs --update" | ||
| }, | ||
| "devDependencies": { | ||
| "@playwright/test": "^1.62.0", | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[P2] Upload the actual frames when this CI step fails
On a breach the checker writes tests/fixtures/reference-frames/pixi/linux/*.actual.png and tells the reviewer to inspect those files, but neither workflow uploads that path. The runner then exits and the only copy is lost; the existing always-upload steps cover screenshots/ and playwright-report/ only. This is especially blocking for a platform-keyed guard because a Windows maintainer cannot reproduce the Linux pixels locally. Please add an if: failure()/always() artifact step for the actual PNGs (in PR and preferably deploy workflows) so the promised diagnostic is retrievable.