Kane CLI Now Reads The Browser: Introducing DevTools Assertions

What the New Release Adds

Four layers of the browser are now testable directly inside a Kane CLI objective.

Network Requests

Kane CLI inspects live network traffic during a run. Assert on status codes, response bodies, and headers. New operators give you range checks like greater-than and less-than, plus not-equals.

kane-cli run "Go to https://shop.example.com, click 'Add to Cart', assert the network request to /api/cart returned status 200" --agent

The test no longer trusts the badge. It confirms the server actually said yes.

Console Output

Every console message is captured per run. Errors, warnings, and app logs. Use them as assertion targets or extract them as values. Log levels are normalized for you.

kane-cli run "Go to https://shop.example.com, click 'Add to Cart', assert the console has no errors" --agent

A clean console is now a pass condition, not something a human notices later.

Cookies and localStorage

Read, assert on, and extract both. Confirm a session cookie was set. Pull a cart ID. Verify what the app stored in the browser.

kane-cli run "Go to https://shop.example.com, click 'Add to Cart', store the cart_id cookie value as 'cart_id'" --agent

The stored value lands in final_state in the run result, ready to use in the next step.

Performance Traces

Browser performance data is collected inline and exposed as an assertion target. Gate a flow on load time.

kane-cli run "Go to https://shop.example.com, assert the page load time is under 3000ms" --agent

Slow is now a failure, not a feeling.

Code Export and Replay

DevTools actions are not just for one run. With code export enabled, network queries, console reads, cookie checks, and performance snapshots all generate runnable automation code. Replay is wired end-to-end too. Network capture starts and stops correctly around the replayed steps, and console, cookie, storage, and performance actions all run again exactly as recorded.

Record once. Replay anywhere. Export to code when you want it in your repo.

Note: Stop trusting the badge. Assert on network calls, console logs, cookies, and page speed in plain English with TestMu AI. Start for free

One Click, Four Checks

Here is the full picture on a real flow. A user clicks Add to Cart. On the surface, a badge changes. Underneath, a request fires, the console logs success, a cookie is set, and the page stays fast. Until now, a human opened DevTools to confirm all of that. Kane CLI does it for you.

kane-cli run "Go to https://shop.example.com, click 'Add to Cart', assert the network request to /api/cart returned status 200, assert the console has no errors, store the cart_id cookie value as 'cart_id'" --agent

Keep objectives under 15 steps. For wider coverage, split the four checks into separate runs and run them in parallel.

Note: Want the full command reference for DevTools assertions and replay? Read the Kane CLI documentation. View the docs

Get It

npm install -g @testmuai/kane-cli
kane-cli login

Already installed? Update in one line.

npm update -g @testmuai/kane-cli

Plain English. Real browser. Pass or fail. Now for the layer you could not see before.