Files
openclaw/qa/scenarios/runtime/gateway-node-pending-work.yaml
Peter Steinberger aba6f26be3 refactor: eliminate wrapper export shadowing hazards (#121388)
* refactor(queue): rename core resolveQueueSettings to resolveQueueSettingsCore

* refactor(channels): make configured binding registry canonical

* refactor(gateway): disambiguate node pending handlers

* refactor(acp): rename gateway session key resolver

* chore(scripts): burn resolved entries from collision baseline
2026-08-09 21:36:46 -07:00

28 lines
1.3 KiB
YAML

title: Gateway node pending work
scenario:
id: gateway-node-pending-work
surface: gateway
category: gateway.nodes-and-remote-capabilities
coverage:
primary:
- gateway.pending-work-delivery
objective: Verify both Gateway node pending-work queues survive same-pairing reconnects and expose explicit delivery outcomes.
successCriteria:
- An operator queues explicit work for a paired disconnected node with wake disabled.
- The same node identity reconnects and drains the explicit work plus the baseline status request.
- An iPadOS camera command rejected as background-unavailable becomes a pullable pending action with the original command, parameters, and action id.
- A same-pairing foreground reconnect pulls and acknowledges the action, after which the queue is empty.
docsRefs:
- docs/gateway/protocol.md
- docs/nodes/camera.md
codeRefs:
- src/gateway/server-methods/nodes.pending-work.ts
- src/gateway/server-methods/nodes.invoke.ts
- src/gateway/server-methods/nodes.pending.ts
- test/e2e/qa-lab/runtime/gateway-node-pending-work.e2e.test.ts
execution:
kind: vitest
path: test/e2e/qa-lab/runtime/gateway-node-pending-work.e2e.test.ts
summary: Start a real child Gateway and prove disconnected enqueue/drain plus foreground-only pull/ack across same-pairing reconnects.