Add e2e tests for documentation and specialwords spector scenarios #9340
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.
Adds missing end-to-end test coverage for TypeSpec spector scenarios in
documentationandspecialwordspackages following patterns established in PR #9172.Tests Added
Documentation package (6 tests):
BulletPointsOpTests- validates bullet point rendering in operation docsBulletPointsModelTests- validates bullet points in model/enum documentationNumberedTests- validates numbered list formattingBoldTextTests- validates bold text formatting (**text**)ItalicTextTests- validates italic text formatting (*text*)CombinedFormattingTests- validates nested bold/italic combinationsSpecialWords package (1 test):
DictMethodsTests- validates Python dict method names as model propertiesExample
Each test exercises the generated Java client against TypeSpec definitions in
packages/http-specs/specs/and validates that reserved words and documentation formatting features are correctly handled by the generator.Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.