How to Use Checkpoints in Kane CLI

A checkpoint is a point in a test where KaneAI checks something while the test runs. Use checkpoints to assert conditions, branch on results, or extract values for later steps.

Checkpoint Types

Type	What it does
Assertion	Verifies that a condition is true, and fails the test if it is not
If/Else	Branches the test based on a condition
Extraction	Stores a value for use in later steps

All three types work with every analyze method listed below.

Analyze Methods

Each checkpoint uses an analyze method, which decides where KaneAI looks for the data:

Method	Data Source	When to Use
Visual	Screenshot (what you see on screen)	Text, labels, prices, counts, colors, visibility checks
Textual (DOM)	Page DOM elements	Element states (disabled, checked), CSS properties, HTML attributes
URL	Browser URL bar	URL path, query params, redirects
Title	Page title	Document title verification
DevTools	Browser internals	Network traffic, console logs, performance, cookies, localStorage, clipboard

How to Use

Write assertions in plain language in your objective. KaneAI picks the right analyze method for each one:

Assert: the price is $29.99                    → Visual
Assert: the submit button is disabled          → Textual (DOM)
Assert: URL contains /checkout                 → URL
Assert: page title contains "Dashboard"        → Title
Assert: no API calls returned 5xx              → DevTools (Network)
Assert: no console errors                      → DevTools (Console)
Assert: page LCP is under 2500ms               → DevTools (Performance)
Assert: session cookie exists                  → DevTools (Cookies)
Assert: auth_token exists in localStorage      → DevTools (localStorage)
Assert: clipboard contains the copied link     → DevTools (Clipboard)

Extractions work the same way:

Store the product price                        → Visual
Store the current URL                          → URL
Store all cookies                              → DevTools (Cookies)
Store the API response body                    → DevTools (Network)

Operators

Assertions support these comparison operators:

Operator	Meaning	Example
`equals`	Exact match	price equals “29.99”
`contains`	Substring match	URL contains “/checkout”
`not_contains`	Does not contain	title not contains “Error”
`gt` / `gte`	Greater than / or equal	items greater than 5
`lt` / `lte`	Less than / or equal	LCP less than 2500
`not_equals`	Not equal	status not equals “failed”

Learn More

Visual Assertions: screenshot-based text and visibility checks
Textual (DOM) Assertions: element states and attributes
URL Assertions: URL-based checks
Title Assertions: page title checks
DevTools Assertions: network, console, performance, cookies, localStorage, clipboard

​Checkpoint Types

​Analyze Methods

​How to Use

​Operators

​Learn More

Checkpoint Types

Analyze Methods

How to Use

Operators

Learn More