You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Harden permission-reject E2E tests across all SDKs (#1194) (#1317)
The existing "reject permission" E2E test in every SDK asserted only that
the target file was unchanged after a model-driven edit attempt. That is a
false-positive-prone check: it passes even when the agent freezes, when the
permission decision is silently dropped, or when the wrong discriminator is
sent. Specifically, it would not have caught the .NET `PermissionDecision`
empty-JSON regression reported in #1194 (since fixed in codegen).
Strengthen each SDK's reject test to additionally assert that the CLI
emits a `tool.execution_complete` event whose error message contains
"user rejected" (case-insensitive). The CLI emits a kind-specific message
for the reject decision ("The user rejected this tool call.") vs. the
distinct message for user-not-available, so this asserts that the specific
`reject` discriminator round-tripped end-to-end - exactly the property
that was broken in #1194.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
0 commit comments