Test reporting & evidence for Azure Test Plans
Audit-ready test reports, with the evidence already inside them
Testmarshal turns Azure Test Plans data into sign-off packs your auditors, executives and clients can actually open — screenshots embedded, every number defined, and no Azure DevOps licence needed to read a single one.
Early access list. No spam, and you can leave whenever you like.
- Runs on your own PC
- No install, no server, no admin rights
- Your token never touches disk
Denominator: test points in the active suite as of 09:00, excluding 41 deferred to Release 24.4. Every figure above states the population it was measured against.
The people who need your test report can't open it
You finish a test cycle. The evidence is real, the numbers are right — and then you spend a day and a half pasting screenshots into a document, because the auditor, the release board and the client sponsor have no way to see any of it themselves.
That is not a gap in your process. It is a gap in the tooling. In Azure DevOps, a free Stakeholder cannot open the Test Plans portal at all, and reading results requires a paid licence. The commercial test management platforms are no better: we checked the major tools in August 2026, and not one of them lets an unlicensed reader open a report with the test evidence attached. The closest — PractiTest — offers free read-only users, then explicitly withholds reports from them.
So the evidence gets copied by hand, into a document nobody can trace back to the run that produced it. That is the job Testmarshal was built to delete.
What Testmarshal does
A reporting, evidence and governance layer for teams already committed to Azure Test Plans. It does not ask you to migrate your test cases anywhere.
Reports that explain themselves
Daily status with burndown, KPIs, a written summary paragraph and a work list ordered by what needs attention first — not a dump of rows for you to interpret at 7am.
Evidence inside the export
Test-run screenshots and attachments are embedded in the report file itself, not linked back to a system your reader cannot open. One file, evidence included, travels anywhere.
Sign-off with a verdict
Exit criteria evaluated against live data and reduced to a GO or NO-GO, with the reasoning attached. The release board gets an answer, not a spreadsheet.
Scope and integrity audit
Historical queries surface test cases quietly removed from scope mid-cycle — the thing that turns a clean pass rate into an audit finding six months later.
Traceability, generated
Requirements-to-tests-to-results matrices built from live data, so coverage claims can be checked rather than asserted.
Every number states its denominator
A pass rate is meaningless without the population it was measured against. Testmarshal prints the definition and the denominator beside the figure, every time.
Your readers don't need a licence
This is the part that saves the day and a half. A Testmarshal report is a self-contained file that opens in any browser — no account, no seat, no licence, no login.
| Tool | Can an unlicensed reader open the report? | With evidence attached? |
|---|---|---|
| Azure Test Plans | No — Stakeholders are locked out of the portal; reading needs a paid seat | No |
| TestRail, Zephyr, Xray, qTest, Testmo | No — every reader consumes a paid seat | No |
| PractiTest | Free read-only users exist | No — reports are explicitly withheld from them |
| Testmarshal | Yes — it's a file, not a login | Yes — embedded, not linked |
How it works
Unzip and run it
One file. No installer, no server, no database, no admin rights and nothing for IT to approve. It opens a page in your own browser, served from your own machine.
Connect with your own credentials
Testmarshal reads Azure DevOps using your personal access token, held in memory for the session and never written to disk. Your test data never leaves your organisation.
Generate, then send
Pick a report, generate it, and you have a self-contained file. Email it, attach it to the audit folder, hand it to the release board. Whoever opens it sees everything, evidence included.
Who it's for
Test managers and QA leads running Azure Test Plans in organisations where somebody, eventually, asks you to prove it.
That includes regulated financial services under SOX and supervisory examination, medical device and life sciences teams working to IEC 62304, automotive and aerospace suppliers held to ASPICE or DO-178C, and the QA consultancies who deliver test reports to clients that have no licence to the client's own tooling. If you have ever rebuilt a status pack by hand the night before a steering committee, this was built for you.
Guides
Practical answers to the questions test managers actually search for.
Frequently asked questions
Can I share Azure Test Plans results with someone who doesn't have a licence?
Not from Azure DevOps itself. A free Stakeholder cannot open the Test Plans portal at all, and reading test results requires at least a Basic licence. Testmarshal produces self-contained report files that open in any browser, so an auditor, executive or client can read the full report — evidence included — without a licence of any kind.
Does Testmarshal export test evidence such as screenshots with the report?
Yes. Test-run attachments and screenshots are embedded directly inside the exported report file rather than linked back to a system the reader cannot open. The report travels as one file, and the evidence travels with it.
Do I need to install anything or get IT approval?
No installation, no server, no database and no admin rights. Testmarshal runs on your own PC and serves a local page in your browser. It reads Azure DevOps with your own credentials, held in memory only and never written to disk.
Does Testmarshal work with Jira and Xray?
Azure Test Plans is supported first. Jira and Xray support is on the roadmap, and the reporting layer is built to be tool-neutral so the same report definitions work across both.
Where is my test data stored?
Nowhere but your own machine. Testmarshal has no cloud service holding your data. Your test data stays in your Azure DevOps organisation, the reports are written to your disk, and your access token is held in memory only for the length of the session.
Is Azure Test Plans being deprecated?
No. Azure Test Plans shipped generally available features as recently as July 2026 and has a published roadmap running into 2027. Microsoft's Azure Repos to GitHub migration tooling explicitly does not migrate test plans, and GitHub has no test management product — so teams on Azure Test Plans have nowhere else in the Microsoft estate to go.
How is this different from TestRail, Zephyr or qTest?
Those are test management platforms that want to own your test cases, and they charge for every person who reads a result. Testmarshal is a reporting, evidence and governance layer for teams already committed to Azure Test Plans. It does not ask you to migrate anything, it charges nothing for readers, and it puts the evidence inside what it produces.
Marshal the evidence.
Testmarshal is in development. Join the early access list and you'll be among the first test managers to try it — and the feedback you give will shape what ships.
No spam, and you can leave whenever you like.