test(python): add response replacement mock API coverage - #12010
Yuchao Yan (msyyc) with Copilot wants to merge 4 commits into
Conversation
|
Azure Pipelines: Successfully started running 1 pipeline(s). 1 pipeline(s) were filtered out due to trigger conditions. There may be pipelines that require an authorized user to comment /azp run to run. |
Co-authored-by: msyyc <70930885+msyyc@users.noreply.github.com>
|
Copilot resolve the merge conflicts in this pull request |
1 similar comment
|
Copilot resolve the merge conflicts in this pull request |
…-for-5471 # Conflicts: # packages/http-client-python/package.json Co-authored-by: msyyc <70930885+msyyc@users.noreply.github.com>
Resolved the merge conflict and pushed merge commit |
The branch already contains the current |
|
|
||
|
|
||
| @pytest_asyncio.fixture | ||
| async def client(): |
There was a problem hiding this comment.
Copilot add "namespace" configuration in https://github.com/microsoft/typespec/blob/main/packages/http-client-python/eng/scripts/ci/regenerate-common.ts to keep consistent with other similar test cases then update test files.
There was a problem hiding this comment.
Added the response-replacement namespace override and updated both test imports in d910354c.
Co-authored-by: msyyc <70930885+msyyc@users.noreply.github.com>
Adds Python mock API coverage for Azure Spector response-replacement scenarios introduced in Azure/typespec-azure#5471.
Changes
Spector dependency
@azure-tools/azure-http-specsto0.1.0-alpha.46-dev.2.Mock API coverage
void_responseandbytes_response.@typespec/http-client-pythonchange entry.