alembic/tests/README.md

Tests

Unit and safety tests for the control-plane app and the dedup file-deleter. They run against throwaway temp dirs and a temp SQLite database (set up in conftest.py); they never touch a real library, your /config, or the network.

Running them

The runtime image doesn't ship pytest, so install it into a throwaway run of the built image (which already has the app's own dependencies). Run as root so pip can write into the image's venv, and keep pytest's cache off so it doesn't create files in your working tree:

docker run --rm --user root -v "$PWD":/src -w /src -e PYTHONPATH=/src \
  --entrypoint bash alembic:latest \
  -c "pip install -q pytest && pytest -q -p no:cacheprovider"

Tests set their own temp ALEMBIC_CONFIG_DIR, MUSIC_DATA_DIR, and encryption key (see conftest.py), so nothing here touches a real library or config.

Or, if you have a matching Python environment locally:

pip install -r requirements-dev.txt
PYTHONPATH=. pytest -q

What's covered

• Dedup safety (test_dedup_gating.py): dedup-library.sh deletes only the paths confirmed via --only-paths, and keeps the higher-ranked (FLAC) copy. This is the most important test: the script deletes files.
• Runner (test_pipeline_runner.py): lock skip, use_lock=False bypass, success/failure/timeout recording, lock release.
• Migrations (test_db.py): schema version, idempotent re-run, FK-safe job-run pruning, stale-run reconciliation.
• Credential rendering (test_credential_service.py): config field substitution (including newline-injection safety), secret vs non-secret classification, cookie-expiry parsing.
• Playlists (test_playlist_service.py): cron round-trips, name validation, config render/delete.
• Diagnostics (test_diagnostics.py): the /health and /setup checks.