Testing and release checks
TTSForge declares a dependency on Readio >=0.3.4. The public API contract test checks
that the installed Readio exposes persisted project settings, synthesis requests and
resolutions, catalog types, and services required by the frontend. For development
against a Readio checkout, install both projects editable:
python -m pip install -e ../readio -e ".[dev]"
Run the suite and lint:
pytest -q
ruff check ttsforge tests
The tests cover the public readio.api contract, persisted settings mapping and
requestless builds, guided catalog selection and capability gates, project reuse and
legacy-workspace handling, saved-setup retry and reconfiguration, chapter selection,
preflight and interaction modes, scoped progress, CLI behavior, package metadata, and CI
configuration. Use tests/test_readio_api_contract.py to diagnose an incompatible
Readio installation.
Publishing checks
Before a TTSForge package release:
Test against the declared Readio floor,
0.3.4, and the newest supported Readio release.Install TTSForge into a clean environment, run
pip check, and smoke-testttsforge --helpandttsforge doctor.Exercise an audiobook workflow with a supported engine, including project reuse and output export.
The local Readio checkout is useful for development but does not replace clean-environment installation and packaging checks.