Document Playwright video proof for UX changes - #429
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
Included review availability: Your plan includes up to 1 review per rolling hour; 0 remain after this review. WalkthroughManual testing and PR verification guidance now requires recorded evidence for temporal browser behavior, matching baseline and candidate conditions, state-based waits, recording inspection, and ignored artifact storage. ChangesVisual evidence guidance
Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to This PR documents a repository-harness-first procedure for producing paired Playwright video evidence without changing product runtime behavior; no actionable merge-blocking risk remains after normal checks and review. Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
🧪 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 |
Summary
recordVideofallback for temporal browser evidencemanual-testing,verify-pr-fix, and the canonical durable visual-evidence gate while keeping generated media out of commitsWhy
The existing workflow already requires durable before/after evidence and clips for interaction changes, but it did not tell agents how to produce those clips. This adopts the useful operational part of OpenClaw’s visual-proof workflow without copying its repository-specific QA infrastructure or undocumented upload path.
Reference: openclaw/openclaw#122920
Validation
ruby skills/pr-batch/bin/hosted-qa-gate-contract-test.rb— 8 runs, 132 assertions, 0 failuresbin/validate— pass, including 133 RuboCop-inspected files with no offensesgit diff --check— passUser Impact
Agents verifying UX changes now have a concrete portable recording procedure for paired before/after clips. Static visual changes continue to use screenshots, and consumer-repository browser harnesses remain authoritative.
Summary by CodeRabbit