VIP.LEAN Quality records browser tests in your own Chrome and stores them as readable YAML in your own Git repository. Every save is a commit you can review. Runs happen on your machine today and in your pipeline next, with a screenshot and a video for every step.
Your tests stay in your repository. Always.
Test suites nobody reviews.
They rot quietly, because the only place they can be read is inside a tool.Tools that hold the data.
Tests, results and credentials sit on someone else's servers, in someone else's format.Flows that break in production.
The login, the checkout, the one form every customer needs — found broken by a customer.The Chrome extension records what you click, with assertions, variables and reusable components.
The test lands as readable YAML in your repository, with a message, ready for a pull request.
Runs happen in your own Chrome now. The same engine will run the test in your CI pipeline.
What changes when your test tool treats your repository as the only place that matters.
Tests, components, suites, variables and results live in your Git repository as YAML. Every save is a commit against the loaded head; if the head changed, the save is refused, so nobody overwrites anybody silently.
in shortThere is no export button, because we never took anything.
Each browser holds its own key; the private half never leaves the device. Repository tokens are encrypted for those keys and stored in your own settings repository, with a keyring and an audit log. Our server never sees a token in cleartext.
in shortWe cannot read your tests, by construction.
Steps read as sentences, and targets are semantic — role, label, text — instead of brittle CSS paths. A pull request shows what changed in the test, not a wall of selectors.
in shortClick [Continue]. Type {{account_mail}} into [Email]. That is the test.
The Chrome extension records real clicks and runs the test locally in an incognito window. No remote grid to get started, and it reaches internal systems that never see the public internet.
in shortRuns where your app runs, behind your VPN if that is where it lives.
Secret values never appear in the YAML, in logs or in API responses. When the recorder sees a password field, it turns the text into a secret variable. Secret and 2FA variables are first class.
in shortA password never ends up in a commit.
Every run gives a per-step result with timing, a screenshot and a video, shown as a waterfall above the steps. Step history compares versions, and restoring an old one is just another commit.
in shortSee which step broke, how long it took, and what the screen showed.
For data protection this means: no personal data of your testers on our side, and your test data stays in your own repository.
| VIP.LEAN Quality | Record-and-replay SaaS | Code-only frameworks | |
|---|---|---|---|
| Where the tests live | Your Git repository, as YAML | The vendor's cloud | Your repository, as code |
| Who can write them | Testers, by recording and editing | Testers, by recording | Developers who write TypeScript or JavaScript |
| Review in a pull request | Yes, readable steps | Not in your repository | Yes, as code |
| Who holds your credentials | Your browsers and your repository | The vendor | You |
| Runs in CI | Local runs today, CI pipelines coming | In the vendor's cloud | Yes |
| Leaving the tool | Nothing to export, the files are already yours | Export, if offered | Nothing to export |
You should not have to retype what already works. We build importers for the test tools teams commonly use — some are available today, others are on the roadmap.
Importers work one way: your tests come into your repository, nothing is written back to the old tool.
If that is you, tell us what you want to test.
Write to us with your company, the Git platform you use, your team size, and what you want to test. We come back with a proposal for a first call.
In a Git repository of your workspace, as YAML files. Every save is a commit.
A record that your workspace exists and two encrypted token blobs that only your browsers can open. No test data, no results, no screenshots.
No. The repository tokens are encrypted for the keys in your browsers, and our server never calls your repository.
Your tests stay where they are, in your repository, in a readable format.
No. You record and edit in the browser. What comes out is a file a developer can read and review.
Recording and local runs happen in Chrome today.
Local runs work today. Runs in CI pipelines and on self-hosted runners are the next step of the roadmap.
An importer for a widely used record-and-replay format is available today, and importers for further tools, including Playwright, are on the roadmap. Tell us what you use.
Early Access starts with Bitbucket Cloud. GitHub, GitLab and Azure DevOps are on the roadmap.
There is no self-service pricing yet. Pricing is agreed with the programme partners before Early Access ends.
Tell us what you want to test. We suggest a first call, and the first recorded test happens in the first session.
.svg)
