Runs

• Runs: cases chosen in a window with the suite tree down to single cases — tick whole suites (with nested ones) and single cases, find a case by title or key — then narrowed by tags, priority and status, with a preview of the count (API: selection.pick); build and environment; closing and reopening.
• Execution: statuses of the case and of individual steps, a comment, time spent, hotkeys (1–5 — result, ↑/↓ — move), automatic move to the next untested case, the history of a result.
• A run copies the case version at the moment it is added: editing or deleting the case does not change what was tested. If the case has changed, the run offers to update it to the new version.
• A run can have an icon left of its name: a desktop tower, the letters PS, the letter X, a robot, an apple, smoke, an exclamation mark. It is chosen when the run is created and changed with “Name and icon…” in the run’s menu.
• The list of runs: “Pin to the top” in a run’s menu puts it first for the whole team. The archive takes closed runs out of the list; reports still count them. A closed run can be rerun: a new run of the same cases at their current versions, with no results, under a new name, in the current sprint by default.