[BUG] Azure.Communication.Chat is not mockable

[cmeyertons]

Library name and version

Azure.Communication.Chat 1.3.1

Describe the bug

The Azure Communication Chat library is not mockable.

Especially for a service that I cannot emulate locally, I need to be able to mock out the interactions with it.

Expected behavior

I would expect the library to adhere to the design guidlines for testability:

https://learn.microsoft.com/en-us/dotnet/azure/sdk/unit-testing-mocking?tabs=csharp

Actual behavior

I cannot mock:

• CreateChatThreadResult
• ChatThreadProperties
• there's probably many more

Reproduction Steps

n/a

Environment

No response

[github-actions]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @acsdevx-msft.

[jsquire]

Hi @cmeyertons. Thanks for reaching out and we regret that you're experiencing difficulties. To our knowledge, the Chat library is following Azure SDK standards for mockability and testing. As the unit testing article describes in the note from this section:

Some input models have read-only properties that are only populated when the model is returned by the service. In this case, a model factory method will be available that allows setting these properties.

The types that you're asking about fall into that category and can be created using the ChatModelFactory:

• CreateChatThreadResult
• ChatThreadProperties

If there are types that are not publicly constructable and do not exist in the model factory, please let us know so that we can make the necessary adjustments.

[github-actions]

Hi @cmeyertons. Thank you for opening this issue and giving us the opportunity to assist. To help our team better understand your issue and the details of your scenario please provide a response to the question asked above or the information requested above. This will help us more accurately address your issue.

[github-actions]

Hi @cmeyertons. Thank you for opening this issue and giving us the opportunity to assist. We believe that this has been addressed. If you feel that further discussion is needed, please add a comment with the text "/unresolve" to remove the "issue-addressed" label and continue the conversation.