Files
AhmedIrfanandGitHub 68ece25a80 fix(mcp): add model_size parameter to voicebox.speak (#895)
The MCP voicebox.speak tool built its GenerationRequest without a
model_size, so every agent-triggered generation fell back to the schema
default ("1.7B"). There was no way to reach the 0.6B Qwen variant (or
TADA's 1B/3B) through MCP, and callers paid a model reload whenever the
requested size differed from what was already loaded.

Thread an optional model_size through voicebox.speak and the _speak
helper into GenerationRequest, mirroring the REST /generate surface.
Omitting it passes None, which generate_speech normalizes to the engine
default, so existing callers are unaffected.

Add backend/tests/test_mcp_speak.py covering the forwarded value, the
omitted-default path, and rejection of an invalid size.

Fixes #884
2026-07-26 23:31:41 -07: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