One button on the page, right where the bug is.
Toolbar icons are invisible to people who do not live in the browser's toolbar. The Bug Report Button puts webQsee where a tester is already looking: floating on the page itself, one click from a full capture. Off by default, and only on the sites you explicitly allow.
All features/assets/img/bug-report-button.pngThe person who found the bug is rarely the person who knows the tool.
Developers learn the keyboard shortcut on day one. Manual testers, product owners, support staff and the colleague who says "it looked weird on my machine" do not. They hit the problem, and then they either write a vague sentence in a chat or forget about it entirely.
A visible button on the page removes the whole learning step. There is nothing to remember and nothing to find: the moment something goes wrong, the thing to click is already on screen.
Who it is for
- Manual QA running through a test plan
- A product owner clicking around a staging build
- Support reproducing what a customer described
- Anyone doing a release smoke test at 6pm on a Friday
Four settings, and the default is "nowhere".
The button is opt-in. A fresh install shows it on no site at all, and you decide from there.
| Setting | Behaviour |
|---|---|
| No websites default | The button never appears. webQsee stays entirely in the toolbar. |
| Whitelisted sites | Only on the sites you list. The usual choice: your own staging and production hosts, nothing else. |
| Not-blacklisted sites | Everywhere except the sites you exclude. For a machine dedicated to testing. |
| All websites | Everywhere. Honest about what it means: every page you open, including your bank's. |
Change it any time from the extension popup under Other Features → Bug Report Button Config. The setting is local to the browser it was made in.
The same capture, fewer steps to reach it.
The button is a shortcut into webQsee's normal capture flow, not a reduced version of it. Whoever clicks it gets the full choice of capture, and whatever comes out is a first-class gallery item: shareable by link, exportable as a file, openable at view.webqsee.com by someone with no extension at all.
Which matters, because the point is not that a tester can press a button. The point is that what the tester produces is something a developer can actually debug from.
What it does not do
- It does not capture anything until it is clicked.
- It does not send anything anywhere on its own.
- It does not appear on a site you have not allowed.
- It does not read or modify the page it sits on.
Captures still land in the Local Gallery first, and still leave the machine only when somebody chooses to share or upload them.
Pairs nicely with.
Stop guessing. Start webQseeing.
Add webQsee to Chrome or Edge in one click. Most features are free, forever, no signup needed. Upgrade only if your team needs cloud sharing, S3 storage and Pro-grade tooling.
Works in Chrome 103+, Edge 103+ and most Chromium-based browsers. Install instructions.