Testing/CI/tooling consistency (#9,#20,#21,#22,#23,#28) (#59)

Co-authored-by: claude <claude@jpaul.io> Co-committed-by: claude <claude@jpaul.io>
2026-06-22 16:07:58 -04:00
parent a6a3cfdc50
commit 391df7fc6d
17 changed files with 216 additions and 82 deletions
@@ -221,12 +221,13 @@ containerize and run the app you already have.
   ```

   That's a clean Python with none of your code. Now confirm CI-grade reproducibility — run the
-   Module 14 test suite in a clean, throwaway container that mounts your code but installs its tools
-   fresh (no test tools baked into your app image — that keeps it lean; see *Where it breaks*):
+   Module 14 test suite in a clean, throwaway container that mounts your code and runs it with the
+   standard-library `unittest` runner: nothing to install, and no test tooling baked into your app
+   image (that keeps it lean; see *Where it breaks*):

   ```bash
   docker run --rm -v "$PWD":/app -w /app python:3.12-slim \
-     sh -c "pip install pytest -q && pytest -q"
+     python -m unittest
   ```

   This is, in miniature, exactly what containerized CI does. If it passes here, it passes the same