rule · _guidelines/spec/5.3 · s-xhcmchcngykvn2k

Tests at a push in a draft

Checkedconfirmed by its owner

While a project's specification is a draft, neither the tests of the system's code nor those of the project's own checks and generators are run at a push.

Why

A draft is above all work on the specification, the code and the tests secondary in it, and a push that waited for every test would slow that work. The tests of the project's own checks and generators go with those of the system's code, since a push runs them together (§s-jau82aq9juv9zzh).

The links it makes

refines → What is checked, when, and what a failure costs

The links made to it

cites ← What is checked, when, and what a failure costs
implements ← The tests, run before a push

The decisions taken on it

2026-11-06 · textual

Problem: A push in a draft waited for every test, though a draft is above all work on the specification.
Ruling: The owner: while the specification is a draft, the tests need not run at a push, to keep the work quick.