From requirements
to tested software.
Upload your spec. Get a Playwright suite you own and a requirement-to-result traceability matrix your auditors will accept. Built for regulated QA teams — medical devices, fintech — without a Playwright engineer in-house.
Audit exports for
Free plan available · No credit card required
Works alongside the tools you already run
The Problem
Your auditor wants a traceability matrix. You don't have one.
In regulated software, you have to prove every requirement is tested and every result traces back to a spec. Building that matrix by hand is slow, and keeping it current as the spec changes is worse — especially without a Playwright engineer on the team.
The matrix is a spreadsheet you maintain by hand
Someone hand-maps each requirement to a test case in a spreadsheet, then re-checks it every time the spec or the suite changes. It is the most tedious, error-prone artifact your team owns — and the one the audit hinges on.
No Playwright engineer in-house
Automated, auditable tests need someone who writes Playwright. Hiring one is hard; the manual test cases stay un-automated until you do.
The audit finds the gaps before you do
When a test result has no link back to a requirement, an auditor sees an untested requirement — and a finding. IEC 62304, FDA 21 CFR 820, and 21 CFR Part 11 all expect that evidence on demand. Assembling it under deadline is where audits slip.
How It Works
Five steps. Fully connected.
Upload BRD
PDF or DOCX. We handle messy tables, headers, and nested sections.
Extract Requirements
AI identifies every requirement, acceptance criterion, and edge case.
Generate Test Cases
One click. Steps, expected results, priority, and confidence scores.
Run anywhere
Run your suite with npx playwright test — your CI, your repo, your cloud.
Track & Report
Pass rates, coverage metrics, audit logs, and CSV exports.
Traceability & audit exports
The matrix your auditor asks for.
Every test case links to a requirement; every result links to evidence. The matrix stays current as the suite runs, and exports to the formats your audit expects — no spreadsheet to maintain by hand.
- Bidirectional requirement-to-test-case-to-result matrix
- Evidence auto-attached to every result
- Audit exports for IEC 62304 / FDA 21 CFR 820 (QMSR) / 21 CFR Part 11
- CSV export usable as evidence for your SOC 2 audit
Generation
From spec to linked test cases.
Extracts testable requirements from your BRD, with confidence scores you review. Each generated test case stays linked to the requirement it covers, so the matrix is built as you go — not bolted on after.
- PDF and DOCX parsing with table extraction
- Confidence score on every extracted requirement
- Each test case linked to the requirement it covers
No lock-in
And if you leave,
your tests leave with you.
The output is a standard Playwright project — .spec.ts files in your repo, run with npx playwright testin your CI. No proprietary format holding your evidence hostage. It is reassurance, not a moat — and we think you should have it anyway.
- Standard Playwright .spec.ts in your own repo
- Run in any CI — GitHub Actions, GitLab, Jenkins
- No proprietary runner, no vendor lock-in
Everything else you'd expect. And then some.
Team & Roles
Owner, Admin, Member, Viewer roles. Invite your team, assign test runs, manage access.
Multi-Organization
Switch between organizations instantly. Each with its own projects, team, and billing.
Playwright, not a black box
Tests are generated as standard Playwright .spec.ts files in your repo. Run them in any CI, on any infra. No proprietary format.
Google SSO
One-click sign-in with Google. No password management for your team.
Test Run Management
Organize execution into runs. Track pass/fail/blocked in real-time, assign to teammates.
Traceability + audit exports
Bidirectional requirement-to-test matrix. CSV exports built for IEC 62304, FDA 21 CFR 820 (QMSR), and 21 CFR Part 11 — and usable as evidence for your SOC 2 audit.
Assistant
It already knows your requirements.
The assistant has your project's requirements, existing tests, and coverage gaps in context — so the test cases it proposes come back linked to the requirements they cover, ready for the matrix.
I found 3 requirements related to coupon codes. Here are 4 test cases:
Accept all · Dismiss
From the blog
Latest thinking
Stop writing test cases from memory.
Upload your first BRD and get a requirement-linked test suite and traceability matrix you can hand to an auditor. Free plan, no credit card.