5.4 KiB
5.4 KiB
phase, plan, type, wave, depends_on, files_modified, autonomous, must_haves
| phase | plan | type | wave | depends_on | files_modified | autonomous | must_haves | ||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 12-polish-audit | 02 | execute | 1 | false |
|
Purpose: Complete the two UAT tests deferred from Phase 11. Code is already deployed -- this is validation only. Output: UAT results confirming Update All works end-to-end via both entry points.
<execution_context> @/home/luc/.claude/get-shit-done/workflows/execute-plan.md @/home/luc/.claude/get-shit-done/templates/summary.md </execution_context>
@.planning/PROJECT.md @.planning/ROADMAP.md @.planning/STATE.md @.planning/phases/11-update-all-callback-limits/11-02-SUMMARY.md @.planning/phases/11-update-all-callback-limits/11-VERIFICATION.md Task 1: UAT -- Update All via text command (BATCH-04) n8n-workflow.json User verifies the Update All text command end-to-end. This was deployed in Phase 11 (Plan 11-02) but UAT was deferred. The Keyword Router matches "update all" and routes to Get All Containers For Update All, which filters :latest containers and shows a confirmation dialog. No code changes needed -- this is validation only. **Preconditions:** - Workflow is active and deployed - You have containers with :latest tag on your Unraid serverTest Steps:
- Send "update all" to the bot via Telegram
- Expected: Bot responds with a confirmation message listing all containers with :latest tag and their current status
- Verify the container count in the confirmation matches your actual :latest container count
- Tap the "Confirm" button
- Expected: Progress message appears showing batch execution starting
- Wait for execution to complete
- Expected: Final summary message shows N succeeded, M failed (ideally 0 failed)
- Send "/status" to verify containers show updated status
Pass criteria:
- Confirmation lists all :latest containers
- Progress updates appear during batch execution
- Summary shows accurate success/failure counts
- No error messages or timeouts User confirms "update all" text command triggers confirmation dialog, batch execution with progress, and summary. BATCH-04 UAT complete.
Test Steps:
- Send "/status" or "/list" to the bot to display the container list keyboard
- Locate the "Update All :latest" button in the inline keyboard (below navigation, above Select Multiple)
- Tap the "Update All :latest" button
- Expected: Bot acknowledges with "Checking for updates..." callback answer
- Expected: Confirmation message appears listing all :latest containers (same as text command flow)
- Tap "Confirm" button
- Expected: Same batch execution flow as Task 1 (progress, summary)
- Send "/status" to verify containers show updated status
Pass criteria:
- "Update All :latest" button visible in container list keyboard
- Tapping button shows confirmation dialog with :latest containers
- Confirmation and batch execution work identically to text command
- No error messages or timeouts User confirms "Update All :latest" inline keyboard button triggers same confirmation and batch execution flow as text command. BATCH-05 UAT complete.
<success_criteria>
- User successfully triggers Update All via "update all" text command with confirmation and batch execution
- User successfully triggers Update All via inline keyboard button with confirmation and batch execution
- Both Phase 11 deferred UAT tests completed with pass/fail determination </success_criteria>