Skip to content

Add e2e tests for documentation and specialwords spector scenarios#9340

Draft
Copilot wants to merge 2 commits intomainfrom
copilot/add-spector-tests-for-tsp
Draft

Add e2e tests for documentation and specialwords spector scenarios#9340
Copilot wants to merge 2 commits intomainfrom
copilot/add-spector-tests-for-tsp

Conversation

Copy link
Contributor

Copilot AI commented Jan 13, 2026

Adds missing end-to-end test coverage for TypeSpec spector scenarios in documentation and specialwords packages following patterns established in PR #9172.

Tests Added

Documentation package (6 tests):

  • BulletPointsOpTests - validates bullet point rendering in operation docs
  • BulletPointsModelTests - validates bullet points in model/enum documentation
  • NumberedTests - validates numbered list formatting
  • BoldTextTests - validates bold text formatting (**text**)
  • ItalicTextTests - validates italic text formatting (*text*)
  • CombinedFormattingTests - validates nested bold/italic combinations

SpecialWords package (1 test):

  • DictMethodsTests - validates Python dict method names as model properties

Example

@Test
public void testBulletPointsModel() {
    client.bulletPointsModel(new BulletPointsModel(BulletPointsEnum.SIMPLE));
}

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

This section details on the original issue you should resolve

<issue_title>tsp, fill spector tests</issue_title>
<issue_description>Refer to this PR to see test cases that should be added: https://github.com/microsoft/typespec/pull/9172/files

documentation and specialwords should be supported and can add tests.

Follow https://github.com/microsoft/typespec/blob/main/.github/instructions/http-client-java.instructions.md#add-end-to-end-e2e-test-case for the steps.

.tsp files can be found in https://github.com/microsoft/typespec/tree/main/packages/http-specs/specs and https://github.com/Azure/typespec-azure/tree/main/packages/azure-http-specs/specs
</issue_description>

<agent_instructions>Follow https://github.com/microsoft/typespec/blob/main/.github/instructions/http-client-java.instructions.md#add-end-to-end-e2e-test-case for the steps.

.tsp files can be found in https://github.com/microsoft/typespec/tree/main/packages/http-specs/specs and https://github.com/Azure/typespec-azure/tree/main/packages/azure-http-specs/specs</agent_instructions>

Comments on the Issue (you are @copilot in this section)


✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

Co-authored-by: haolingdong-msft <87355844+haolingdong-msft@users.noreply.github.com>
Copilot AI changed the title [WIP] Add Spector tests for TypeSpec files Add e2e tests for documentation and specialwords spector scenarios Jan 13, 2026
@microsoft-github-policy-service microsoft-github-policy-service bot added the stale Mark a PR that hasn't been recently updated and will be closed. label Feb 12, 2026
@timotheeguerin timotheeguerin added the emitter:client:java Issue for the Java client emitter: @typespec/http-client-java label Mar 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

emitter:client:java Issue for the Java client emitter: @typespec/http-client-java stale Mark a PR that hasn't been recently updated and will be closed.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

tsp, fill spector tests

3 participants