Point DeckTest at your site or app and it tests the whole flow like a real person — signs up, reads the verification email, pulls the OTP, types it in, clicks through, and confirms the result three ways: on screen, in the DOM, and in the console. It's a real browser adapting live, not a brittle recorded script. Bring your own Claude. $0 to run.
A screenshot alone lies — a form can look fine while the request silently 500s. DeckTest confirms each step against what you see, what the page actually is, and what the browser is really doing underneath.
Looks at the rendered page the way a person would — is the success state there, did the modal close, is the button gone, does the dashboard actually load?
Reads the real elements, text and state — the right heading, the row that should exist, the field that should be cleared — not just pixels that happen to match.
Watches the browser console and every network call — a red error, a failed request, a 4xx/5xx the UI swallowed. The bugs a screenshot can't see.
Verification is where most test bots fall over. DeckTest doesn't. It fills the form, waits for the email to arrive, opens it, pulls the OTP or magic-link, and types the code in like a person would — then keeps going into whatever's behind the wall. No stubbed inbox, no skipped step.
When something fails, you don't get a red X and a shrug. DeckTest writes a QA report: the step that failed, a screenshot at the moment it broke, the console error or failed request behind it, and the exact steps to reproduce — so it's fixable, not just flagged.
DeckTest connects the Claude you already have — Claude Code or an API key — to a real browser over MCP. Same BYO-key, local-first philosophy as DeckSpace: no new account, no metering, no markup. The browser runs on your machine and the report stays on your machine.
Point it at your Claude Code install or drop in an API key. DeckTest never sees, stores, meters or marks up your usage.
It drives an actual browser and adapts when the page changes — no flaky selectors to re-record every time you ship.
The browser, the run and the report all run locally. Nothing about your app leaves your machine unless you send it.
Any website or web app you can reach in a browser — signup and login, checkout, onboarding, forms, dashboards. It goes through the flow end-to-end like a user: filling fields, reading verification emails, pulling OTPs or magic-links, clicking through, and confirming the result visually, in the DOM, and in the console + network.
Yes. DeckTest connects the Claude you already have — Claude Code or an API key — to a real browser over MCP. Bring your own key; DeckTest never sees, stores, meters or marks up your usage. $0 to run beyond what your own model costs.
No. It drives a real browser and adapts as it goes — reasoning about the page in front of it rather than replaying brittle selectors. When your UI changes, it adjusts instead of breaking, so you're not re-recording tests every release.
macOS and Windows. It's a native cross-platform desktop app — small and fast — that runs the browser and writes the QA report locally on your machine.
DeckTest is in beta for macOS and Windows. Bring your own Claude, $0 to run, and let it test the flow like a real person would.
DeckSpace