Serious 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?
@kboyd @grmpyprogrammer yep.
1. write abstraction wrapper layer
2. write tests (of the consumers) with mocks for that layer
3. write integration tests for that layer that call the other API.
The tests in 2 run all the time as part of your automated tests of your consuming code, the tests in 3 run periodically, maybe not even automatically, and confirm that your integration with the 3rd party still works.
(and no, that's NOT how some of our tests work, but if I had a magic wand....)
If wishes were horses, I'd be making a killing in the manure market.