dch_003 · Deployment Handler: project exists but no deployment_spec → 400
Status: ✓ Passing · Last run: 2026-06-09T07:14:28 · Pipeline: deployment_handler
· History: 1/1 runs passed (100%)
What was tested
Project doc exists in Firestore but has no deployment_spec field yet — typical state for a project the user created but never deployed. Calling handle_render_live must return 400 with a clear "no deployment on this project" message.
What we planted in the data
- 1 entities
- Signal strength: 0.50 (sigmoid slope multiplier)
scenario=no_spec
What the system did
- Model selected:
DeploymentHandlerRunner
What we checked — all assertions passed
| Status | Assertion | Detail |
|---|---|---|
| ✓ | handler_returns_status |
handler returned 400 (body error='no deployment on this project') |
| ✓ | handler_error_message_mentions |
handler error mentions 'deployment' |
How this could have gone wrong
(no assertion descriptions provided)
Why this case matters
Users sometimes hit the refresh endpoint before clicking Deploy. Without this guard, the handler would crash trying to parse a None DeploymentSpec, and the FE would show a generic 500.
Reproducing
# from auto_insight_api/
python -m validation.v2 run dch_003 --pipeline deployment_handler -v
- Case config:
validation/v2/cases/dch_003_no_spec.yaml - Data shape:
deployment_handler_no_spec - Analytics type:
deployment_handler