Chris HartjesSerious test-related question -- there is a bunch of code that relies on talking to an API that we do not control. How would YOU go about writing tests for code that relies on this API internally?
poetaster@grmpyprogrammer assume GIGO? When you say 'internally' do you mean without network? Ditto abstraction. Interface. Facade.
@poetaster By internally I mean our code generally wraps calls to it but there are also places we call it directly
@grmpyprogrammer ah, got it. I'd put a facade on that, but it sounds like work. With an abstraction like a facade you isolate the i/o ... Otherwise you are hooped. I've recently discovered one such case in a code base I maintain. I believed everything was using the same interface. Wrong. Lucky it was only 2 calls of 12 going directly. But it cost 2 hours to track.
To expand, tests on the interface, a facade, were easy. All input, known form, template. All returns, bounds, template. Tests have discrete file templates, used in one class. Api under control.