I am using a Github repo, linked to Travis CI - Travis can do cron/scheduled builds (daily works for me). On build failure, including if any of the tests fail,

I am using a Github repo, linked to Travis CI - Travis can do cron/scheduled builds (daily works for me). On build failure, including if any of the tests fail, I receive notification. Some of my tests use mocks, others hit live remote/third-party services. If anything external component/system changes, or is down, I get to know about it, and can decide what is the best action to take. Sometimes it’s nothing more than a network glitch / service outage, but sometimes endpoints change and/or return different data. You should definitely consider setting up a monitoring service for your app’s live HTTP endpoint. There are online services that may provide the functionality you require, but otherwise it’s NBD to write your own. It can be a good idea to run monitoring from a different network, e.g. a different host, from the office, from home (or all of these). Bespoke monitoring code can sometimes/often leverage code that you already have in your tests. (Almost bringing us full circle, and back to CI)