Client-ready QA reports
from manual tests and CI runs.
Manual screenshots and CI runs bundled in one read-only URL. No login for viewers, comments built-in.
From blank tab to shareable evidence — in three moves.
No project setup, no template wizard. Open the app and start.
Paste & log
Screenshot to clipboard, paste into the step. Test data picker — IBAN, BSN, SSN, Luhn cards — one click away. Autosaved every keystroke.
Pipe in CI
One curl
from your pipeline. New tests land as drafts to review; existing ones log a fresh snapshot. Cypress,
Playwright, JUnit XML — no plugin.
curl -X POST https://testdossier.com/api/ci/ingest \ -H "Authorization: Bearer $TD_TOKEN" \ -H "Content-Type: application/json" \ -H "X-CI-Format: cypress" \ --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 login for viewers.
Record the session. Get the test written for you.
The testing was never the hard part — the write-up is. So you don't do it: record the run, AI drafts the Action / Expected steps, you review instead of transcribe. Up to 10 minutes a recording.
Record it, or curl it from CI — either way, you never re-type what your tests already encode. It drafts itself; you review and freeze.
Know if it's a bug or a bad test — before you open it.
TestRail, Zephyr, and Xray show the same red ✗ whether your product broke or the test is just flaky.
TestDossier ranks every failing case by failure pressure and splits it — Regressed (a real product bug),
Flaky (a test you can't trust), Chronic (known-broken) — across your manual sessions and nightly Cypress
runs. No plugin in your Cypress config, no add_run API call, no orphaned test IDs.
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 |
One project. One report. One shareable link.
Tests match against your project's tabs by ticket ID first, then by test-name substring. Unmatched tests still appear in History — tagged "untracked," never lost.
The gaps tools of record leave open.
Five evidence problems you end up solving yourself in TestRail, Zephyr, or Xray.
curl (no plugin, no setup)Prices and features verified against each tool's public site, May 2026. Spotted something off? support@testdossier.com — we'll correct it.
PMs, clients, contractors — everyone who only needs to look opens the link with no login and no seat.
That's the part legacy tools charge the most for. Here it costs nothing — you only pay for the people who build the evidence.
Workspaces — same workflow, shared.
Invite teammates by email. Shared projects, tabs, history, and Test Inbox. The workspace activity feed shows who changed what, so nothing slips through unnoticed.
$15/seat after the first.
See team pricing →Workspace activity
Who changed what, newest first. Click any item to open the related test case.
Questions you're probably asking.
How is this different from TestRail / Zephyr / Xray?
TestRail tracks. TestDossier does. We replace the Google Doc next to your test management tool, not the tool itself.
Tools of record store the catalog and org-wide run history. TestDossier is for the actual doing: pasting screenshots, generating valid test data, capturing evidence — then sharing it as one read-only link your PM, client or lead opens and comments on without a login or a paid reviewer seat. When you're done, export to whichever tool your team uses — 9 formats. Built to live alongside TestRail / Zephyr / Xray, not replace them.
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, Pro is yours to use — Free is also full-featured, and you export to whatever tool of record your team uses.
Where is my data stored?
On Free, everything stays in your browser — IndexedDB, never sent to a server. Close the tab, your tests are still there next time. On Pro, tabs and history sync to your account so you can pick up on another device. Either way, screenshots aren't shared with anyone unless you generate a share link yourself.
Are my screenshots sent to an AI?
Only if you opt in. AI features are off by default and Pro-gated. When you trigger one (screen-recording extraction or fixture builder), the relevant text or recording is sent to Anthropic for that single request. We don't train on your data, we don't store your prompts beyond the request, and we don't read them. Skip AI entirely and nothing leaves your account.
How does the CI integration work?
One curl step in your pipeline — no plugin to install in your Cypress config, no
pre-created run object, no orphaned IDs. Cypress JSON, Playwright JSON, JUnit XML, or generic JSON all
work. Tests match against project tabs by ticket ID first (e.g. JIRA-123), then by
test-name substring; unmatched tests still appear in History tagged "untracked." Per-project bearer
tokens, atomic batch insert, idempotent retries via X-CI-Run-Id.
Do I need to install anything? Sign up?
No to both. Open /app in your browser and start a test report — no account, no install, no payment method. Free is full-featured for solo work. You only sign up if you want Pro (cloud sync, AI, sharing, team workspaces).