Questions about AI-native vibe testing.

Vibe testing is end-to-end testing for the AI-coding generation. You paste a URL and one sentence about your app; the AI planner authors a structured test plan with assumptions, missing context, browser steps, and confidence. A real browser runs it. A vision model explains whether the screenshots prove the goal. You walk away with a token-gated public proof page and a release-health entry.

Hand-written Playwright tests take hours to author, need a repo, and break every time the UI changes. Vibe testing starts from a URL + 1 sentence; the AI authors a stable, accessibility-first test plan; Playwright MCP runs it in a real browser; a vision model reads the screenshots; you walk away with a shareable proof page and a release-health entry. No source-code access, no SDK install, no test maintenance.

A PlannerOutput with: inferred product label, assumptions the planner is making, missing context (critical entries block the run; advisory entries become notes on the share page), browser test steps, API/k6 stress guidance, safety warnings, and a self-rated confidence (0..1). The full planner JSON is persisted on the run, so the share page and release-health history can read it without re-running the model.

After the browser run finishes, a vision model reviews the final screenshot and any failed-step screenshots. It returns a structured verdict: did the visual evidence prove the goal? What was the root cause of any failure? What are the limitations of the verdict? What should the customer do next? The verdict renders on the share page above the screenshot timeline and feeds the release-health history.

Growth and Scale customers see /app/insights — readiness score, blockers, pass-rate trend, top failure categories, recent bug/regression history, and recurring regressions. Growth gets basic release health over a 30-day window. Scale gets full release health with per-step latency, flakiness detection, trend analysis, exports, and deeper drilldowns. Free and Starter see per-run reports but not the aggregate dashboard.

Vibe tests run on the Playwright MCP server (Chromium by default, Firefox and WebKit on Growth and above). Every step is asserted in a real browser; screenshots are captured per step; console and network evidence are recorded where available. After the run finishes, the vision pass reviews the screenshots and the planner's record is saved on the run.

Free captures a screenshot of the final state and a video on failure. Paid tiers (Starter+) record failure video; Growth and above also support on-demand pass video. Videos are kept for 7 days on Starter, 30 days on Growth, and 90 days on Scale.

A typical 3–6 step vibe test finishes in 15–30 seconds end-to-end. The first run after signup may take a few extra seconds while the Playwright MCP browser context spins up.

Vibe mode needs a URL and one sentence (10–500 characters) about your app. The planner produces the structured plan. Explicit mode is preserved for users who want to write a detailed prompt.

Every successful run produces a token-gated /vibe/[slug]/share?t=<token> URL with the planner record, vision verdict, per-step screenshots, step outcomes, and the failure video if available. The slug is a public identifier; the 32-character token is the only secret. Free keeps 1 active share page; paid tiers get unlimited.

Yes — that's the wedge. The public share page is built for Slack, Twitter, and iMessage link previews (OG + Twitter card meta). Vibe coders ship the URL in standup, in launch announcements, or in a portfolio.

API stress is the sibling engine to browser vibe tests. Growth and Scale users can run bounded k6 checks from /app/vibe using the same minimum input: URL + one-sentence goal. The app enforces URL safety, plan gates, RPS caps, duration caps, and tokenized proof pages with p95 latency, request count, error rate, and failed checks.

Growth includes 200 API stress runs per month up to 100 RPS for 60 seconds. Scale includes 2,000 runs up to 1,000 RPS for 600 seconds. Free and Starter are gated to the upgrade path or a future pay-as-you-go k6 add-on. Public launch still requires the k6 worker to be deployed and verified in production-private-beta.

Chromium on Free and Starter. Chromium, Firefox, and WebKit on Growth and Scale. The browser is selected per-run in /app/vibe.

Free: 3 days for screenshots, no video. Starter: 14 days for screenshots, 7 days for video. Growth: 30 days for screenshots and video (every-step). Scale: 90 days. Enterprise is custom.

Cypress and Playwright are tools you wire into a repo and own. QA Wolf is a managed service for hand-written tests. Vibe testing is goal-based: URL + 1 sentence → AI plan → real browser run → vision verdict → shareable proof page and release-health entry. No source-code access, no test maintenance, no per-test pricing.

Yes. The /app product shell exposes projects, environments, scenarios, and runs that work for hand-authored scenarios too. The AI scenario generator is the same generator behind /app/vibe — the difference is whether the run is one-off or part of a saved scenario library.

Yes. Free gives you 3 vibe test runs per month (then a 7-day Starter or Growth trial), 1 parallel run, Chromium only, final screenshot, failure video, 1 active public share page, and 3-day screenshot retention. A card is required up front — you are only charged if you don't cancel the trial. Upgrade to Growth for multi-browser, the release-health dashboard, and AI credit top-ups.

Yes — Enterprise covers custom monthly runs, custom concurrency, private/VPN environment agents, custom k6 limits, SSO, security review, custom artifact retention, and custom support. Use /contact to start a conversation.

Email support, the /contact page, or open an issue. Paid tiers add priority support and success planning. We respond fastest on the in-app help widget inside /app/vibe.

Yes. /app/vibe is live in private beta. Paste a URL and one sentence; the planner explains what it will test; the browser runs it; the vision pass produces a verdict; you get a token-gated public proof page and a release-health entry. Product access remains allowlisted during private beta.