[python] add test case #12152

Activity

1. Yuchao Yan (msyyc)

   assigned

   Yuchao Yan (msyyc)

   and

   Copilot

   on Oct 12, 2026
2. Copilot

   linked a pull request that will close this issue[python] Add body-or-no-content Spector coverage #12153on Oct 12, 2026
3. github-actions

   added

   featureNew feature or requestNew feature or request

   emitter:client:pythonIssue for the Python client emitter: @typespec/http-client-pythonIssue for the Python client emitter: @typespec/http-client-python

   on Oct 12, 2026
4. github-actions commented on Oct 12, 2026

   

   github-actionsBot

   on Oct 12, 2026 – with GitHub Actions

   Contributor

   More actions

   🎯 Issue Triage
   This requests Python SDK Spector mock API coverage for the existing response/body-or-no-content scenarios, validating both body-bearing and no-content successful responses.
   Category: Feature Request
   Area: emitter:client:python

   🔍 Analysis

   The work belongs in the Python client emitter's generated mock API tests and should cover the existing @typespec/http-specs scenario for a successful response that may contain a model body or no body. #11650 is related: it introduced the shared 200-body/204-no-content Spector scenario, while this issue tracks consuming that scenario in Python-specific tests, so it is not a duplicate. #12153 is already linked as the implementation PR.

   📝 Suggested next steps

   • Add synchronous and asynchronous Python mock API tests for both declared outcomes.
   • Verify the 200 response is deserialized and the 204 response returns without body deserialization.
   • Run the targeted generated-client mock API tests.

   Generated by Agentic Triage
5. Yuchao Yan (msyyc)

   closed this as completedin #12153on Oct 12, 2026
6. H Nazmul Hassan (Naz-Ovh)

   added a commit that references this issue on Oct 12, 2026

   [python] Add body-or-no-content Spector coverage (microsoft#12153)

   ...

   This issue will close once commit 79ca62c is merged into the 'main' branch.

   79ca62c