docs: document when to use page.evaluate vs user actions in browser tests#10658
docs: document when to use page.evaluate vs user actions in browser tests#10658christian-byrne wants to merge 3 commits intomainfrom
Conversation
🎨 Storybook: ✅ Built — View Storybook |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✅ Files skipped from review due to trivial changes (1)
📝 WalkthroughWalkthroughAdds a "When to Use Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
📦 Bundle: 5.09 MB gzip 🟢 -206 BDetailsSummary
Category Glance App Entry Points — 22.3 kB (baseline 22.3 kB) • ⚪ 0 BMain entry bundles and manifests
Status: 1 added / 1 removed Graph Workspace — 1.14 MB (baseline 1.14 MB) • ⚪ 0 BGraph editor runtime, canvas, workflow orchestration
Status: 1 added / 1 removed Views & Navigation — 76.6 kB (baseline 76.6 kB) • ⚪ 0 BTop-level views, pages, and routed surfaces
Status: 9 added / 9 removed / 2 unchanged Panels & Settings — 484 kB (baseline 484 kB) • ⚪ 0 BConfiguration panels, inspectors, and settings screens
Status: 10 added / 10 removed / 12 unchanged User & Accounts — 17.1 kB (baseline 17.1 kB) • ⚪ 0 BAuthentication, profile, and account management bundles
Status: 5 added / 5 removed / 2 unchanged Editors & Dialogs — 109 kB (baseline 109 kB) • ⚪ 0 BModals, dialogs, drawers, and in-app editors
Status: 2 added / 2 removed UI Components — 60.3 kB (baseline 60.3 kB) • ⚪ 0 BReusable component library chunks
Status: 5 added / 5 removed / 8 unchanged Data & Services — 2.96 MB (baseline 2.96 MB) • ⚪ 0 BStores, services, APIs, and repositories
Status: 13 added / 13 removed / 4 unchanged Utilities & Hooks — 334 kB (baseline 334 kB) • ⚪ 0 BHelpers, composables, and utility bundles
Status: 13 added / 13 removed / 12 unchanged Vendor & Third-Party — 9.8 MB (baseline 9.8 MB) • ⚪ 0 BExternal libraries and shared vendor chunks Status: 16 unchanged Other — 8.43 MB (baseline 8.43 MB) • ⚪ 0 BBundles that do not match a named category
Status: 55 added / 55 removed / 79 unchanged ⚡ Performance
|
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@docs/guidance/playwright.md`:
- Around line 139-158: The migration-candidate TODO block is wrapped in an HTML
comment ("<!-- TODO: Migration candidates — ... -->") so it isn't rendered;
remove the surrounding HTML comment markers and ensure the inner list
(actionbar.spec.ts, changeTracker.spec.ts, selectionToolboxSubmenus.spec.ts,
etc.) remains as plain Markdown so the section is visible in
docs/guidance/playwright.md; keep the existing bullet list and any TODO wording
intact and verify the section renders in the compiled Markdown.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: d2c0af16-8c9b-4d06-a1a3-0fc8ac5b980c
📒 Files selected for processing (1)
docs/guidance/playwright.md
22228fb to
de13d2b
Compare
Addresses review feedback: #10658 (comment)
Addresses review feedback: #10658 (comment)
Summary
Document acceptable vs avoidable
page.evaluatepatterns in Playwright E2E tests, with migration candidates for existing offenders.Changes
page.evaluate" section todocs/guidance/playwright.mdwith acceptable/avoid/preferred guidance and 8 migration candidates identified from auditReview Focus
Whether the migration candidate list covers the right tests and whether the acceptable/avoid boundary is drawn correctly.
┆Issue is synchronized with this Notion page by Unito