Visual QA and bug reporting with AI
Record a test journey, annotate the evidence and review the fix on the same board. Vitrinka keeps the context attached to the work.
Start free01
Record the journey once
Turn on the browser recorder and test your application as usual. Screenshots, interactions, network calls and your notes become a reviewable journey; on a phone, the recorder mounted in your own web app does the same. A developer can see the path that led to the issue instead of asking you to repeat it. Recording scope and masking are configurable; check the capture guide before testing sensitive flows.
Read the guide02
Point to the problem
Draw a region on a screenshot and explain what looks wrong. The annotation stays beside the screen, its discussion and the work item. Reviewers can work in the browser while a connected coding agent picks up the queue. The full workflow and access requirements are documented in the board guide.
Read the guide03
Review the result where you reported it
Recorded sessions can be distilled into issues for triage. A connected agent can work on an issue and return evidence of the change. Your automated suite reports to the same place: wrap it in vitrinka qa run and its results land on the feature's QA record, where a review can check the screenshots against your team's rules. Compare the before and after, review the discussion and decide whether the result is accepted. The evidence supports your judgement; a completed agent run is not a substitute for acceptance testing.
Read the guideTest runs, in depth