Glossary

One word for each thing

BonaFident makes small changes to your code and checks whether your tests fail. It is mutation testing, scoped to the pull request. The landing page, the console, the CLI and the pull-request check all use the words below.

Terms

Mutant
A copy of your code with one small change, such as < turned into <=, that a good test should notice.
Killed
A test failed with the change in place, so your tests caught it; a kill by a crash or a hang is reported separately from a kill by an assertion.
Survived
Tests ran the changed code and all of them still passed, so no test noticed the change.
No coverage
No test executes this line, so BonaFident lists it but does not score it.
Timeout
The change made the code loop without end and BonaFident stopped it; it counts as killed, by the environment.
Runtime error
The test process failed to run the change at all, so it is excluded from the score.
Indeterminate
BonaFident could not run the change to a result, so it is excluded from the score and always shown with its reason.
Critical path
Code your policy names as critical (gate.strict_paths), where a single survived mutant blocks the merge.
Mutation score
Killed divided by killed plus survived: the share of decided mutants your tests caught.
Evidence Ledger
The Team plan’s tamper-evident record of verdicts, one hash-chained entry per merge. It is not signed yet.
BonaFident (check)
The name of the GitHub check BonaFident reports on each pull request. Branch protection can require it by this exact name.

What BonaFident supports

Languages and frameworks
TypeScript, JavaScript (ESM, CJS), React / JSX, Next.js, Vue SFC (partial), Svelte (partial)
Test runners
Jest, Vitest, on Node 22 or newer
CI
GitHub Actions (PR check), GitLab CI (merge request report), Bitbucket Pipelines (report only)
Not supported yet
Python, Go, Rust, Java

Reports as supporting evidence

No standard names mutation testing. A BonaFident report is evidence that changes were tested, and how well.

It can support the testing records behind SOC 2 CC8.1 (change management), PCI DSS 6.2.3 and DORA Article 25. It is not an audit opinion, and BonaFident holds no SOC 2 report of its own.

The Evidence Ledger on the Team plan is tamper-evident: each entry is hash-chained to the one before it. It is not signed yet.