test(e2e): screenshot the capture opt-in control (Task 1 evidence) - #63
Conversation
…evidence) Expands the 'Capture & processing' section and captures the opt-in surface — status label + Pause/Restart controls + screen-access state. On macOS this shows the darwin branch (capture active, permission-gated); the win32/linux paused default is a main-process rule proven by the real-seam integration test in desktop-pro (captureStartsPaused + configureCaptureSettings over a real SettingsStore).
|
ⓘ Qodo reviews are paused because your trial has ended. Ask your workspace admin to add credits to resume reviews. Manage billing |
|
Warning Review limit reached
Next review available in: 26 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: defaults Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
✨ 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 |
|
1 participant
Paired e2e evidence for desktop-pro #34 (capture explicit opt-in per device). E2E specs live in core, so the screenshot lands here.
What
Adds a
capture Settings — capture opt-in controlcase to the existingscreenshots-quality-hardeningspec: navigates to Settings, expands the Capture & processing section, and screenshots the opt-in surface (status label + Pause/Restart controls + screen-access state).Screenshot
e2e/screenshots/qh-settings-capture-optin.png— verified by reading the image: on macOS it shows Capturing (green) · SCREEN ACCESS: granted · an explicit Pause capture control. That is the darwin branch of the fix (capture active, permission-gated). The win32/linux paused default is a main-process rule not observable on a macOS e2e host — proven by the real-seam integration test in desktop-pro #34.Tests
npx playwright test -g "capture opt-in control"→ 1 passed. Screenshot read + validated per the mandatory screenshot-validation rule.