Dovada.
01 / 09
Dovada

Your tests pass. That is not proof.

Dovada examines each ticket and each release automatically. It finds the tests that run the changed code and judges if they prove the change. Dovada shows how it reached each answer.

A test your last release relied on

This test runs, and it passes.

it('sends an alert', () => {
  alertOnCallIfDead(deadDelivery)
  expect(sendAlert).toHaveBeenCalled()
})

The test does not examine the text of the alert or who receives it. It also does not show if the alert starts after the third failure or after the first. CI shows green, but the test proves almost nothing.

Dovada found the problem. The next slide shows it.

One record · DEMO-112
One ticket. Two answers that differ.
/dovada/cer/14
View of the Change Evidence Record (CER) for DEMO-112. Validation reads Aligned and Verification reads Discrepancy.
What a summary does not show · DEMO-111
The ticket reads Done. No code shipped.
/dovada/release/DEMO-1.1.0
Release View: DEMO-1.1.0, with an Unshipped Ticket finding
How Dovada makes each answer

Two axes, assessed independently

Validation
Did we build the right thing?
Dovada compares each requirement of a ticket with the pull requests for that ticket. It judges each requirement alone. It does not give one score for all requirements.
Verification
Did we prove it works?
Dovada starts from the code that changed. It traces imports and calls to the tests that exercise this code. Then it judges if each link is meaningful.

Each judgment above is one call to a model. Today the model is Claude. The call uses your Anthropic account and your contract, not an account of Dovada. Dovada plans to add other providers.

In the package
Some linked tests do not count

To read a full Claims sheet, open the sample package.

/dovada/package-document/3 · Claims
The Claims sheet shows one test judged meaningful and a second linked test judged not to exercise the code.
Observed Coverage
Tests in a test repository
/dovada/package-document/5 · Claims
The Claims sheet for DEMO-110. A Tool Observed claim lists three observed tests that passed and were not assessed.
In the package
Tests that might be missing
/dovada/package-document/3 · Coverage Observations
The Coverage Observations sheet shows three missing-test gaps in two tickets.

Evidence, not verdicts.

Dovada does not make the release decision. It gives evidence for each ticket and each release. A person uses this evidence to decide GO or NO-GO.

Validation asks if we built the right thing. Verification asks if we proved that it works.

Or open a sample package on its own.