Skip to content

test: add pytest coverage for LRC formatting, status, and export routes - #10

Open
OmikronApex wants to merge 1 commit into
mainfrom
chore/add-basic-tests
Open

test: add pytest coverage for LRC formatting, status, and export routes#10
OmikronApex wants to merge 1 commit into
mainfrom
chore/add-basic-tests

Conversation

@OmikronApex

Copy link
Copy Markdown
Contributor

Twenty-fifth repo from the org test-coverage audit. This is the older, non-DB sibling of feedBack-plugin-lyrics-karaoke#12 - same sloppak-module dependency for /align and /save, so those routes are left for a follow-up; this PR covers what's testable standalone.

12 pytest tests:

  • _format_lrc / _format_lrc_word_level (pure): MM:SS.CC timestamp formatting, inline word-level timestamps when words is present, falls back to line text without it, empty-input edge case
  • /status: no server configured, healthy (200) and error-status-code server responses via mocked requests.get, connection-exception handling
  • /export: missing-segments 400, header field presence when title/artist given vs. omitted, Content-Disposition filename sanitizes slashes

🤖 Generated with Claude Code

Covers _format_lrc/_format_lrc_word_level (line + inline word-
timestamp formatting, empty-input edge case), /status (no server
configured, healthy/error status codes, connection exceptions via
mocked requests), and /export (missing-segments 400, header field
presence/absence, filename sanitization).

/align and /save additionally require a host-provided sloppak
module not importable standalone in this repo, so route-level
testing for those is left for a follow-up (same situation as
lyrics_karaoke#12).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Jul 8, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@OmikronApex, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 1 minute

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: d9362968-0c77-472a-8ece-13f0e8521efc

📥 Commits

Reviewing files that changed from the base of the PR and between f172eef and e33868f.

📒 Files selected for processing (2)
  • tests/conftest.py
  • tests/test_lrc_and_routes.py
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/add-basic-tests

Comment @coderabbitai help to get the list of available commands.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant