Genspark app testing

Test the apps you build with Genspark before real users open them

Genspark's Super Agent builds a full app from a prompt, but the polished first build often ships broken. Kane CLI drives your live Genspark app in a real browser, verifies the flow, and returns a pass or fail. Free to install.

npm install -g @testmuai/kane-cli

or read the documentation

Why test apps built with Genspark

Genspark's AI Developer turns a prompt into a working build: frontend and backend code written together, a built-in database, a live preview, and one-click publish to Cloudflare Pages or Vercel. That speed is the point, but the generated logic only gets exercised once a real visitor actually uses it.

That is where Genspark apps break. Reviewers report the same pattern across builds: the UI looks finished while the signup form silently fails, the dashboard chart never updates, and each fix-prompt risks a regression loop that reintroduces an old bug.

Kane CLI is the second pair of eyes. Describe the journey in plain English and it drives your live Genspark URL in a real Chrome browser, fills the forms, and checks the data persists. Genspark syncs to GitHub, so your agent can run it.

Kane CLI verifying a generated app flow in a real browser

What Kane CLI tests in your Genspark app

Forms, data, charts, and the deployed build, verified for a real user.

Generated signup and login forms

Submit the auth forms Genspark wired up, confirm the redirect after login, and verify the session holds. This is where AI Developer builds fail most: the form looks right but the submit handler is dead and nothing reaches the backend.

Data create, read, and persistence

Run the create-read flow against Genspark's built-in database, then reload and confirm the row reads back. Catch the silent insert that never persists, the gap reviewers describe as polished UI over broken functionality.

Interactive widgets and charts

Click the date-range selectors, KPI cards, and SVG line charts Genspark loves to generate, and confirm the numbers actually recompute. Catch the animated dashboard that looks live but never updates.

Checkout, pricing, and CTAs

Walk the purchase or signup CTA on a generated landing page or pricing grid, and confirm each button routes and converts, so a dead CTA never reaches a real visitor.

Deployed build, not just preview

Run against your Cloudflare Pages or Vercel domain to catch the blank screen on publish, a 404 on refresh from client-side routing, and asset chunks that 404 after a redeploy.

Regression after every reprompt

Genspark iterates by conversation, and AI builders fall into regression loops: fix A, break B, then A returns. Lock in known-good journeys and re-run them after every prompt so a fix never quietly breaks a working flow.

Build up confidence before real users open it

Start in your terminal

Validate on the cloud

Release with confidence

Built for the prompt-then-verify loop

Kane CLI and KaneAI share the same automation engine and dashboard.

Built for the prompt-then-verify loop

Genspark's Super Agent turns your prompt into a working site or app in minutes. Kane CLI proves the generated forms, data, and CTAs work for a real user before that app reaches anyone.

Verify the live app, not the code that looks right

Generated builds read polished far more often than they run correctly. You or your coding agent point Kane CLI at the live Genspark URL, and it drives the deployed app in a real browser to confirm the flow, not the screenshot.

Evidence you can share

Every run produces a persistent video, a step trace, and a replay link you can drop into a PR, a Genspark bug report, or a team message.

Test your Genspark app in three steps

Install Kane CLI

Run npm install -g @testmuai/kane-cli and sign in with your TestMu AI account. Nothing to wire into your Genspark project or its generated backend.

Point it at your Genspark URL

Use the Genspark preview link or your deployed Cloudflare Pages or Vercel domain. Run flows from the terminal, or tell Cursor, Claude Code, or Codex to run them against the synced GitHub repo.

Describe the flow and verify

Write the journey in plain English: sign up, create a record, confirm the dashboard updates. Kane CLI drives a real browser, verifies each step, and returns a pass or fail with evidence.

Get Started With Kane CLI

🎉 Launch offer: Bonus credits for the first 3 months on paid plans

Choose the right plan for you

Local test authoring via CLI

Auto-heal & vision

View test cases on UI

Test Manager

Free

/month

200 Credits

Resets in every

30 days

Free tier

Starter

$19

/month

2000 Credits

Launch: 4,000 Credits (+100%)

Bonus for first 3 months

Free tier

Get the technical rundown

Blog

A look at Kane CLI. What we built, what it does, and where it is headed.

Read the blog

Documentation

Everything you need to install, configure, and run Kane CLI in under 2 minutes.

View documentation

GitHub

Browse the source, file issues, and follow the roadmap on GitHub.

Open GitHub

Frequently asked questions

Install Kane CLI, then describe the journey in plain English, for example "open the published site, fill in the signup form, submit, and confirm the dashboard loads with my new record." Kane CLI drives your live Genspark URL in a real Chrome browser, walks the flow, checks each step, and returns a pass or fail with video evidence. Run it from the terminal against the Genspark preview or your deployed Cloudflare Pages or Vercel domain, or let your AI coding agent run it after pushing the project to the synced GitHub repo.

Genspark's AI Developer writes the frontend and backend from a single prompt, and reviewers consistently report the same gap: the first build looks polished but ships broken functionality that needs debugging through more prompting. The classic break is a landing page or dashboard that renders perfectly in the preview, then the signup form silently fails to submit, the KPI chart never recomputes, or a button does nothing. Because every fix-prompt can quietly reintroduce an old bug (the well-documented regression loop), clicking through by hand once is not enough. Kane CLI verifies the real flow in a browser, as a real user, before you publish.

The signup and login forms Genspark generated, create-read-update-delete against its built-in database, the interactive pieces it loves to ship (date-range selectors that recompute numbers, sparkline and SVG charts, multi-screen onboarding with swipe gestures), checkout and pricing-card clicks, and the deployed build rendering instead of a blank screen. It also catches SPA 404s on refresh, console errors, and broken API calls. It checks each step, not just the final screen, and flags the exact point where the generated app breaks.

Yes. Genspark pushes your project to GitHub with one click, so a coding agent like Cursor, Claude Code, or Codex can take over and edit it. Point that agent at the guide at testmuai.com/kane-cli/agents.md and it will install Kane CLI, run flows with the --agent flag, read the structured results, and fix the dead form button or broken chart before you see it. Generate with Genspark, hand off to your agent, verify with Kane CLI, in one loop.

Yes. Authenticate with your TestMu AI credentials, pass --headless and --timeout, and gate your pipeline on the exit code: 0 on pass, 1 on fail, 2 on setup or auth errors, and 3 on timeout. Run your signup, data, and checkout flows on every Cloudflare Pages or Vercel deploy, so a silently failing form or broken redirect never reaches production.

The CLI is free to install and use. Local runs are free; cloud runs on the TestMu AI grid are billed against your TestMu AI plan. Start on the free tier and verify your Genspark app end to end without a credit card.

Teach your agent to test what Genspark builds

Genspark pushes your app to GitHub. Point your coding agent at the Kane CLI guide and it will install, authenticate, and verify the signup, data, and CTA flows in a real browser on its own.

Point your agent to: testmuai.com/kane-cli/agents.md