Tool With 33 Passing Tests Never Ran Once — No Schedule Was Set

A software team built a monitoring tool designed to scan four public sources daily for relevant product mentions, writing 33 tests that all passed before shipping. Despite thorough acceptance checks covering output limits, error handling, and duplicate removal, the tool had no scheduler attached, so it never executed and produced no results. Because a silent tool reports nothing, the failure went unnoticed until someone asked what the tool had found and the answer was simply nothing, ever. The team responded by writing a lightweight automated guard — 12 lines of code — that checks on every push whether any script claiming a daily schedule actually appears in a workflow file. They also configured the scheduled job to send a daily message even when it finds nothing, making silent failures immediately distinguishable from a job that has stopped running.