Documentation
¶
Overview ¶
Command skipcheck runs this repository's tests and refuses to let a skipped row pass unnoticed.
THE PROBLEM IT SOLVES IS THAT A GREEN RUN LOOKS THE SAME EITHER WAY. The suite runs non-verbosely, so a skipped test prints nothing at all — and several rows here skip on conditions that are legitimate on one platform and a broken environment on another. A row needing a program that is not installed, a filesystem feature the account cannot use, a permission the runner does not have: each of them turns into silence, and silence is what a passing run is made of.
Three properties, and the third is the one that makes the first two worth having:
- every skip is printed, with the reason its author wrote;
- a manifest records which skips are legitimate on which platform;
- a skip nobody declared FAILS the run.
It wraps the test command rather than replacing it: the same arguments, the same exit code, and output that reads like the ordinary non-verbose run with a skip section added. Making the whole suite verbose would surface the same three lines inside ten thousand, which is a way of hiding them that also annoys everybody.
Source Files