Vibe testing
Vibe testing is the QA workflow where you paste a URL plus one sentence and a goal-based test runs against the deployed product.
Vibe testing is the discipline of producing browser, native mobile, or API evidence for the thing you just shipped — without writing a test suite first. You paste a URL and a single sentence describing the goal; an AI planner authors the scenario; a real engine (browser, native iOS/Android, or API stress runner) executes it; a vision model reviews the screenshots; you walk away with a token-gated public proof page. Vibe testing is the QA-side counterpart to vibe coding — the same ship-fast, AI-native philosophy applied to verification. Not mood or culture assessment, not water-well testing.
Read the full definition →
Vibe testing platform
A vibe testing platform runs multiple test engines — web, native mobile, and API — on the same AI planner, the same /app shell, and the same release-health timeline.
A vibe testing platform is the multi-engine counterpart to a single-purpose tool. Three engines share one planner, one shell, and one timeline: Playwright for web (Chromium, Firefox, WebKit, mobile web), Appium for native iOS and Android (XCUITest, UiAutomator2), and k6 for API stress (rps, p95, p99, error rate). A solo founder signs in once, picks a saved scenario from their phone, hits Run, and gets a shareable proof page regardless of which engine ran. The platform category is distinct from test management, CI orchestration, or QA-as-a-service.
See the platform category →
Vibe testing SaaS
A vibe testing SaaS delivers vibe testing as a cloud subscription — pricing tiers, no on-prem install, and the execution plane runs on the vendor's servers.
A vibe testing SaaS is the cloud-delivery counterpart to running k6 and Appium yourself. You pay a monthly or annual fee, the execution plane runs on the vendor's infrastructure (no macOS simulator fleet to maintain), and the mobile shell is a hosted web app at /app you can open from your phone. Free, Starter, Growth, and Scale tiers segment by engine access, monthly run volume, and high-volume k6 capacity. Enterprise adds SSO, private deployment, and managed Appium device farms.
See the SaaS pricing tiers →
AI vibe testing platform
An AI vibe testing platform uses an AI planner to author test scenarios from a URL plus a one-sentence goal, then dispatches a real engine to execute.
An AI vibe testing platform is the category Well Tested files under. The AI planner is responsible for authoring steps, surfacing assumptions and missing context, and reporting confidence. The real engine is responsible for execution. The vision model is responsible for scoring the screenshots against the goal. A solo founder does not write a multi-step agent prompt, a Playwright spec, or a k6 script — they paste a URL and one sentence, then review the planner's assumptions before run.
See the multi-engine breakdown →
Multi-engine vibe testing
Multi-engine vibe testing runs web (Playwright), native mobile (Appium), and API stress (k6) from one planner, one shell, and one release-health timeline.
Multi-engine vibe testing is the practice of routing a single AI-authored scenario to whichever engine matches the goal — Playwright for browser flows, Appium for native iOS/Android gestures, k6 for API stress — and writing the evidence into the same release-health history. The benefit is one source of truth: a regression on the homepage that broke the iOS login flow and pushed the API past p99 shows up as three correlated findings on one timeline.
Vibe testing tool
A vibe testing tool is a single-purpose product that helps you run, record, or share a vibe test. The category spans planners, runners, and proof-page generators.
A vibe testing tool sits inside the vibe testing workflow at one stage: the planner (AI authoring the steps), the runner (Playwright/Appium/k6 executing), or the proof-page generator (the shareable evidence). Well Tested ships all three on the same shell — and is therefore a vibe testing platform, not a vibe testing tool. Adjacent vibe testing tools include AI planner CLIs, screenshot-diff services, and share-page builders.
See vibe testing vs vibe testing tools →
Vibe testing in QA
Vibe testing in QA is the practice of running a goal-based, AI-authored test against the deployed product and capturing the evidence as a release artifact.
Vibe testing in QA means treating the proof page as a first-class release artifact — alongside the commit, the deploy URL, and the changelog entry. The QA lead opens the share link in Slack, sees the screenshots and the vision verdict, and either signs off or escalates. Vibe testing is not a replacement for unit tests, integration tests, or code review — it is the verification layer above all of them, where the goal is "did the user actually experience what we shipped?"
Read the QA definition →
Playwright
Playwright is the open-source browser-automation library used by Well Tested to run web vibe tests in Chromium, Firefox, and WebKit.
Playwright is the engine behind every web vibe test on Well Tested. It supports headless and headful Chromium, Firefox, and WebKit, plus iOS Safari and Android Chrome via mobile web emulation. Multi-browser parallel runs are available on Growth+; Free and Starter ship Chromium only. Playwright MCP is the Model Context Protocol server that wraps Playwright as a tool for AI agents — see Playwright MCP below.
Appium
Appium is the open-source mobile automation framework used by Well Tested to run native iOS and Android vibe tests on real devices and simulators.
Appium is the engine behind every native mobile vibe test on Well Tested. It supports XCUITest (iOS) and UiAutomator2 (Android) drivers, tap/swipe/type/accessibility-id lookup, and screenshots + accessibility-tree evidence at every step. Native Appium execution is available on Growth+; Free and Starter ship with browser-only runs. Appium MCP is the Model Context Protocol server that wraps Appium as a tool for AI agents — see Appium MCP below.
k6
k6 is the open-source load-testing tool used by Well Tested to run API stress vibe tests against an endpoint and report rps, p95, p99, and error rate.
k6 is the engine behind every API stress vibe test on Well Tested. The k6 worker reports request rate, response time percentiles (p50, p95, p99), error rate, and a per-endpoint breakdown. Pay-as-you-go k6 is available on Free and Starter ($0.50 per 1k requests); sustained k6 runs unlock on Growth and Scale. Scale runs up to 1,000 rps for 600 seconds; Enterprise negotiates higher capacity. k6 runs as a sibling engine to Playwright and Appium on the same /app shell.
How to run k6 from your phone →
Playwright MCP
Playwright MCP is the Model Context Protocol server that exposes a Playwright browser session as a tool for AI agents to drive.
Playwright MCP wraps Playwright in the Model Context Protocol — the AI-agent tool-integration layer. It gives an AI agent a browser handle and expects the agent to author the prompt loop, dispatch the browser steps, and parse the result. Well Tested uses Playwright MCP internally as one of its execution layers, but adds an AI planner (so the customer does not author the agent prompt), a vision verdict (so the customer does not parse the screenshots), and a shareable proof page (so the customer does not write a session log). Well Tested is therefore a Playwright MCP alternative for builders who want the outcome, not the browser handle.
Playwright MCP alternative →
Appium MCP
Appium MCP is the Model Context Protocol server that exposes a real iOS or Android device as a tool for AI agents to drive via XCUITest or UiAutomator2.
Appium MCP wraps Appium in the Model Context Protocol. It gives an AI agent a native iOS/Android device handle with the same tap/swipe/type/accessibility-id lookup primitives that Appium exposes directly. Well Tested uses Appium MCP as its native mobile execution plane on Growth+ — adding the planner, the vision verdict, the share page, and the /app mobile shell that Appium MCP alone does not provide.
Mobile testing shell
The mobile testing shell is the /app web app at welltested.io/app — pick a saved scenario, hit Run, watch status, share the proof link — from your phone.
The mobile testing shell is the customer-facing UI for running vibe tests from a phone. You sign in, pick a saved Playwright, Appium, or k6 scenario from a list, hit Run, watch status push back from the worker (queued, planning, running browser, vision verdict, sharing), and tap to copy a token-gated public link. The shell is a hosted web app — no app store install, no native client. Available on Growth+; Starter shows a preview card with a one-click upgrade CTA.
See the mobile shell in context →
Run k6 from your phone
Run k6 from your phone means opening the /app mobile shell, picking a saved k6 scenario, and watching the rps + p95 + p99 + error rate push back as the run completes.
Run k6 from your phone is the canonical how-to for solo founders and on-call engineers who want API stress results without a laptop. The /app mobile shell handles sign-in, scenario selection, run dispatch, status polling, and proof-page sharing. The k6 worker runs on the Well Tested infrastructure; you watch from your phone. Available on Growth+; pay-as-you-go k6 is available on Free and Starter.
How-to: run k6 from your phone →
Appium alternative
An Appium alternative is a product that runs native iOS and Android tests without requiring you to maintain a simulator fleet, a CI runner, or a webdriverio codebase.
An Appium alternative should cover the same gestures (tap, swipe, type, accessibility-id), the same drivers (XCUITest for iOS, UiAutomator2 for Android), and the same evidence (screenshots + accessibility-tree snapshots). The differentiating factors are: who runs the device farm (you vs the vendor), who authors the test (you vs an AI planner), and who ships the proof page (you vs the vendor). Well Tested is an Appium alternative for solo founders who want the engines without the maintenance — see the k6 + Appium comparison for the self-hosted counterpart.
Appium alternative comparison →
Playwright MCP alternative
A Playwright MCP alternative is a product that gives an AI agent a browser session without requiring the customer to write the prompt loop, dispatch the steps, or parse the screenshots.
A Playwright MCP alternative is for builders who want the outcome of an AI-driven browser run — a vision verdict on the screenshots, a shareable proof page, a release-health entry — without writing a multi-step agent prompt. Well Tested wraps Playwright MCP internally and adds the planner, the vision verdict, the proof page, and the /app mobile shell on top. See the Playwright MCP comparison for the build-vs-buy breakdown.
Playwright MCP alternative comparison →
AI planner
The AI planner is the LLM that turns a URL plus one sentence into a structured test plan with assumptions, missing context, browser steps, and a confidence score.
The AI planner is the first stage of every Well Tested vibe test. It receives a URL and a one-sentence goal; it returns a structured plan with the steps it intends to run, the assumptions it is making about the page's intent, the context it wishes the customer had given it, and a confidence score from 0 to 100. The customer can push back on the plan before run. The planner is not the runner — Playwright, Appium, and k6 are. The planner is the thing that decides what to run.
Vision verdict
The vision verdict is the LLM's review of the run screenshots — did the evidence actually prove the goal stated in the URL plus one sentence?
The vision verdict is the last stage of every Well Tested vibe test. The vision model receives the step screenshots, the planner's goal, and the planner's intended assertions; it returns a pass/fail verdict with a one-paragraph explanation and a per-step confidence breakdown. The verdict is what makes the proof page useful — it separates what the engine observed from what the planner inferred, and it surfaces exactly which step failed when something goes wrong.
Shareable proof page
A shareable proof page is a token-gated public URL that shows the screenshots, the vision verdict, and the run metadata for one Well Tested vibe test.
A shareable proof page is what you get when a vibe test finishes. It is a public URL at /vibe/<slug>/share?t=<token>; the token gate prevents SEO indexing and lets the customer revoke access. The page shows the planner's goal, the steps the engine ran, the screenshots at each step, the vision verdict, and a copy-pasteable badge for the marketing site. Shareable proof is the single most important output of the vibe testing loop — it converts a private run into a release artifact.
Release-health dashboard
The release-health dashboard is the per-app history of vibe runs — trends, recurring bugs, regressions, and the vision verdict that explains each one.
The release-health dashboard is the long-term value layer on top of the per-run proof page. Every run feeds a release-health entry: planner goal, engine, verdict, screenshots, step counts, and a link to the full proof. Trends emerge over time — a button that failed on every deploy, a checkout flow that regressed after the new pricing page, a k6 p99 that crept from 280ms to 520ms over three weeks. Available on Growth+.
Real engine
A real engine is the Playwright, Appium, or k6 worker that actually executes the test — distinct from a simulated, mocked, or stubbed response.
A real engine in the vibe testing context means Playwright actually driving a Chromium browser, Appium actually dispatching a tap to an iOS simulator, or k6 actually sending HTTP requests to a target URL and measuring response time. Vibe testing insists on real engines because the entire point of the loop is to capture what a real user would have experienced. Simulated, mocked, or stubbed responses are not what vibe testing tests — and the vision verdict downstream is calibrated to detect the difference.
Token-gated share
A token-gated share is a public URL with a private token — anyone with the link can view the proof, but the URL is not indexed by crawlers and the customer can revoke it.
Token-gated share is the privacy primitive under the shareable proof page. The share page lives at /vibe/<slug>/share?t=<token>; without a valid token the page returns 404 to crawlers and 401 to humans. The token is per-share and can be rotated from the customer dashboard. The page is intentionally not indexable by Google or AI crawlers — only the customer who runs the test decides who sees the proof.
On-the-move mobile shell
The on-the-move mobile shell is the /app web app — pick a saved scenario, hit Run, watch status, share the proof link — from a phone in a coffee shop.
The on-the-move mobile shell is the same /app shell as the mobile testing shell, with an emphasis on the customer being away from their laptop — on the train, in a meeting, on the couch. The shell is responsive, push-status-aware, and tap-friendly. It is the proof that vibe testing is not just browser automation — it is the workflow you can complete from your phone.
Goal-based test
A goal-based test is a vibe test specified by a URL and a one-sentence goal — the planner infers the steps, the engine executes them, the vision model scores the result.
A goal-based test is the input shape vibe testing was built around. The customer does not write a multi-step test plan, a Playwright spec, or a k6 script. The customer states the goal — "the user can complete checkout with a saved card" — and the planner, the engine, and the vision model do the rest. This is the opposite of script-based testing, where the customer authors every step.
Browser proof
Browser proof is the per-step screenshot sequence captured by the Playwright engine during a web vibe test — the visual evidence the vision model reviews.
Browser proof is one half of the evidence a vibe test ships with (the other half is the vision verdict on those screenshots). Every step in the planner's plan gets a screenshot at the moment the engine considers the step complete; the sequence of screenshots is what the vision model reviews to decide pass/fail. Browser proof is stored on the shareable proof page and on the release-health entry for the run.
Native mobile proof
Native mobile proof is the per-step screenshot + accessibility-tree snapshot captured by the Appium engine during a native iOS or Android vibe test.
Native mobile proof is the counterpart to browser proof for native iOS/Android runs. Every step captures both a screenshot (visual evidence) and an accessibility-tree snapshot (structural evidence — element labels, roles, states). The vision model uses both to decide pass/fail. Native mobile proof is what proves that a tap landed on the right element, that a swipe scrolled the list correctly, and that a type-into-field committed the text.
API stress proof
API stress proof is the rps / p95 / p99 / error-rate timeline + per-endpoint breakdown captured by the k6 worker during an API vibe test.
API stress proof is the counterpart to browser proof and native mobile proof for API runs. The k6 worker reports the request rate it sustained, the response time percentiles (p50, p95, p99), the error rate, and a per-endpoint breakdown of failures. The vision model reviews the timeline to surface anomalies — a p99 spike correlated with a deploy, an error rate that climbed past 1% under load. API stress proof is what you paste into the postmortem.
Pricing tier
A pricing tier is one of the five Well Tested plans — Free, Starter, Growth, Scale, or Enterprise — that segments engine access, monthly volume, and high-volume k6 capacity.
Well Tested pricing tiers are: Free ($0/mo, 3 browser runs, Chromium only, no Appium, no k6), Starter ($79/mo or $853/yr, recurring Chromium evidence + branded share pages, pay-as-you-go k6), Growth ($249/mo or $2,688/yr, Playwright + Appium + k6, run from your phone via the /app mobile shell — most teams land here), Scale ($799/mo or $8,629/yr, k6 to 1,000 rps, Appium device farm, 90-day evidence), Enterprise (custom, SSO, private deployment, negotiated capacity). 10% annual discount on every paid tier.
See all pricing tiers →
Water-well testing
Water-well testing is the unrelated industry that shares the phrase 'well tested' — water quality, well maintenance, plumbing diagnostics. Not what we do.
Water-well testing is the disambiguation target for the phrase 'well tested' on Google, Bing, and AI answer engines. It is the industry of testing private water wells for contaminants, hardness, and flow rate. The brand collision causes Perplexity, in particular, to describe Well Tested as 'testing kits, devices, or evaluations' when it cannot find the canonical disambiguation. The brand-defensive answer-first block on /pricing and the /about page exist to disambiguate.
Well Tested pricing
Well Tested pricing is the five-tier subscription at welltested.io/pricing — Free $0, Starter $79, Growth $249, Scale $799, Enterprise custom.
Well Tested pricing is the explicit price ladder for the vibe testing SaaS. Free ships with 3 browser runs/month, no card required, Chromium only. Starter ships with recurring Chromium evidence plus branded share pages. Growth unlocks Playwright + Appium + k6 + the /app mobile shell — the most popular tier. Scale unlocks k6 to 1,000 rps and 90-day evidence retention. Enterprise adds SSO and private deployment. Annual plans receive a 10% discount on every paid tier.
See Well Tested pricing →