Explore the whole application
Kane reaches every screen and connects them on one map.
Paste your URL. Kane explores your running app, shows you what is broken and designs the test cases to prove it works.
Get KaneAI Max free for a month. Worth $179.
No PRD or test scripts needed
Kane reaches every screen and connects them on one map.
Functional, backend and accessibility issues, each with evidence.
Use cases, acceptance criteria and test cases for end-to-end coverage.
Kane Explore is how Kane learns your app. Parallel browser agents explore every screen and user flow, report findings with evidence and hand the map to Kane Assurance for end-to-end coverage.
Browser agents explore different screens and user flows in parallel, logging every request and console error. No scripts to write.
Functional, backend and accessibility issues on every screen. Each one is tied to its flow, with the failed request and a screenshot.
Most apps have no current PRD. Kane writes the use cases and acceptance criteria from the map, so everyone knows what must hold true.
Kane Assurance designs test cases from that context. Each one traces back to its acceptance criterion and screen for end-to-end coverage.
Every release changes your app. Kane explores it again, adds new screens to the map and rechecks earlier findings, so your context never goes stale.
A signed-in customer checks out their cart and finds the order in their history.
Sample output. A person reviews the test design before choosing to run it.
Your coding agent says the change works. Run Kane on the preview URL and catch broken flows, dead buttons and failed requests before code review starts.
A hotfix or a big release just reached staging. Kane explores it again and shows new screens, changed flows and the findings that are back.
No docs, no tests and nobody left who built it. Give Kane the URL and get every screen, every user flow and the PRD the app never had.
Open a map to see its screens, flows and findings. Your results will differ with your app.
Paste a staging or preview URL. The run is read-only, so your data stays untouched.
One command from your terminal, or one prompt for your coding agent.
$ npm install -g @testmuai/kane-cli $ npx @testmuai/kane-cli-skill $ kane-cli login $ kane-cli explore run --project <id> \ --url https://your-app.example.com --policy read_only $ kane-cli cover
Install Kane CLI with: npm install -g @testmuai/kane-cli Install the Kane CLI skill with: npx @testmuai/kane-cli-skill Sign in with: kane-cli login Then explore my web app with: kane-cli explore run --project <id> --url <my app URL> --policy read_only Ask me for the project id and the URL if you do not have them. When the run finishes, run kane-cli cover and summarise the application map and the findings.
How Kane explores, what it checks and how it treats your application.
Kane Explore is the agentic exploration capability of Kane, the testing agent from TestMu AI (formerly LambdaTest). Starting from a single URL, parallel browser agents explore your running application, map its screens and flows, and report issues with browser evidence. You write no test scripts.
Every screen it can reach within the run limits. Kane stops at a login it has no account for, so add a test account for the screens behind sign-in. It covers breadth across your app, and a person decides which flows need deeper tests.
No. A finding is a lead with evidence attached. It stays open until a person reviews it and decides whether it is a real bug. Kane does not know your business rules, such as which discount a customer should get, so it cannot judge those on its own.
Not from this page. Runs started here are read-only, so Kane blocks POST, PUT, PATCH and DELETE requests. Kane CLI allows changes by default, so pass --policy read_only for the same behaviour. Blocking those requests does not guarantee every interaction is free of side effects, so review the policy before exploring a sensitive environment.
You give Kane the URL of your running web application. For an app behind login you can add a test account. Kane's browser agents follow links, controls and forms in parallel, discover screens and map the flows that connect them.
They are separate cloud browser sessions that Kane runs at the same time. Each agent explores a different screen or flow, so a multi-screen application is mapped faster. Kane Explore supports up to 20 browsers in parallel.
Yes. Kane checks discovered screens for console errors, failed network requests, broken links, slow requests and accessibility issues. You do not write assertions first.
Yes. Each finding links to the screen and the flow where Kane saw it. It includes browser evidence, such as the failed request or the console error. Your team has a concrete place to start.
Discovered screens and flows become application context. From that context Kane derives business entities, use cases, acceptance criteria and linked test cases. Exploration designs tests and does not execute them. A person reviews the test design before choosing to run it.
Your coding agent checks the change it just made. Kane explores the whole running app and is independent of the agent that wrote the code. It also flags issues nobody asked it to look for.
A scripted suite checks the flows someone wrote assertions for. Exploration maps the screens and flows the suite never touched and flags issues nobody asked it to look for. The two work together.
Yes. Install @testmuai/kane-cli and give your coding agent the Kane CLI commands. After a change it can run kane-cli explore run and kane-cli cover, then summarise the application map and the findings.
A run ends when the agents have nothing left to explore or when it reaches a built-in limit: one hour, 400 actions or 800 model calls. From Kane CLI you can also set your own cap.
Not yet. Kane Explore works on web applications today.
Paste one URL. Kane shows you the map, the findings and the test cases to review.
Explore your app