I also read about tests that compare the mockups and stubs with the original implementations, but it sounded like overkill to write tests for your tests.
Yes, at some point you get diminishing ROI :) We were OK with having the pipeline fail due to a change in the live API that our mocks didn't emulate, then we'd go update our mocks (and fix the code).
It happened infrequently enough that it wasn't worth the effort to automate the testing of the mocks against the live APIs.
Though honestly, for internal APIs owned by sister teams, this was usually due to a bug/non-backward-compatible change on their side, and we'd work with them to fix their APIs.
It happened infrequently enough that it wasn't worth the effort to automate the testing of the mocks against the live APIs.
Though honestly, for internal APIs owned by sister teams, this was usually due to a bug/non-backward-compatible change on their side, and we'd work with them to fix their APIs.