1 Introduction
FlowMint Test Evidence is a browser extension that lets you record user actions (clicks, typing, form submits, navigation) with screenshots, generate a report with all steps and images, and export as PDF, HTML, or JSON. Built for QA and documentation — capture test evidence without writing code.
All data is stored locally in your browser; no external servers or analytics.
2 Installation
Install FlowMint Test Evidence from the browser store — no build or command line required.
- Open the Chrome Web Store (or Edge Add-ons / Firefox Add-ons).
- Search for FlowMint Test Evidence or use the direct link from the FlowMint website.
- Click Add to Chrome (or Get / Add to Firefox) and confirm.
- Pin the extension to the toolbar for quick access.
To use it: click the FlowMint Test Evidence icon. The side panel opens. From there you can start recording, view the report, save or load sessions, and export.
npm install && npm run build, then in chrome://extensions/ turn on Developer mode and use Load unpacked to select the dist folder.
3 Quick start
4 Side panel
The side panel is your main control center:
- Session name — Name the current recording (used when saving and in the report).
- Start / Stop recording — Begin or end a recording session.
- View report — Opens the report page with all steps and screenshots (available after you stop recording).
- Export — Save as PDF (direct file), or download HTML or JSON. You can also export from the report view.
- Sessions — Save the current report with a name and tags; load a previously saved session.
- Settings — Screenshot delay, max steps, dark/light theme, and optional Help link.
5 Recording
What gets recorded
Clicks, inputs (on blur — when you leave the field), select and checkbox/radio changes, form submits, and navigation. A screenshot is taken after each action; the target element is briefly highlighted in the capture for clarity.
Start / Stop
- Start recording — Begins capturing on the active tab. Make sure the tab is on a normal web page (http/https). Chrome/extension pages cannot be recorded.
- Stop recording — Ends the session. The report is built automatically. You can then view it or export.
Session name
Set a session name before or after recording. It appears in the report header and when you save the session.
6 Report & steps
After you stop recording, the extension builds a report with:
- Session name and timestamp.
- Step list — Each step shows the action type (click, type, navigate, etc.), a short description, and the screenshot taken after that action (with the target element highlighted).
Open the report via View report in the side panel. From the report page you can scroll through all steps and use Save PDF, HTML, or JSON to export.
7 Export
Export your test evidence in three formats:
| Format | Description |
|---|---|
| Direct file download. Opens in the report view; use Save PDF to get a single PDF with all steps and screenshots. No print dialog — saves straight to your chosen location. | |
| HTML | Self-contained HTML file with embedded images. Open in any browser to view or share. |
| JSON | Structured data (session name, steps, screenshot data). Use for tooling, archiving, or custom reports. |
You can export from the side panel (after stopping) or from the report view.
8 Sessions
Save and load recording sessions so you can keep multiple reports and revisit them later.
- Save — Save the current report with a name and optional tags. Stored locally in the browser.
- Load — Open a saved session from the list. The report is restored; you can view it or export again.
- Delete — Remove a saved session (with confirmation).
9 Settings
Configure behavior and appearance:
- Screenshot delay — Short delay (ms) after each action before the screenshot is taken, so the UI can settle (e.g. highlights, animations).
- Max steps — Maximum number of steps per recording (helps avoid huge reports).
- Theme — Light, dark, or system. Affects the side panel and report view.
- Help URL — If your deployment sets a help URL in config, a Help link appears in the UI (e.g. to your internal docs).
Settings are stored locally. Deployers can override defaults via config.json (see the project README).
10 Tips & troubleshooting
- “No valid webpage” / recording doesn’t start — Ensure the active tab is a normal web page (http or https). Chrome/extension pages (e.g.
chrome://,edge://) cannot be recorded. - Content script or messaging errors — Refresh the page you’re recording and try again so the content script loads.
- Screenshots missing or blank — Some pages (e.g. with strict CSP or cross-origin frames) may block screenshots. Try on a simpler page to confirm the extension works.
- PDF export — Use View report then Save PDF from the report page for the best result. Large reports may take a few seconds to generate.
- Too many steps — Use the Max steps setting to cap the number of steps per recording.