Media
1 item
Description
Capture session replay, console logs, network requests and repro steps on any page. Share a link or export a single HTML report. --- ## Store listing **Name:** LaporBug — 1-click bug reports **Summary (≤132 chars):** > QA bug reports with session replay, console, network and repro steps — uploaded as a shareable link in one click. **Category:** Developer Tools · **Language:** English **Description:** > LaporBug is an internal bug-reporting tool for QA teams. > > While you test, LaporBug keeps a short rolling buffer (1–5 minutes) of the > current tab — a visual session replay, console output, network requests and > your interaction steps. Nothing is stored or sent anywhere automatically. > > When you hit a bug, click the LaporBug icon: > • Upload & copy link — the full report uploads to your team's own server and > a shareable link lands on your clipboard > • Download — the same report as a single self-contained HTML file > • Copy summary — a Markdown digest for Jira / Slack tickets > > Each report contains: pixel-accurate session replay, console logs with stack > traces, network requests with timing and bodies, auto-written reproduction > steps, and full environment details. Password fields are always masked; an > option masks all typed input. > > Note: this extension is built for internal team use. Uploading requires your > team's server URL and API key (set once in the popup's Settings). **Screenshots (needs at least 1, 1280×800):** take two — 1. A report page open at https://lapor.zhio.site/r/QnPScPrw-2LypSE3cskmYA (replay + tabs visible) 2. The popup open on any page (click 🪲, screenshot the popup with the stats chips) --- ## Privacy tab **Single purpose description:** > Captures debugging context (session replay, console, network, repro steps) in > the current tab so QA can file complete bug reports with one click. **Permission justifications:** - **Host permissions (http/https on all sites):** The extension must record the page the tester is currently testing — console output, network requests and DOM changes can only be captured by a content script running on that page. Which sites are tested varies (staging, production, local), so a fixed site list is not possible. No data leaves the page unless the user clicks upload. - **storage:** Saves user preferences (replay length, input masking, team server URL and API key). - **downloads:** Saves the bug report as an HTML file when the user clicks "Download". - **clipboardWrite:** Copies the share link / Markdown summary when the user clicks the corresponding button. - **Remote code:** No — all code is packaged in the extension. **Data usage disclosures (check these):** - ✅ Website content (page visuals, console, network — captured locally, uploaded only on user action) - ✅ User activity (clicks, typing steps — same) - ✅ Personally identifiable information (only if visible on tested pages / typed by tester) - ❌ Everything else (health, financial, location, etc.): not collected - Certify: data is NOT sold, NOT used for unrelated purposes, NOT used for creditworthiness. **Privacy policy URL:** https://lapor.zhio.site/privacy ---