5 items
Record browser tests, review screenshot evidence, and replay existing cases with clear results in TestDossier. Turn a manual browser test into a case you can review and run again in TestDossier. RECORD AND REVIEW Choose Record, select your project, and record a new test or update an existing case. As you interact with the page, TestDossier assembles clicks, committed field changes, form submissions, navigations, and visible outcomes into readable steps. Capture screenshots automatically or manually. Press Stop to review the generated title, steps, expected and actual results, and evidence. Edit instructions, remove unwanted steps, add notes, choose which screenshots to include, and permanently black out private details before choosing Submit. Recording evidence stays on your device until Submit; Discard removes the local capture. GUIDED REPLAY Choose Run test and select an existing case. You perform the actions; TestDossier guides you step by step and highlights the relevant page element when it can identify the target. With automatic screenshots enabled, Replay attempts to capture an Action image from your interaction and a Result image after the outcome settles. Screenshots are best-effort: missing or uncertain images remain visible for review rather than being silently replaced. Replay can check supported expected results, collect browser diagnostics, and advance automatically when verification and evidence checks succeed. When a result cannot be confirmed or evidence is incomplete, review it and choose the verdict yourself. Automatic advancement can also be turned off. Record Pass, Fail, Blocked, or Skip, and add notes. Repair outdated instructions, pick a current page target, insert missing steps, or go back to redo a checkpoint. Conditional steps, such as a cookie banner that no longer appears, can be skipped with an explanation. Step diagnostics let you inspect available Network and Console evidence for current and completed steps. Requests remain associated with the step where they started, including responses that arrive later. Console warnings and errors use their emission time. Eligible requests offer Attach details for redacted request and response previews. Review every step’s verdict, notes, verification status, and screenshots before saving. Inspect, permanently black out, or remove individual screenshots in completed Replay review. Screenshot editing locks when submission begins so retries preserve the evidence already sent. Finish here marks remaining steps as not executed. Replay evidence and progress stay local until Save results or Share finding. Share finding also creates a share link. Closing the panel does not discard an unfinished replay. Discard removes pending local progress; it does not delete an already saved result. FREE AND CLOUD PROJECTS A TestDossier project and project capture token are required. Recording and Replay support device-stored cases and cloud projects available to your account. Keep the TestDossier app tab open when replaying local tests. Cloud availability and limits depend on your account plan. The extension is free to install, and no purchase is required to use the Free workflow. CAPTURE AND PRIVACY Recording and Replay are user-initiated. The extension installs with access to TestDossier and requests optional access to all websites when you authorize capture. This broad browser grant supports screenshots and tests that navigate between sites; it is not limited to one selected website. Tested-page collection is scoped to your active recording or Replay session. A separate TestDossier-only bridge connects the app and extension for setup, preferences, and local Replay. Token validation and case lookup can contact TestDossier before you submit evidence. Evidence can include page labels and URLs, committed field values, screenshots, visible outcomes, network request metadata, console warnings and errors, uncaught errors, and Replay verdicts and notes. Detected password fields, known-sensitive patterns, and your configured private-field names are masked or redacted. These safeguards cannot identify every private detail on a page: review the evidence before saving it. Screenshot masking is applied to captured pixels before they are retained. If the extension cannot verify masking coverage or apply the masks, it leaves that screenshot out. Manual blackout permanently replaces pixels in stopped Record review and completed Replay review before submission. With Network & errors enabled, supported text-like fetch/XHR request and response previews can be captured during recording and Replay. Standard previews cover POST, PUT, PATCH, and DELETE, with limits of 4 KB per request and 64 KB per response. You choose which eligible previews to attach. Optional Developer handoff for recording is off by default. Enabling it expands previews to every method, including GET, raises the response limit to 128 KB, and attaches eligible previews automatically within a 6 MB session budget. The request limit stays 4 KB. In recording review, you can inspect and exclude previews, including those selected automatically. All previews are redacted again on submission. This is broader than network metadata alone. File selections record bounded, redacted filenames, not file contents or local paths. Browser/version, operating-system/platform, and viewport details may accompany submitted evidence as troubleshooting context. Replay includes the browser’s user-agent string and platform. Evidence is used for your TestDossier tests, not advertising, and is not sold. TestDossier uses deterministic rules for capture and guided checks. It does not use AI to generate test cases or send your evidence to an AI model. Privacy: https://testdossier.com/privacy Support: support@testdossier.com
Oct 19, 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.