A crucial little caveat to my statement that automated tests aren’t automated if they don’t run automatically: All your automated tests should fail.
… at least once, anyway.
In the thick of implementing a new feature and coding up a bunch of tests for it, it’s easy to forget to run each one to make sure they’re actually testing something. It’s great to work in an environment where all you have to do is type make test or npm run test and see some green. But if you only ever see green, you’re missing a crucial step.