Skip to content

Test execution integrity

EXEVRA

A green CI run is not enough. Prove that the tests your repository promised to execute actually ran.

Exevra runs one configured test command, requires fresh JUnit XML reports, and compares suite execution with a reviewed baseline. It detects missing reports, zero execution, policy breaches, and test-identity drift.

By default, identity diagnosis keeps raw test names out of the baseline and ordinary output. It records opaque fingerprints and reports safe missing and added counts instead. Teams can explicitly opt in to readable names for a protected suite when that is appropriate for their repository.

Exevra v0 accepts JUnit XML only. It does not assess test quality, assertions, code correctness, or whether a change is safe. It has no hosted service, accounts, GitHub API calls, pull-request comments, remote artifact lookup, or matrix aggregation.

Start with the quick start to create and commit a baseline.