You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @pyrocumulus, nice library, I'm using it in an upcoming Windows Service that syncs GoodWe API to PVOutput. Somewhere in that code, I have a class that wraps your PVOutputClient for configuration and DI purposes, and it has a property:
public PVOutputClient ApiClient { get; }
Now I want to test that my code calls your code, without actually calling your code, it being test data and all which I don't want to be sent to PVOutput.
Could you consider interfacing the PVOutputClient and its services, so it can be mocked for unit tests?
The text was updated successfully, but these errors were encountered:
First of all, thank you for the kind words! It's nice to hear you are using it, I always hoped it would be useful to someone someday👍🏻
About your feature request, no problem. I understand that you need it for unit testing, it's how I use it myself as well. Until now I never looked at my library from an outside unit test standpoint.
Thanks for the PR as well, I'll review it the coming days and integrate it 🙂
Hi @pyrocumulus, nice library, I'm using it in an upcoming Windows Service that syncs GoodWe API to PVOutput. Somewhere in that code, I have a class that wraps your
PVOutputClient
for configuration and DI purposes, and it has a property:Now I want to test that my code calls your code, without actually calling your code, it being test data and all which I don't want to be sent to PVOutput.
Could you consider interfacing the
PVOutputClient
and its services, so it can be mocked for unit tests?The text was updated successfully, but these errors were encountered: