Dovada. Release evidence that builds itself

Dovada collects evidence as your team works. It does not wait for the release.

Did we build it,
and did we prove it?

Dovada reads your tickets, your pull requests and your test runs. It makes the release evidence package for Release Managers, QA Leads and Engineering Leaders.

Works with today

The first page of a sample release evidence package. It shows the release, the trigger, and the verdicts: two tickets Aligned, one Discrepancy, one Nothing to verify and one Unshipped ticket. A sample release evidence package, made from demo data. The person who decides on a release reads it to see what was examined.

Why now

When code moves faster, confidence needs evidence.

Confidence in a release came from the hours that people spent to write and review each change. Those hours showed that someone examined the change.

When teams use agents to write code, the change can grow faster than people can review it.

Dovada gives evidence for each change, so that the person who decides can see what was examined.

What shipped that nobody asked for. What was asked for that nobody shipped.

Watching continuously next check · 6 stages
Intent Jira · acceptance criteria Implementation GitHub · diffs, commits Verification evidence CI · tests, executions Validation did we build the right thing? Verification did we prove it works? Release evidence assessments insert-only · no deletes pinned at release · never shifts
Intent Implementation Test evidence Proved Nobody asked for it

What comes out

Dovada validates each change against the request for it. It verifies each change with the tests that exercise it. It judges if each test proves the behavior. A test that only ran is not enough.

Each verdict cites the evidence that Dovada judged. The citation is a pointer that a query can follow. It is not prose. If the criteria change and Dovada judges again, the earlier verdict stays on record beside the new verdict.

One verdict from a sample package. The verdict is Not Met for a test that exercises the on-call alert path. The reasoning says the only linked test mocks the alert call and would pass even if the alert message or recipient were wrong. A verdict from the sample package, made from demo data. Dovada judged that the only test for this behavior does not prove it.

Observed Coverage

Tests in a different repository, linked to the code they ran.

Your tests can be in a different repository. A collector in your test pipeline records which code each test ran. Dovada does not run your tests.

Dovada links each test to that code. The package shows the link as Tool Observed. A config flag controls if Dovada judges these tests. The flag is off by default.

One verdict from a sample package. The reading is Tool Observed. The reasoning says three tests in a different test repository were observed running the code of this behavior, and were not assessed. The cited evidence lists the three tests. A verdict from the sample package, made from demo data. Three tests in a different test repository ran this code. Dovada shows them as Tool Observed.

What Dovada is not

Evidence, not verdicts.

Who builds this

JS

I am Josh Strimbu. I worked for thirty years across the software lifecycle, from manual testing to staff-level SDET and automation architect. I assembled this evidence by hand many times. I saw teams ship because a build was green, when the build proved nothing about the request.

Dovadă is the Romanian word for proof. Romanian is also the language of my grandparents.

Before it ships

I talk to the people who do this today.

Are you responsible for a release? You can be in release management, QA leadership, engineering or governance. I want thirty minutes to hear how you assemble evidence today, what fails and who asks you for it. Then we can discuss where Dovada fits in your release cycle.

josh@dovada.dev