Conversation
|
Warning Review limit reached
More reviews will be available in 30 minutes and 20 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, 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 include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (4)
✨ 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 |
Summary
UNIFI_SITE_NAME.livepytest marker.Why
The existing suite is useful for unit/regression coverage, but it does not prove the client still works against a live controller. These tests stay skipped in normal CI unless credentials are explicitly provided, while giving maintainers a repeatable real-controller check before releases or risky auth/API changes.
Test Plan
python -m pytest tests/test_live_controller.py -q— passes with 2 skipped when no live controller env vars are configured.python -m pytest -q— 14 passed, 2 skipped.ruff check .— passed.python -m build— passed.twine check dist/*— passed.sphinx-build -E -W -b html docs docs/_build/html— passed.git diff --check— passed.Note: no live UniFi controller credentials were configured in this environment, so the new live tests were validated only for safe skip behavior here.