Flask App Testing

This project has an established pytest framework. Match it; do not invent a parallel one.

Step 0 — Confirm framework decisions (ALWAYS, when this skill is invoked)

The stack is Flask (assume this). Before scaffolding new test infrastructure, ask the user to confirm — they may differ per task. Skip a question only if the answer is already obvious from the directive.

1. Tier(s) needed — unit only, or also an integration (real-DB) test?
2. Database for integration — MySQL test schema via TEST_DATABASE_URI is the default here. Confirm if a test genuinely needs a real DB (e.g. FOR UPDATE, GET_LOCK, raw SQL) vs. logic that runs fine on SQLite.
3. Seams to fake — confirm which externals to stub: AWS/SOAP via test_mode=True controllers, HTTP via responses, Celery via direct method calls. Do not hit real services.
4. New dependency or config change — if a test needs a new lib, marker, or addopts change, confirm before editing pyproject.toml.