Skip to content

Add mocked HTTP tests for connectors that require operation parameters #142

@daviburg

Description

@daviburg

Several connector test files only cover constructor/null/Dispose scenarios and do not exercise any generated operation method. This is because all public operations on these connectors require parameters (no parameterless methods available).

Affected connectors (batch 4):

  • AzureAutomation — all operations need subscription/resourceGroup/account params
  • AzureDataFactory — all operations need subscription/resourceGroup/factory params
  • AzureDigitalTwins — all operations need hostname/input params
  • AzureVM — all operations need subscription params
  • Office365Groups — paginated return type, needs special handling

Action: Add mocked HTTP tests with representative parameter values for each connector. May also need to handle AsyncPageable return types in test assertions.

Deferred from PR #134 Copilot review.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions