Commit message test plans

I agree.

But I guess there are some rare, valid exceptions in which you want to have a test just at the commit level (like the ad-hoc and diff example). In those cases, you might as well write them as executable commands in your commit message.

• This is for a different stage in the feedback loop. An entire test suite run could take minutes or hours, depending on your situation. (If you can run your entire test suite quickly, then certainly do so.)
• Even if you run the entire test suite, you don't retain historical information like "this test used to meaningfully fail at some point in development, but passes in the end result", which is valuable information.