Skip to content

VeritasWhat does your test actually guarantee?

Specification-aware test verification for TypeScript and Vitest — backed by mutants, counterexamples and proofs, not a score.

Thirty seconds ​

bash
npm install -D @under18dev/veritas
npx veritas init --yes
npx veritas run --profile standard

On the small project from the tutorial, whose README says "1000 or more" while the code says total > 1000, the run reports:

text
run run-20261120T105459627Z-000-0ed704  verdict: pass_with_warnings (exit 0)
[...]
succeeded   mutate
            mutator 0.4.5: succeeded
            counts: {"killed":16,"survived":1}
[...]
succeeded   assess
            assessments: {"weak_or_incomplete":2,"meaningful_with_evidence":2,"tautological_or_disconnected":1}; 3 finding(s)
[...]
findings (3):
  F-0b43c88cc3a6  [confirmed medium] no test detects total > 1000 -> total >= 1000 at src/pricing.ts:3
  F-89435b62ae1e  [suspected medium] src/pricing.ts#discountAmount may not satisfy "total >= 1000"
  F-99e71509e3c4  [suspected low] test "pricing works" does not check project behaviour

Veritas does not tell you that your tests are "87% good". It tells you which specification each test checks, which faults it would catch, what has been checked formally and within which bounds — and what is still unknown.

Released under the Apache-2.0 License.