Commit message test plans (opens in new tab)

Intended audience Software engineers who already write test plans in commit messages or code review descriptions. People working with patch stacks or stacked diffs. Origin Private correspondence re Julio Merino's post . Mood Practical. Why How Patterns Script Related posts Comments Julio Merino recently published , about using Markdown itself as a lightweight test format. That reminded me of a related workflow I’ve been using for a while with scrut: I put executable test plans directly in com...