-
Notifications
You must be signed in to change notification settings - Fork 66
Add tests for lro scenarios #3363
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
base: main
Are you sure you want to change the base?
Conversation
commit: |
|
All changed packages have been documented.
|
|
You can try these changes here
|
iscai-msft
left a comment
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.
This overall looks pretty good to me, however I would reorganize. I would put all of these into one folder and main.tsp, call it azure-core/lro/lro-status, and have a namespace for cancelled, failed etc
| let uploadPollCount = 0; | ||
|
|
||
| function uploadPendingHandler(req: MockRequest) { | ||
| req.expect.containsQueryParam("api-version", "2022-12-01-preview"); |
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.
depending on whether we really want to test api version, we either should remove it from this file, or explicitly state in the scenario docs that we're looking for api version of a certain value
Adding some tests for scenarios that folks frequently customize in their client libraries. Eventually, client libraries should be able to customize LRO generation based on typespec definitions like custom lro status values.