Your QA process, as software.
Passmuster turns a messy ticket into a test plan a human approves and your QA signs off — criterion by criterion — before the code merges.
It is not an automatic AI code-review bot. Nothing is rubber-stamped: a person approves the plan, and a tester marks each item passed before work earns its merge.
How it works
The proven loop — five steps, a human in the middle of every one.
1. Read the ticket
When a pull request links a Jira ticket — even a half-written, prose-only one — Passmuster reads the ticket and the diff.
2. Draft a test plan
It drafts a concrete plan: what to verify, and which parts the diff's own tests already cover versus what a human still needs to check.
3. A human approves it
An engineer reviews and approves the plan (or edits it first). Nothing is acted on until they do.
4. QA signs off, item by item
A tester walks the plan and marks each item passed, failed, or unclear. A failed item files a bug back in the tracker.
5. Write the record back
The result is posted back onto the ticket as a plain-text sign-off record — and, if you opt in per repo, a required check that holds the merge until it passes.
On a real, messy ticket
Most tickets aren't tidy spec docs. Here's a prose-only one with no acceptance criteria at all — and the plan Passmuster drafts from it.
WEB-238 — Checkout sometimes double-charges
A few customers said they got charged twice when the payment page was slow. Probably a double-submit thing? Make it not do that. Also the spinner is confusing.
- On a slow network, submit the checkout form twice quickly — confirm only one charge is created.
- Confirm the pay button is disabled after the first click until the request resolves.
- Covered by the new test in checkout.test.ts: a second submit while one is in flight is rejected.
- Verify the spinner shows while the charge is pending and clears on success or error.
Pricing
$100 / active developer / month
You're billed only for the developers whose pull requests actually go through Passmuster in a given month — not for your whole headcount.
Try it free, no card. We'll enable a few real generations on your own board so someone on your team can see a plan for one of your actual tickets — before you grant source access or pay anything.
Start a pilot
We onboard your team by hand and set a price together. There's no self-serve checkout yet — just email us and we'll set you up.
What leaves your infrastructure? When a pull request is processed, your PR diff and the linked ticket's text are sent to Anthropic to generate the plan. That is the data that leaves your infrastructure, and Anthropic is who receives it. Read the full data-handling page →
Who's behind it
Passmuster is built by Dan Witt at Echowire. It's an early product and I'm hands-on with every team that pilots it — email me anytime at hello@passmuster.io.