QA & Testing
Record the evidence once — the path for testers.
Recording replaces reporting
You know the journeys, and you have already reproduced every bug once — while testing. In most teams that evidence is thrown away and survives only as a ticket that half-describes the issue, so a developer spends a day re-reproducing what you watched happen.
Here the recorder runs while you test. Screens, clicks, network calls, console errors and your annotations are captured as they occur; the server turns the run into a reviewable board and the issues into work items. The reproduction is the report — you never write it up. Automated suites feed the same record: vitrinka reads what your test runner leaves behind and never drives a browser or a device itself.
The path
| Page | What it covers |
|---|---|
| Browser extension | The Chrome extension: install it, link it to your server, map domains to projects, record with the on-page capsule. |
| React and web apps | @vitrinka/web — the recorder inside your own web app, for phones and browsers without the extension. |
| Expo and React Native | The journey recorder for mobile apps. |
| What the recorders capture | The published capture contract — exactly what is taken and where it goes. |
| Annotating boards | Circle a region, one sentence — and what happens to it after you do. |
| Review toolkit | The team's review rules, the audited judge, text maps beside screenshots, eleven mechanical checks, findings anchored to on-screen text. |
| Recorded sessions | The pipeline that turns a recorded run into fixes, tests and tickets. |
| Test runs and the QA record | QA plans as journeys, and vitrinka qa run -- <test command> folding your runner's results into the feature's QA record under the project's Record › QA. |
| Bug-report widget | A report button inside your own app, quarantined until an admin approves it. |
Testing side by side with a developer — the recorder's ⌖ snaps landing in their session while you keep testing — is Pairing.
What changes for you
- No repro steps. The session carries the exact walk, per screen, with the network and console underneath it.
- No screenshot folders. Every screen you touched is already on the board, in the order you walked it.
- One sentence per bug. An annotation is a region and a sentence; everything else is attached automatically.
- You stay the judge. Fixes come back to the same board with proof, and nothing is resolved until you accept it.