Manual tests,
handled like code.
RunCase keeps manual test cases as markdown in your repository — diffable, reviewable in a pull request, and runnable from a browser, a terminal or your coding agent.
- Markdown, not a database
- Cases are files you own.
runcase pullwrites them into the repo; the export is the same format the import reads, so leaving costs one command. - Your agent can run them
- An MCP server gives a coding agent seven tools — read the cases, start a run, record a verdict with a note. Free on every plan.
- A run seals into a report
- Finish a run and it freezes: verdicts, notes, evidence. Share it as a link that needs no account.
## Password reset link expiresGroup: AuthPriority: high Given a reset link issued 16 min agoWhen the user opens itThen the link is rejected as expiredAnd a fresh link can be requested ## Second charge on double-submitGroup: CheckoutPriority: critical## Title starts a case · Key: value becomes metadata · Given / When / Then is highlighted, never rewritten
The whole loop, in one place.
No dashboards to configure, no suites to maintain. This is the actual UI — projects, a live run, and the coverage it rolls up to.
Projects, not suites.
Flat cases with an optional group and a distribution bar per project. Open runs sit at the top; everything else is one hairline away.

The latest verdict per case.
Not "the last run's outcome" — a case nobody ran shows as untested, never silently dropped. Stale groups get flagged, and "what keeps breaking" lists the tests that fail again and again.

A run is frozen.
Starting a run snapshots its cases. Edit them afterwards and the run doesn't change — it stays a record of what was true that afternoon.

Works where you already are.
The same cases, runs and verdicts — reached from a browser, from a terminal, or by the agent you already code with.
runcase pull and runcase push keep your markdown and the workspace in step. runcase report turns a JUnit file from CI into a sealed run, and exits non-zero when something failed — so a pipeline can gate on it.Plain files, narrow credentials, and a way out.
Test cases describe how your product works, so where they live is a fair question to ask first.
runcase pull writes them into your own repository, and the export is the same format the import reads — leaving costs one command, not a support ticket.Unlimited runs on every tier.
That's deliberate — you're never charged for testing more. The plan line is projects and team size, not how often you run.
Get the first build.
RunCase isn't public yet. Leave an email and we'll send it when the first build is ready — no drip campaign.