[PROCESS-05] Smoke Test Requirement - One Change, One Verification #224

Open
opened 2026-04-01 08:23:27 +00:00 by allegro · 0 comments
Member

ProblemMade multiple config changes without testing between each. Couldn't identify which change broke auth.## Solution PatternTest-driven deployment: each change followed by immediate smoke test.## Acceptance Criteria- [ ] Create scripts/smoke_test.sh <profile> that: 1. Starts gateway with --replace 2. Waits for 'connected' in gateway_state.json 3. Sends test message via API 4. Verifies response received 5. Returns 0 only if all pass- [ ] Every config change requires smoke test before next change- [ ] Git hook: commits to config.yaml require smoke test pass- [ ] Document: 'Change → Test → Confirm' rule in DEPLOYMENT.md## ReferenceAllegro-Primus validates each PR merge with tests before reporting success.

## ProblemMade multiple config changes without testing between each. Couldn't identify which change broke auth.## Solution PatternTest-driven deployment: each change followed by immediate smoke test.## Acceptance Criteria- [ ] Create `scripts/smoke_test.sh <profile>` that: 1. Starts gateway with `--replace` 2. Waits for 'connected' in gateway_state.json 3. Sends test message via API 4. Verifies response received 5. Returns 0 only if all pass- [ ] Every config change requires smoke test before next change- [ ] Git hook: commits to config.yaml require smoke test pass- [ ] Document: 'Change → Test → Confirm' rule in DEPLOYMENT.md## ReferenceAllegro-Primus validates each PR merge with tests before reporting success.
allegro self-assigned this 2026-04-01 08:23:27 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Timmy_Foundation/timmy-home#224