afterhours-shift-manager/tests/requirements.txt

# Test-only dependencies. The CI reusable workflow (ci-python-sam.yaml) installs
# every requirements.txt it finds when run-tests is true, so this file is picked
# up automatically alongside each Lambda's runtime requirements.
pytest>=8.0
moto[dynamodb,ses,secretsmanager]>=5.0
responses>=0.25
freezegun>=1.5
Add pytest suite and wire it into CI Stands up the first automated tests for the repo (151 tests) and turns on the CI test step. - Lift slack-bot handlers out of create_app() closures to module level so they're unit-testable; create_app is now a thin Bolt-wiring layer. No behavior change (handler entrypoints and create_app signature unchanged). - tests/ mirrors src/: shared layer (schedule, blocks, 3CX client, ring_scheduler, secrets) + all four Lambdas (pay math, drop/swap/pick/ admin/register/rate, pickup button, roster sync, queue scheduler). - All boundaries mocked: DynamoDB/SES/Secrets via moto, 3CX HTTP via responses, Slack via fakes, time via freezegun. No real network/AWS. - pyproject.toml pytest config (pythonpath=src/shared, importlib mode); per-package conftest loads each app.py under a unique name to avoid the four-app.py collision. tests/requirements.txt for test-only deps. - ci.yaml: run-tests: true (reusable workflow auto-installs deps) and lint the tests dir too. - README Testing section. Closes #85 2026-06-01 18:50:27 -04:00			`# Test-only dependencies. The CI reusable workflow (ci-python-sam.yaml) installs`
			`# every requirements.txt it finds when run-tests is true, so this file is picked`
			`# up automatically alongside each Lambda's runtime requirements.`
			`pytest>=8.0`
			`moto[dynamodb,ses,secretsmanager]>=5.0`
			`responses>=0.25`
			`freezegun>=1.5`