UTS: correct wrong/nonexistent spec-point references in rest/unit Test IDs - #539
Open
owenpearson wants to merge 1 commit into
Open
owenpearson wants to merge 1 commit into
owenpearson wants to merge 1 commit into
Conversation
…t IDs Several Test IDs cited spec points that are wrong or absent from features.md (e.g. TK3-TK6 do not exist). Relabels them to the correct existing spec points and updates the generated completion-status.md accordingly. Closes #525 Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This branch was successfully deployed
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
1 participant
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.
Several UTS Test IDs cited spec points that are wrong or do not exist in
features.md. This relabels them to the correct existing spec points and updates the generatedcompletion-status.md. No behavioural assertions changed; nofeatures.mdchange needed.Wrong reference → correct spec point
error_types.mdTI2/TI3/TI5as attribute labelsTI1(href=TI1, TI4); from-JSON + AblyException-wraps re-filed underTI2token_types.mdTD1–TD5TD2–TD6(off-by-one)token_types.mdTK1–TK6(TK3–TK6don't exist)TK2a–TK2e, all-attrs =TK2token_types.mdTE1/TE2/TE4/TE6TE2/TE4swap fixed; keyName/clientId/nonce =TE2, ttl =TE4authorize.mdRSA10e/RSA10g/RSA10h/RSA10jRSA10g/RSA16c/RSA10j/RSA10a; header dropsRSA10h, addsRSA16cidempotency.mdRSL1k2/RSL1k3RSL1k1, single client id =RSL1k2, mixed batch =RSL1k3All target spec points were cross-checked against
specifications/features.mdand confirmed to exist;features.mdwas not edited.-<n>Test ID suffixes were reindexed to keep IDs unique (verified no duplicates). The idempotency edits are confined to labels/IDs so they compose with #527's assertion fix rather than conflicting.Files changed:
uts/rest/unit/types/error_types.md,uts/rest/unit/types/token_types.md,uts/rest/unit/auth/authorize.md,uts/rest/unit/channel/idempotency.md,uts/docs/completion-status.md.Merge order: PR 6 of 7; merge after the mock-HTTP PR (#534, shares
auth/authorize.md) and the publish-body PR (#537, shareschannel/idempotency.md); rebase after those.Closes #525
🤖 Generated with Claude Code