Get your testing approved —
not just documented.
Stop rebuilding QA proof from screenshots, CI logs, tickets, and Slack threads. TestDossier turns browser sessions, manual checks, and CI runs into one approval-ready report reviewers can sign off on without an account.
PMs and clients ask whether it was tested, then need screenshots, notes, or CI context before they can sign off.
Teams recreate QA evidence after the fact from screenshots, CI output, tickets, Slack threads, and manual notes.
Stakeholders should review the evidence, comment, and cast a verdict without joining your QA tool.
Evidence you can stand behind.
Every step is recorded or typed — never generated. Your report shows what was tested, what failed, and what reviewers approved.
Deterministic, not generated
Steps come from what the extension records, what you type, or what your CI run already describes. No model writes your evidence — so what a reviewer approves is exactly what happened.
Private until you share
Free authoring stays in your browser until you choose to create a share. Screenshots, steps, and test data are not sent to a model or used for training.
Shared links stay stable
A share link captures a snapshot. Edit, delete, or re-run the case later — the report someone approved still shows the same evidence.
Capture the test. Package the proof. Get the sign-off.
Start locally without an account. Sign in only when you need share links, capture tokens, or cloud sync.
Record the flow
The browser extension records an explicit session — clicks, inputs, page changes, network metadata, uncaught browser errors, and screenshots. Hit Stop and the events become a draft case. No extension? Paste screenshots into the steps instead.
Pipe in CI
One curl
from your pipeline. Cypress, Playwright, JUnit XML, or generic JSON all work. Known tests log a fresh
run; new or unmatched tests land as drafts or untracked history to review.
curl -X POST https://testdossier.com/api/ci/ingest \ -H "Authorization: Bearer $TD_TOKEN" \ -H "Content-Type: application/json" \ -H "X-CI-Format: cypress" \ -H "X-CI-Run-Id: $GITHUB_RUN_ID" \ --data-binary @cypress-results.json
Ship one link
Hit Share. Drop the URL in Slack, Jira, or the bug report. Read-only, optional password, optional expiry — no paid seat for reviewers.
PMs, clients, contractors — everyone who only needs to review opens the link without taking a QA seat.
They read, comment, or cast a verdict straight from the report — no more "can you screenshot that?" back-and-forth. You only pay for the people who build and sync the evidence.
Run the flow once. Review the draft before it becomes a case.
The extension turns real browser activity into editable test steps with screenshots, network context, and error evidence attached. You review the draft before it joins your catalog.
Not a video. Not selectors. Not a screenshot dump. Structured steps with evidence attached.
Free includes unlimited local capture.
Capture it in the browser, type it manually, or curl it from CI. Either way, the source writes the draft; a human reviews the definition before it becomes trusted.
Manual sessions and CI runs, in one approval report.
Every run finds its case automatically — matched by file, suite, and name, with no test IDs to wire up. Rename or move a test and it stays the same case, never a duplicate — and unmatched CI runs still land here, never dropped.
Where TestDossier fits beside your tool of record.
Keep the catalog and enterprise controls in TestRail, Xray, or Qase. Use TestDossier when the missing piece is approval-ready evidence: screenshots, run history, comments, verdicts, and a link stakeholders can open.
Prices and features verified against public pricing pages, May 2026. Jira app pricing varies by Atlassian user tier. Spotted something off? support@testdossier.com — we'll correct it.
One QA workflow, shared by the people doing the work.
Bring teammates into the same evidence history, review flow, and client-ready reports without changing how anyone captures tests.
First seat included. Add teammates for $15/seat.
See team pricing →Projects, runs, screenshots, and share links stay in one workspace instead of each tester's browser.
Comments, verdicts, and sign-off stay attached to the report everyone is reviewing.
See who changed cases, created shares, and submitted runs without chasing updates in Slack.
Questions you're probably asking.
How is this different from TestRail / Xray / Qase?
Your tool of record keeps the catalog, permissions, and long-term governance. TestDossier creates the evidence package around the work: captured steps, screenshots, CI runs, reviewer comments, sign-off, and exports back to the tools your team already uses.
Use it beside TestRail, Xray, Qase, or Zephyr when the thing slowing you down is evidence prep, stakeholder review, or connecting manual sessions with CI results.
Is this for solo testers, or teams?
Both. Solo devs and indie QAs work in Free or upgrade to Pro for cloud sync and sharing. Small teams (typically 2–15) add a workspace for $15/seat after the first. If you're an individual QA inside a larger company, Free covers local authoring and exports, and Pro adds the synced team workflow around whatever tool of record your company uses.
Where is my data stored?
On Free, authoring data stays in your browser until you choose a server feature. Free share links and capture submissions briefly use TestDossier servers to deliver the link or bundle; shared reports keep their own copy until expiry. On Pro, your tabs, history, and screenshots sync to your account, so you can pick up on another device.
Does TestDossier use AI?
No. Every step and report is built deterministically from what the capture extension records, what you type, or what your CI run already describes. Your screenshots and test data are not sent to an AI, and we don't train on them.
How does the CI integration work?
One curl step posts results to TestDossier. Cypress JSON, Playwright JSON, JUnit XML, or
generic JSON all work. Known tests attach a fresh run to the matching case; new or unmatched tests stay
visible as drafts or untracked History. Per-project bearer tokens and X-CI-Run-Id support
repeatable pipeline retries.
Do I need to install anything? Sign up?
No account is needed to start authoring in /app. You sign in to create share links, mint a capture token, or use Pro cloud sync. Browser capture requires the TestDossier extension; without it, manual authoring and screenshot paste work in the browser.