PR 11: E2E — Settings Coverage Expansion#442
Conversation
Add coverage for previously untested settings sections: - Staging Directory: path field save, use staging checkbox toggle - Archive Extraction: extract in downloads directory toggle - Integrity Check: verify checkbox + algorithm select presence, algorithm save - Connections: max parallel downloads field save - Notifications: Discord/Telegram webhook field presence - Logging: log level dropdown persistence after page reload Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
Warning Rate limit exceeded
To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 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. Review rate limit: 0/1 reviews remaining, refill in 46 minutes and 38 seconds.Comment |
nitrobass24
changed the title
The hash algorithm select test's finally block used UI interaction (selectOption) to restore the original value, but the page/browser may already be torn down by that point. Switch to apiSetConfig which makes a direct HTTP call and doesn't depend on the page being open. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
The Hash Algorithm select is disabled when xfer_verify is false (the default). Enable it via API before testing, and restore the original state in the finally block. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Set the xfer_verify config via API BEFORE navigating to the settings page, so the page loads with the select already enabled. Use waitForStream to ensure SSE config delivery before interacting. Increase toBeEnabled timeout to 10s for CI. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
The algorithm select is disabled when its value is null/undefined (option.component.html). Wait for the SSE config delivery to populate the select value before asserting it's enabled. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
1 participant
Summary
settings.spec.tscovering previously untested settings sections:Test plan
finallyblocksexpect.poll()for async backend verification🤖 Generated with Claude Code