Reaction SDK(.NET): Add explicit Unit Tests for ManagementClient and ResultViewClient

[amansinghoriginal]

⚠️ Contributor & GSoC Rules ⚠️

To ensure a fair and manageable process for all contributors (including Google Summer of Code applicants), please follow these rules:

1. Do NOT open a Pull Request unless you have been assigned to this issue. Unassigned PRs will be closed without review.
2. To get assigned: Leave a comment below explaining where in the codebase you will implement this, and a 1-2 sentence description of your approach. The maintainers will assign it to the first coherent proposal.
3. You may only be assigned to one "good first issue" at a time.
4. If there is no update within 4 days, we may have to reassign the issue to another contributor.

---

Area for Improvement

Currently, the .NET Reaction SDK has a test project located at reactions/sdk/dotnet/Drasi.Reaction.SDK.Tests/. However, it only contains tests for the core ReactionTests (like the ReactionBuilder).

The core services located in reactions/sdk/dotnet/Drasi.Reaction.SDK/Services/, specifically the ManagementClient and ResultViewClient, completely lack unit test coverage. This leaves a gap where networking logic, API endpoint paths, and JSON deserialization might silently break during future refactoring.

Desired behavior

The test suite in Drasi.Reaction.SDK.Tests/ is expanded to include comprehensive unit tests for both ManagementClient and ResultViewClient, ensuring our HTTP integrations with the Drasi backend are robust and tested.

[hungnguyen1607]

Hi @amansinghoriginal , I am planning to make 2 new test files ManagementClientTests.cs and ResultViewClientTests.cs that utilize custom MockHttpMessageHandler to basically simulate the HTTP responses, essentially helping to do the unit test on the API endpoint paths, json deserialization etc.

Please let me know If i can take care of this issue. Thank you!!!

[Shanzita]

Hello @amansinghoriginal sir, I am currently waiting to be assigned on #413 (Python ResultViewClient) and, while digging deep into the SDK for that, this issue also caught my attention.
One thing I noticed is that both ManagementClient and ResultViewClient are currently creating their own HttpClient internally, and this makes them a bit tricky to unit test without some changes to the class first. I'd like to change this to inject HttpClient via the constructor, and this is the standard approach in .NET.
Once this is in place, I'd like to add ManagementClientTests.cs and ResultViewClientTests.cs with tests for the happy path, HTTP errors, malformed JSON, empty result sets, cancellation in the middle of the stream, and null handling.
I'd love to take this over after #413 is complete if that's assigned !

[Shanzita]

Hello @amansinghoriginal sir ! Following up if I can work on this issue and get assigned. Thank you !

[amansinghoriginal]

Thanks for the proposal @hungnguyen1607 — assigning this to you!

Please keep us updated on your progress. As a reminder, if there is no update within 4 days we may need to reassign.

[amansinghoriginal]

Thanks for the interest here too @Shanzita! Since you've been assigned #413, we'll go with another contributor for now per the one-at-a-time rule. Once you've wrapped up #413, feel free to comment on any open issues you'd like to take on next!

[hungnguyen1607]

Thank you I will gladly take this