9 projects
assay-checks
Audit the checks, and find the answers your tree already has: could those tests have failed, and does the tree already answer this?
zerocase
A check with a zero denominator reports clean. Read the junit/TAP/lcov/eslint report the runner already wrote and put a floor under what actually ran.
restore-verified
Temporarily modify a file, survive the signal, and prove the tree came back.
didrun
An exit code cannot tell you whether anything happened. Did it RUN, did it FAIL, and was the failure the RIGHT one.
undetermined
Point it at a program, get back what can and cannot be determined: a constant with an error bar, and an explicit undetermined list with reasons.
countfn
How does this function's cost scale? Counted, not timed -- and UNDETERMINED when no complexity class settles.
nondet
Run a function in fresh processes and see if it answers the same. A witness is a fact; agreement is not.
canfail
Break the thing on purpose and check that your check notices. A guard that never fails may be incapable of failing.
ladderpin
Freeze what a function answers and report when that changes. assay's bundle, read in the other direction: the finding is difference, not sameness.
