Files
openclaw/qa/scenarios/plugins/voice-call-cli-rpc-agent-tool.yaml
Dallin Romney 95e3b9243b test: execute media and Talk runtime boundaries (#101091)
* test: execute media and Talk runtime boundaries

* test(qa): centralize gateway fixture startup

* test(qa): check in voice call plugin fixture
2026-07-06 16:25:33 -07:00

34 lines
1.6 KiB
YAML

title: Voice Call CLI, RPC, agent tool, and realtime consult flow
scenario:
id: voice-call-cli-rpc-agent-tool
surface: voice-call-channel
category: voice-call-channel.channel-setup-and-operations
coverage:
primary:
- voice-call.cli-rpc-agent-tool
objective: Verify the real Voice Call CLI, Gateway RPC, and Gateway-invoked agent tool share one mock-provider runtime whose realtime media stream reaches embedded-agent consult context.
successCriteria:
- The CLI starts an outbound call through its Gateway RPC path.
- The registered Gateway RPC starts an outbound call through the same mock provider runtime.
- Gateway tools.invoke starts an outbound call through the registered voice_call agent tool.
- The runtime issues a real webhook media-stream token for the tool-started call.
- The fake realtime provider invokes openclaw_agent_consult and the embedded agent receives caller transcript and provider context.
docsRefs:
- docs/cli/voicecall.md
- docs/plugins/voice-call.md
- docs/gateway/protocol.md
codeRefs:
- extensions/voice-call/index.ts
- extensions/voice-call/src/cli.ts
- extensions/voice-call/src/runtime.ts
- extensions/voice-call/src/webhook/realtime-handler.ts
- test/e2e/qa-lab/runtime/voice-call-gateway.ts
execution:
kind: script
path: test/e2e/qa-lab/runtime/voice-call-gateway.ts
summary: Starts a real Gateway and Voice Call plugin, runs the actual CLI plus RPC and tools.invoke entry points, then drives the runtime-issued realtime media stream through embedded-agent consult.
args:
- --artifact-base
- ${outputDir}