Files
openclaw/qa/scenarios/runtime/tools/exec.yaml
Dallin Romney c1c231ced9 fix(qa): reject runtime tool intent without result evidence (#113502)
* fix(qa): require runtime tool result evidence

* fix(qa): preserve meaningful tool coverage gates

* refactor(qa): colocate runtime parity projection

* fix(qa): keep passing tool totals evidence-backed
2026-07-27 11:00:59 +08:00

52 lines
1.8 KiB
YAML

title: "Runtime tool fixture — exec"
scenario:
id: runtime-tool-exec
surface: runtime-tools
runtimePairLane: core
coverage:
secondary:
- tools.exec-routing-exec
objective: Verify command execution behavior is tracked across OpenClaw and Codex while Codex owns exec/process natively.
successCriteria:
- OpenClaw may expose OpenClaw exec while Codex app-server mode may omit duplicate OpenClaw dynamic exec/process.
- Mock provider exec plans are reported as fixture intent, not as actual runtime tool calls.
- The row stays report-only until the fixture validates native Codex command behavior directly.
docsRefs:
- qa/scenarios/index.yaml
codeRefs:
- src/agents/bash-tools.schemas.ts
- extensions/qa-lab/src/runtime-tool-fixture.ts
execution:
kind: flow
summary: Exercise the exec runtime tool family.
config:
toolName: exec
toolCoverage:
family: exec
actualTool: exec
bucket: codex-native-workspace
expectedLayer: codex-native-workspace
required: false
tracking: "#80319"
codexDefaultImpact: P4
qaImpact: P1
action: split native command behavior from OpenClaw dynamic tool parity
reason: Codex app-server intentionally owns command execution natively; the fixture must not require OpenClaw dynamic exec exposure.
knownHarnessGap:
issue: "#80319"
reason: QA tool-defaults currently needs native command behavior coverage instead of OpenClaw dynamic exec exposure.
promptSnippet: "target=exec"
failurePromptSnippet: "failure target=exec"
flow:
steps:
- name: exercises exec happy and failure paths
actions:
- call: runRuntimeToolFixture
saveAs: result
args:
- ref: env
- ref: config
detailsExpr: result