test: pin cua-driver resolver in CLI-fallback sanitization test

The test passed on dev boxes where a cua-driver binary is on PATH but
failed in hermetic CI: _call_tool_via_cli hit resolve_cua_driver_cmd()'s
install-hint early exit before reaching the spawn-env assertion. Pin the
resolver so the test exercises the code path it actually asserts.
This commit is contained in:
Teknium 2026-07-29 09:30:07 -07:00
parent 16720dc45b
commit 28cc6599df

View file

@ -111,6 +111,11 @@ def test_cli_fallback_sanitizes_env_and_hides_console_on_windows(monkeypatch):
captured = {}
_patch_windows_hide_flags(monkeypatch, cua_backend)
# Hermetic CI has no cua-driver binary; pin the resolver so the test
# exercises the spawn-env path instead of the install-hint early exit.
monkeypatch.setattr(
cua_backend, "resolve_cua_driver_cmd", lambda override=None: "cua-driver"
)
monkeypatch.setattr(
cua_backend.subprocess,
"run",