-
Notifications
You must be signed in to change notification settings - Fork 3k
Added recording result api #41704
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added recording result api #41704
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This pull request adds a new recording result API and updates the end‐to‐end test coverage for call automation. Key changes include updating test functions to trigger recording result retrieval, renaming functions and variables to reflect the new API, and revising JSON event fixtures to support the enhanced recording results.
Reviewed Changes
Copilot reviewed 25 out of 25 changed files in this pull request and generated 3 comments.
File | Description |
---|---|
sdk/communication/azure-communication-callautomation/tests/test_e2e_callautomation_client.py | Updated the recording tests to validate the recording result API and renamed test functions/variables accordingly. |
Remaining test files | Revised JSON event fixtures to support recording result events and adjust expected event payloads. |
sdk/communication/azure-communication-callautomation/tests/test_e2e_callautomation_client.py
Show resolved
Hide resolved
sdk/communication/azure-communication-callautomation/tests/test_e2e_callautomation_client.py
Show resolved
Hide resolved
sdk/communication/azure-communication-callautomation/tests/test_e2e_callautomation_client.py
Show resolved
Hide resolved
API Change CheckAPIView identified API level changes in this PR and created the following API reviews |
Description
Please add an informative description that covers that changes made by the pull request and link all relevant issues.
If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
All SDK Contribution checklist:
General Guidelines and Best Practices
Testing Guidelines