ABOUT The person behind it

I'm Doron.
I build TestVault.

TestVault reads your app, writes the tests, runs them in real browsers, and repairs the ones that break. This page is why it works that way — and what that cost to find out.

Doron, who builds TestVault
Doron Benita
Founder
why it works this way

Your app changes.
The tests keep up.

Most suites are written once and then rot. The app moves, a selector changes, and a red build slowly teaches the team to ignore red builds. The suite is still there. It just stops meaning anything.

So TestVault starts from your running app, not a spec. It signs in with credentials held in an encrypted vault, crawls what is actually there, proposes a plan mapped to what it found, and writes Playwright tests against the real DOM. When one breaks, it attempts a repair and re-runs until the fix holds.

That is the product. The part I care about more is what it does when it is wrong about itself.

what I hold it to

What you can rely on

Grounded, not guessed

Every test comes from a real, authenticated crawl of your app, with selectors taken from the live DOM. A test written from a description of your product is a guess about your product.

Proven before trusted

A test does not count as coverage because it exists. It counts once it has been verified and has passed at least once. New and repaired tests go through a gate that re-runs them to show they are not flaky — and those re-runs are free, because they are our uncertainty, not yours.

Every number says what it is out of

A pass rate carries the share of the plan it covered. A schedule states how many tests it will run. A timestamp names its time zone. A percentage without the number it came from is not a measurement.

Two things I will not do

I will not block your runs. If you're out of tokens your suite still runs, still reports, and is still recorded. Refusing to run a test against your own application isn't a decision I'm willing to make for you.

I will not sell what is not built. Capabilities that were once advertised here before they existed have been taken off the site, and a test in the codebase now fails the build if a plan promises one.

I would rather lose a sale to an honest limitation than win one and have you find it mid-release. Every rule above exists because that is far easier to say than it is to do.

Doron Benita
Founder, TestVault · get in touch

Start where the doubt is.

Connect one app and watch a real suite build itself. The free plan needs no card, and PRO starts at $49/month when you outgrow it.