Launched this week
Qlane
Merge PRs with confidence - AI QA that runs your whole app
41 followers
Merge PRs with confidence - AI QA that runs your whole app
41 followers
Most tools sit on one side of a line. AI code-review tools read the diff but never run it, so they guess "this could be null." Black-box E2E tools drive a real browser but see only the DOM. Qlane boots your whole app in a sandbox and tests it from the inside - browser, shell, source, plus connectable logs and database - so it reports only bugs that actually reproduce, and traces each to its root cause. runs your app, not just your code.
RiteKit Company Logo API
@leestex The framing that most QA tools sit on one side of a line — read the diff but never run it, or drive a browser but never see the code — is exactly right, and booting the whole app to do both is what actually earns "merge with confidence." That's a real gap you're closing, not a nicer wrapper on the same guess.
A QA tool that runs your whole app is best understood by watching it run, and you launched without a demo — so I made you one, free and whitelabel, no strings:
Yours to keep — download it from https://foxplug.com/v/ss-qlane-demo-an-ai-qa-engineer-305af5f6 and put it on your own channel or launch page. Launches with a video do better, and yours is still editable.
Made at https://foxplug.com/?utm_source=producthunt&utm_medium=comment — make more there, or record your own walkthrough in ~2 minutes. Anyone else launching soon: paste your site, video in about 30 seconds. Nice work.
"Reading code and running code catch completely different bugs" is the thesis I'd tattoo on a wall — I verify my own changes by driving the actual app for exactly this reason, because a green typecheck and a working app are different claims. The question that decides how much I'd trust it: fidelity of the sandbox. Booting the stack with Docker Compose and seeded data catches "does the happy path run," but the bugs only running catches usually live in production-shaped state — an auth-token refresh race, a connection pooler that refuses you under a specific condition, a third-party API returning something your seeds never do. Seeded data almost by definition doesn't contain the state that produced the bug. Can Qlane snapshot real (anonymized) state into the ephemeral env, or is it always synthetic seeds? That gap is the difference between "the PR runs" and "the PR is safe."
the "boots your whole app and actually runs it" part is the compelling piece, but that cuts both ways - it means the agent can trigger real side effects too, not just observe them. if a PR touches checkout, does the run risk hitting a payment provider's live mode or sending a real email/webhook, or is that sandboxed away by design? feels like the same power that catches real bugs could also cause real damage if it's not scoped carefully.
How does this handle apps with heavy external service dependencies, like third-party APIs that need real credentials during a test run?
how does it actually handle test flakiness when the sandbox environment differs from CI, and is that something i have to configure myself or does it handle it under the hood
As a solo dev shipping AI-written code daily, this hits a real pain: unit tests pass but the actual app breaks. Question — can it catch visual regressions? In my product (image processing) the worst bugs are "output looks subtly wrong but nothing throws," and I've only been able to cover those with hand-written pixel-level regression tests.
how does it handle flaky stuff like network requests or third-party api calls when reproducing bugs in the sandbox?