Item logo image for TestDossier — capture browser tests

TestDossier — capture browser tests

ExtensionDeveloper Tools5 users
Item media 5 (screenshot) for TestDossier — capture browser tests
Item media 1 (screenshot) for TestDossier — capture browser tests
Item media 2 (screenshot) for TestDossier — capture browser tests
Item media 3 (screenshot) for TestDossier — capture browser tests
Item media 4 (screenshot) for TestDossier — capture browser tests
Item media 5 (screenshot) for TestDossier — capture browser tests
Item media 1 (screenshot) for TestDossier — capture browser tests
Item media 1 (screenshot) for TestDossier — capture browser tests
Item media 2 (screenshot) for TestDossier — capture browser tests
Item media 3 (screenshot) for TestDossier — capture browser tests
Item media 4 (screenshot) for TestDossier — capture browser tests
Item media 5 (screenshot) for TestDossier — capture browser tests

Overview

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 Open the Record tab, choose 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 the case, remove unwanted steps, open screenshots, and permanently black out private details in the stopped recording before choosing Submit. Recording evidence stays on your device until Submit; Discard removes the local capture. GUIDED REPLAY Open the Replay tab and select an existing case. You perform the actions; TestDossier guides you step by step and highlights the relevant page element when it can. It can capture screenshots and browser diagnostics, check the expected result, and advance when its checks succeed. When a check cannot confirm the result, choose the verdict yourself. You can also turn automatic advancement off. Record Pass, Fail, Blocked, or Skip, add notes, and review the result summary. Finish here marks the remaining steps as not executed. Replay evidence and progress stay local until Log results; Discard removes them. Closing the panel does not discard an unfinished replay. Manual screenshot blackout is available for stopped recordings, not Replay. FREE AND CLOUD PROJECTS A TestDossier project and project capture token are required. Free supports recording and replay with device-stored tests and results. Keep the TestDossier app tab open when replaying those local tests. Pro and Team projects support cloud-synced tests and replay history. 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 a grant 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. Evidence can include page labels and URLs, committed field values, screenshots, visible outcomes, network request metadata, console warnings/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 a stopped recording. With Network & errors enabled during recording, small, redacted text-like fetch/XHR request and response previews can be reviewed and attached as API evidence. Standard previews cover POST, PUT, PATCH, and DELETE, with limits of 4 KB per request and 64 KB per response. Optional Developer handoff 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. 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. Chrome includes browser/version and operating-system names with submitted captures as troubleshooting context. 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

Details

  • Version
    1.0.21
  • Updated
    September 16, 2026
  • Size
    543KiB
  • Languages
    9 languages
  • Developer
    Website
    Email
    support@testdossier.com
  • Non-trader
    This developer has not identified itself as a trader. For consumers in the European Union, please note that consumer rights do not apply to contracts between you and this developer.

Privacy

Manage extensions and learn how they're being used in your organization

TestDossier — capture browser tests has disclosed the following information regarding the collection and usage of your data. More detailed information can be found in the developer's privacy policy.

TestDossier — capture browser tests handles the following:

Personally identifiable information
Health information
Financial and payment information
Authentication information
Personal communications
Location
Web history
User activity
Website content

This developer declares that your data is

  • Not being sold to third parties, outside of the approved use cases
  • Not being used or transferred for purposes that are unrelated to the item's core functionality
  • Not being used or transferred to determine creditworthiness or for lending purposes

Support

For help with questions, suggestions, or problems, visit the developer's support site

Google apps