Promote 14 pagination and error-handling scenarios from Backlog to Core - #5086
Open
iscai-msft wants to merge 1 commit into
Open
Promote 14 pagination and error-handling scenarios from Backlog to Core#5086iscai-msft wants to merge 1 commit into
iscai-msft wants to merge 1 commit into
Conversation
These scenarios test fundamental patterns used by shipped Azure services: Pagination (12 scenarios): - ContinuationToken (6): header/query request × body/header/nested response - Link-based (3): link, linkString, nestedLink - PageSize (2): listWithPageSize, listWithoutContinuation - XML Pagination (2): listWithContinuation, listWithNextLink Error handling (2 scenarios): - Response_StatusCodeRange_errorResponseStatusCodeInRange - Response_StatusCodeRange_errorResponseStatusCode404 Rationale: These patterns appear in real Azure services (every list operation uses pagination, every service returns errors with status code ranges). They test distinct wire-format behavior not covered by other Core scenarios, and users would file bugs if these didn't work in generated SDKs. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 421f24e7-8a8e-4dad-b066-2c4e974abd68
iscai-msft
requested review from
markcowl,
timotheeguerin and
xirzec
as code owners
July 28, 2026 19:16
Contributor
|
No changes needing a change description found. |
Contributor
|
You can try these changes here
|
| "Payload_Pageable_ServerDrivenPagination_ContinuationToken_requestHeaderResponseHeader", | ||
| "Payload_Pageable_ServerDrivenPagination_ContinuationToken_requestQueryNestedResponseBody", | ||
| "Payload_Pageable_ServerDrivenPagination_ContinuationToken_requestQueryResponseBody", | ||
| "Payload_Pageable_ServerDrivenPagination_ContinuationToken_requestQueryResponseHeader", |
Member
There was a problem hiding this comment.
any azure service doing this? continuationToken on header?
Member
There was a problem hiding this comment.
Same concern with weidong, are these promoted tests used by read service?
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Moves 14 scenarios from Backlog to Core tier in the Can I Use dashboard.
Pagination (12 scenarios)
These patterns are used by every Azure list operation:
link,linkString,nestedLinklistWithPageSize,listWithoutContinuationlistWithContinuation,listWithNextLinkError Handling (2 scenarios)
Every service returns errors; these test distinct wire behavior:
Response_StatusCodeRange_errorResponseStatusCodeInRangeResponse_StatusCodeRange_errorResponseStatusCode404Rationale
Using the rubric:
Current adoption (unbranded emitters)