Files
voicebox/backend/tests
jamiepineandcapy-ai-staging[bot] ae300c5316 fix(kokoro): trim edges only, keep inter-segment gaps
Registering Kokoro with needs_trim=True routed its output through the
generic trim_tts_output, whose 1s internal-silence cut was tuned for
Chatterbox hallucinations. KPipeline synthesizes newline- and
token-limit-separated segments independently, and the ~0.3s lead plus
~0.7s tail pads at each boundary add up to 1.2s of silence, so with
af_sarah a four-paragraph script came back as its first paragraph only
(10.9s -> 1.8s) and a 51s text lost half its segments.

Drop the needs_trim flag, keep the in-backend trim, and give
trim_tts_output a max_internal_silence_ms=None mode that only trims the
leading and trailing pads. Tests updated for the new behaviour, with a
two-segment fake pipeline and an explicit internal-gap case.
2026-10-04 00:01:24 +00:00
..
2026-04-18 16:19:12 -07:00
2026-01-30 16:48:14 -08:00
2026-03-16 01:46:19 -07:00

Backend Tests

Manual test scripts for debugging and validating backend functionality.

Test Files

test_generation_progress.py

Tests TTS generation with SSE progress monitoring to identify UX issues where users see download progress even when the model is already cached.

Usage:

cd backend
python tests/test_generation_progress.py

Prerequisites:

  • Server must be running (python main.py)
  • At least one voice profile must exist

test_real_download.py

Tests real model download with SSE progress monitoring.

Usage:

cd backend
# Delete cache first to force fresh download
rm -rf ~/.cache/huggingface/hub/models--openai--whisper-base
python tests/test_real_download.py

Prerequisites:

  • Server must be running (python main.py)

test_progress.py

Unit tests for ProgressManager and HFProgressTracker functionality.

Usage:

cd backend
python tests/test_progress.py

test_check_progress_state.py

Debugging script to inspect the internal state of ProgressManager and TaskManager.

Usage:

cd backend
python tests/test_check_progress_state.py

Notes

These are manual test scripts, not automated unit tests. They're designed for:

  • Debugging progress tracking issues
  • Validating SSE event streams
  • Monitoring real-time download behavior
  • Inspecting internal state during development