Captr: capture the evidence while you test
Press record and keep testing. Captr takes timestamped screenshots, logs what you click, and notes CPU, GPU and memory use at each step. Afterwards, mark up the screenshots with arrows, text and boxes, and export the session as a PDF your developers can follow step by step.
What Captr does
- Timestamped screenshots
- A filmstrip of the session, each frame stamped with the date and time it was taken.
- User events
- Each click logged with the element’s name and role, so the steps to reproduce write themselves.
- System context
- CPU, GPU and memory use recorded alongside each screenshot.
- Annotation
- Arrows, text callouts and boxes, with numbered markers that tie each note to the event log.
- Export
- Export the whole session or just the screenshots you select as a PDF.
Why it matters
- Bugs found in exploratory testing are only as useful as the evidence behind them.
- Recording as you go means you stay focused on testing instead of stopping to take notes.
Good to know
- Captr records what happens on your screen. Close anything private before you start recording.
Questions
Does Captr record video?
Captr records a sequence of screenshots with the events and system readings around them, which is easier to annotate and share than a video.
Can I choose which screenshots go in the report?
Yes. Use Export Selected to export only the screenshots you pick.
Also in Holstr
Bring your next test session into one place
Get Holstr, or book a demo and see the whole workspace in action.