> For the complete documentation index, see [llms.txt](https://docs.duku.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.duku.ai/core-concepts/goals-and-intent-tests.md).

# Goals & Intent Tests

Goals tell Duku what matters. Intent tests prove those journeys still work.

### Goals

A **goal** is a business-critical destination in the state graph, such as a checkout confirmation page, a successful login redirect, or a registration completion screen.

Duku identifies likely goals from graph structure, page characteristics, and navigation patterns.

### Intents

An **intent** is a human-readable description of a path to a goal. Duku generates descriptions like:

* *User opens the login page, enters credentials, and reaches the dashboard*
* *User adds an item to cart, completes checkout, and reaches order confirmation*

### Intent tests

**Intent tests** replay discovered journeys in a real browser. Duku selects the shortest known paths to each goal, then executes them against the target.

This gives you a simple answer to a hard question: can users still complete the journeys that matter?

{% hint style="info" %}
Intent tests are derived from exploration data, so they adapt as your application changes.
{% endhint %}

#### Run intent tests

* **From the app:** Open a product, choose a target from the top-right target menu, then click **Run Tests**
* **From the API:** Call `startIntentRuns`

#### Results

Each run includes:

* **Status:** Whether the journey completed
* **Step log:** Which steps passed or failed
* **Screenshots:** Visual evidence for each step
* **Errors:** Any issue captured during replay