test: add pytest coverage for setlist CRUD and song ordering - #16
Conversation
Covers list/create/rename/delete, name validation, position assignment on add, position renumbering on remove, reorder, cross-setlist scoping guard, and updated_at-driven list ordering. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
Warning Review limit reached
Next review available in: 10 seconds 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 selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Twentieth repo from the org test-coverage audit.
16 pytest tests over
routes.py(FastAPI TestClient):{"error": "Not found"}for a missing idfilename, assigns incrementingposition, bumps the setlist'supdated_at(verified via list ordering)song_idsarray drives new position order, empty/missingsong_idsrejected🤖 Generated with Claude Code