Evidence-ready QA reports
from manual tests and CI runs.
Record browser flows into draft test cases, pipe in automated results, and send one read-only report stakeholders can review without a paid seat.
Capture manual tests. Ingest CI runs. Stakeholders 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 watches a real session — clicks, inputs, page changes, network metadata, 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.
Run the flow once. Review the draft before it becomes a case.
The extension records what actually happened — clicks, inputs, page changes, network metadata, uncaught browser errors, and screenshots — then assembles an editable draft. You approve the definition before it joins your catalog.
Not a video. Not Cypress selectors. Not a screenshot dump. Structured, editable steps with evidence attached.
Free includes 10 capture-extension submissions a month; Pro makes capture unlimited.
Capture it in the browser, or curl it from CI. Either way, the source writes the draft; a human reviews the definition before it becomes trusted.
See which failures deserve attention first.
Most test managers can tell you a run failed. TestDossier puts manual sessions and CI runs in the same project view, then groups failures by pressure: regressed, flaky, chronic. Unmatched CI still lands in History as untracked instead of disappearing.
Insights
Project-wide health, hotspots, and run comparisons.
| Ticket | Summary | Fail rate | Fails / runs | Last fail | |
|---|---|---|---|---|---|
| QA-412 | Checkout — promo code recalculates order total | 67% | 4 / 6 | 2 hours ago | |
| QA-388 | Login — SSO redirect returns to the original deep link | 50% | 3 / 6 | 5 hours ago |
| Ticket | Summary | Fail rate | Fails / runs | Last fail | |
|---|---|---|---|---|---|
| QA-205 | Dashboard — revenue widget renders within 2s | 22% | 5 / 23 | 1 day ago | |
| QA-117 | Search — typeahead debounces rapid keystrokes | 18% | 4 / 22 | 3 days ago |
| Ticket | Summary | Fail rate | Fails / runs | Last fail | |
|---|---|---|---|---|---|
| QA-061 | Export — 50k-row CSV download completes without timeout | 91% | 41 / 45 | 6 hours ago |
Manual and CI. One project. One triage 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. Unmatched runs still appear in History — tagged "untracked," never lost.
Where TestDossier fits beside your tool of record.
Keep the catalog and enterprise controls in TestRail, Xray, or Qase. Use TestDossier for the evidence package, reviewer link, and manual-plus-CI workflow around it.
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.
PMs, clients, contractors — everyone who only needs to review opens the link without taking a QA seat.
They can read, comment, or cast a verdict from the report. You pay for the people who build and sync the evidence.
Workspaces — same workflow, shared.
Invite teammates by email when local work turns into a shared QA process. Pro workspaces add shared projects, synced history, Test Inbox, and an activity trail without changing the capture-to-report workflow.
$15/seat after the first.
See team pricing →Projects, tabs, runs, screenshots, and share links sync for everyone in the workspace.
Comments, verdicts, @mentions, and sign-off stay attached to the evidence report.
Activity history shows who changed cases and shares; Test Inbox gives the workspace a disposable address for signup, reset, and notification emails.
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 store a frozen 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.