How it works
Microfilm fits into the QA loop you already run. Here's the full path — from picking up a test case to exporting a signed evidence package — step by step.
Microfilm reads requirements and test cases straight from Jira, Linear, or Azure DevOps. Your testers see assigned work without leaving the app — no migration, no duplicate test management.
A tester opens Microfilm and sees what is on their plate: the test case, its acceptance criteria, the linked ticket, prior tester notes, and relevant code references — all in one surface.
The desktop app sits next to the browser and records the session — screen, voice narration, screenshots, and structured comments — captured against the specific test case being executed.
Each test gets a pass/fail verdict signed by the tester. The evidence log is append-only and tamper-evident, producing a signed microfilm record for every execution.
When a test fails, the linked Jira or Linear ticket gets a structured comment — requirement, acceptance criteria, what the tester saw, and a deep link to the capture. AI coding agents read the same context through the MCP server.
Requirements → acceptance criteria → test cases → execution evidence → signatures. The traceability matrix builds itself and exports as an audit-ready package on demand.
Download the free capture app, or create an account to set up a team workspace.