Skip to main content
Expanded and added links for the abbr.'s, etc. to make it less cryptic. Used more standard formatting (we have italics and bold on this platform).
Source Link
Vector Zita
  • 2.5k
  • 10
  • 20

Absolutely. We have been caught out by this with Microsoft APIs, for example, and we were not even set up to log that in our Azure function application. So all we saw was that requests to our endpoints failed. It changed without any warning between hand testing / UAT and actual live use of our application.

Our unit tests still worked of course, because they used the schema from the Microsoft documentation (which had not been updated). I only knew because some other kind developer commented on the Microsoft documentation!

Make sure to log what you actually get as request from external APIs to your endpoint / as response to your call and throw meaningful errors (as appropriate) in your application.

This actually gives me the willies with our current project, which relies on many external APIs - we have monitoring functions and E2E tests with Cypress for vital functions running every so often, so at least we know when it happens. We are still working toon how to reliably know in advance...

Absolutely. We have been caught out by this with Microsoft APIs, for example, and we were not even set up to log that in our Azure function application. So all we saw was that requests to our endpoints failed. It changed without any warning between hand testing / UAT and actual live use of our application.

Our unit tests still worked of course, because they used the schema from the Microsoft documentation (which had not been updated). I only knew because some other kind developer commented on the Microsoft documentation!

Make sure to log what you actually get as request from external APIs to your endpoint / as response to your call and throw meaningful errors (as appropriate) in your application.

This actually gives me the willies with our current project, which relies on many external APIs - we have monitoring functions and E2E tests with Cypress for vital functions running every so often, so at least we know when it happens. We are still working to how to reliably know in advance...

Absolutely. We have been caught out by this with Microsoft APIs, for example, and we were not even set up to log that in our Azure function application. So all we saw was that requests to our endpoints failed. It changed without any warning between hand testing / UAT and actual live use of our application.

Our unit tests still worked of course, because they used the schema from the Microsoft documentation (which had not been updated). I only knew because some other kind developer commented on the Microsoft documentation!

Make sure to log what you actually get as request from external APIs to your endpoint / as response to your call and throw meaningful errors (as appropriate) in your application.

This actually gives me the willies with our current project, which relies on many external APIs - we have monitoring functions and E2E tests with Cypress for vital functions running every so often, so at least we know when it happens. We are still working on how to reliably know in advance...

Expanded and added links for the abbr.'s, etc. to make it less cryptic. Used more standard formatting (we have italics and bold on this platform).
Source Link

Absolutely. BeenWe have been caught out by this with MSMicrosoft APIs, for example, and we were not even set up to log that in our AzureAzure function appapplication. So all we saw was that requests to our endpoints failed. Changed with noIt changed without any warning between hand testing / UATUAT and actual live use of our appapplication.

Our unit tests still worked of course, because they used the schema from the MS docsMicrosoft documentation (which had NOTnot been updated). I only knew because some other kind devdeveloper commented on the MS docsMicrosoft documentation!

Make sure to log what you actually get as request from external APIAPIs to your endpoint / as response to your call and throw meaningful errors (as appropriate) in your appapplication.

This actually gives me the willies with our current project, which relies on many external APIs - we have monitoring functions and e2eE2E tests with CypressCypress for vital functions running every so often, so at least we know when it happens. StillWe are still working to how to reliably know in advance  ...

Absolutely. Been caught out by this with MS APIs, for example, and we were not even set up to log that in our Azure function app. So all we saw was that requests to our endpoints failed. Changed with no warning between hand testing / UAT and actual live use of our app.

Our unit tests still worked of course, because they used the schema from the MS docs (which had NOT been updated). I only knew because some other kind dev commented on the MS docs!

Make sure to log what you actually get as request from external API to your endpoint / as response to your call and throw meaningful errors (as appropriate) in your app.

This actually gives me the willies with our current project, which relies on many external APIs - we have monitoring functions and e2e tests with Cypress for vital functions running every so often so at least we know when it happens. Still working to how to reliably know in advance  ...

Absolutely. We have been caught out by this with Microsoft APIs, for example, and we were not even set up to log that in our Azure function application. So all we saw was that requests to our endpoints failed. It changed without any warning between hand testing / UAT and actual live use of our application.

Our unit tests still worked of course, because they used the schema from the Microsoft documentation (which had not been updated). I only knew because some other kind developer commented on the Microsoft documentation!

Make sure to log what you actually get as request from external APIs to your endpoint / as response to your call and throw meaningful errors (as appropriate) in your application.

This actually gives me the willies with our current project, which relies on many external APIs - we have monitoring functions and E2E tests with Cypress for vital functions running every so often, so at least we know when it happens. We are still working to how to reliably know in advance...

Source Link

Absolutely. Been caught out by this with MS APIs, for example, and we were not even set up to log that in our Azure function app. So all we saw was that requests to our endpoints failed. Changed with no warning between hand testing / UAT and actual live use of our app.

Our unit tests still worked of course, because they used the schema from the MS docs (which had NOT been updated). I only knew because some other kind dev commented on the MS docs!

Make sure to log what you actually get as request from external API to your endpoint / as response to your call and throw meaningful errors (as appropriate) in your app.

This actually gives me the willies with our current project, which relies on many external APIs - we have monitoring functions and e2e tests with Cypress for vital functions running every so often so at least we know when it happens. Still working to how to reliably know in advance ...