Question: Advice on testing

[scott-david-walker]

As the title states, can anybody give some advice about mocking/faking this project?
Looking at the tests inside the project, they actually test against an actual GPT instance and doesn't provide a way around this?

Thanks

[StephenHodgson]

There is a proxy csproj you could probably use to mock this a bit easier. I just like to test against the real deal, since the API changes too frequently.

[scott-david-walker]

Yes, but to be able to mock or fake any class, it would either need to implement an interface or the class would have to have virtual methods. That alongside the immutability makes it nearly impossible for an implementer to fake the call to GPT when testing. And I'd argue that being able to fake a call to an external service is of vital importance when unit/integration testing. We could have a factory for each of the response classes that allows them to be created for testing purposes, but this would require the setter to be made internal on all of the necessary properties. I'd happily implement this, but I'd need some agreement from you on how we should approach it, as I'd rather not put in the effort just to end up with no solution. Thoughts?

[StephenHodgson]

let me think on it. I'm sure there's a way to test against fake proxy service without changing the core project.

Just seems unnecessary to change your whole client library just to enable mock tests. less is more.

[scott-david-walker]

Normally I'd agree, but when your client library acts as an interface to an api, I think it becomes more important. I look forward to hearing your thoughts on a possible solution.

[baramartin]

Any news on this? I am currently updating from version "6.8.7" to "7.7.6" and it broke my working unit tests.
The issues is I have is the following:

I created a wraper around your service for the calls I need in order to be able to test my logic to various responses. With the version I used before, I was able to construct some of your response classes, such as 'ChatResponse', 'Choice', etc.. This is no longer possible due to constructors becoming private. I also tried deserializing them from Json, but obviously that didn't work at all either since the setters are private too.

[StephenHodgson]

Any news on this? I am currently updating from version "6.8.7" to "7.7.6" and it broke my working unit tests.

I suppose take baby steps with each release.
I keep the change log pretty well documented, and document all of the breaking changes and typically follow SemVer.