5 items
File bug reports from the web app you test, with screenshots, steps, console and network context, into Session Based Testing. Session Based Testing helps teams run structured, time-boxed test sessions on their web applications. This extension is the tester's side of it: a side panel that sits next to the application under test, so you can report a problem the moment you see it, without switching tools. • Log in with your Session Based Testing account and pick the session and feature you are testing. • File a finding (bug, improvement or question) with steps to reproduce, the actual and the expected result. • Attach a screenshot of the page and crop it in place. • Findings carry the pages you visited and the network calls the page made. Turn on deep capture, and it also carries what you clicked and typed, console errors, a series of screenshots and performance and environment details — the context developers need to reproduce it. • A duplicate check shows similar findings before you submit. Privacy: nothing captured from the application you test leaves your browser until you file a finding. Passwords, card numbers and one-time codes are never read, and request and response bodies are never read. Deep capture is off until you allow it. Findings go only to your own organisation's workspace. Requires a Session Based Testing account — see https://www.sessionbasedtesting.eu.
Nov 3, 2026
rating_count is the Chrome Web Store ratings count, not a written-review count.
Media assets
Screenshots and videos on the listing.
Has promo video
Whether the listing includes at least one video.
Languages
Declared language locales.
Developer website
Listing exposes a developer website URL.
Contact email
Listing exposes a contact email.
Keyword in name
Case-insensitive substring match in the name.
Keyword in description
Case-insensitive substring match in the description.
Keyword occurrences in description
Count of case-insensitive occurrences in the description.
Category user-count percentile
Share of same-category extensions with fewer users (null if unknown).
These are transparent listing completeness / keyword signals, not a prediction of Chrome Web Store search ranking.