␣⌘Test rounds

Test files get a third state: a test can pass, fail, or not have been run yet. When a round is finished, New Round unticks every test and logs the version it was run on, so the file shows which versions have been tested. The panel is on the left and the file it writes is on the right. Click a box to step it through not run, pass and fail, or ⌥-click to fail it straight away. Hover over the “Hand tests” heading for ↺, or right-click it.

The panelThe project, scrolled to its test file.
TESTING.mdAs Space Command writes it.
BUGS.mdWhere New Round logs the failures you pick (its end shown).

How it works

  1. Three states, test files only. In TESTING.md, TESTS.md and TEST.md a box can be not run, pass or fail. Every other file keeps two states.
  2. Click (decided, question 37): a click steps the box through not run, pass and fail, then back to not run; ⌥-click fails it in one go, or clears a fail.
  3. Fail in Markdown (decided, question 38): the box stays open and the line gets a #fail tag, so GitHub and Obsidian show an open box with the tag: still to do.
  4. The tally: passed, failed and still to run, with the bar in Moss and Terracotta. A failed test counts as open in the panel's progress and on the health card, since it needs a fix and another run (decided, question 39).
  5. New Round is never automatic. Once every test has been run, the section offers a new round. It's also there at any time, from ↺ on the heading or the heading's right-click menu. The version comes from the top CHANGELOG.md entry, and you can change it before confirming.
  6. One write, one undo. A new round unticks the tests, clears their Result lines (on by default, decided, question 40), and adds one line to the round log, under the title (decided, question 41): the date, the version the new round is for, and how the last round ended. ⌘Z puts it all back.
  7. Failures become bugs, if you pick them. When the round has failures, New Round lists them, each ticked, to add to BUGS.md (or TODO.md when the project has none, decided, question 44) as open bugs, written the way that file's other entries are, with the version and the Result note. A failure already logged and still open is left alone, so a test that fails two rounds running isn't logged twice. The same ⌘Z undoes both files. Fixing the bug doesn't untag the test: it keeps #fail until it passes in a later round (decided, question 45).