> For the complete documentation index, see [llms.txt](https://docs.ratl.ai/guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ratl.ai/guide/features/dashboard.md).

# Understanding Dashboard: A Complete Guide

## Dashboard

The **Dashboard** is your home screen in ratl.ai Studio. It’s designed to do two things fast:

1. **Start a test** (for modules that are enabled on your plan)
2. **View insights** (only for enabled modules — the dashboard won’t show analytics for modules you can’t use)\ <br>

   <figure><img src="/files/8HZ3YzQqyePPVVcf5YC6" alt=""><figcaption></figcaption></figure>

> **Note:** On Free and Pro, the dashboard only shows insights for the modules currently enabled for those plans.\
> **Right now, Web Test is enabled**, so you’ll primarily see Web Test insights.

***

### What you’ll see on the Dashboard

#### 1) Test launcher (top section)

At the top, you’ll see a test entry area that lets you start a test without navigating anywhere else.

**Module selector**

You’ll see module tabs (example):

* **Web Test** (enabled)
* API Test / Load Test / App Review (may appear but will be disabled if not enabled on your plan)

If a module is not enabled, you won’t be able to start tests for it from the dashboard.

**Prompt input (start a test)**

You’ll see a prompt box where you can describe what you want to test.

Use it to write instructions like:

* “Validate that the homepage loads and the main CTA works”
* “Run an add-to-cart flow and confirm the cart updates”
* “Check that login works and the user lands on the dashboard”

**Execution configuration**

In the launcher, you can also choose execution settings (as shown in the UI), such as:

* **Device** (example: Desktop)
* **Browser** (example: Chrome)

These control how your web test is executed.

**Quick actions (icons)**

You may see helpful controls near the prompt area such as:

* **Attachment** (to add relevant context, when supported)
* **Voice** input (microphone icon)
* A **send / run** button to start the test

**DeepProbe toggle (optional)**

You may see an **Enable DeepProbe** toggle.

* Keep it off if you want a standard run.
* Turn it on when you want deeper investigation behavior (where applicable).

**Prompt suggestions**

Below the input area, you’ll see clickable suggestion chips (examples shown in the UI):

* “Run an add to cart test on …”
* “Run a video playback test on …”
* “Run a test for flight discovery on …”

These are just shortcuts — click one to prefill a prompt and edit it.

***

#### 2) Watch Demos dropdown (top-right)

On the top-right of the dashboard, you’ll see **Watch Demos**.

Use this when you’re new or you want a quick reminder of how to run tests.

* Click **Watch Demos**
* Select a demo video from the dropdown
* Follow along inside Studio

This is intentionally placed on the dashboard so users don’t have to hunt through docs to begin.

***

### Dashboard insights (enabled modules only)

The bottom section of the dashboard shows **module insights**, but only for modules that are **enabled for your plan**.

#### Web Test insights (currently enabled)

When Web Test is enabled, you’ll see a Web Test insights card that typically includes:

**Time range filter**

A time filter (example: **Last 30 Days**) controls the reporting window for what you’re seeing.

Use it when you want to:

* check recent stability,
* validate improvements after changes,
* or confirm if failures are increasing over time.

**Last run summary**

You’ll see a “Last Run” snapshot such as:

* the last tested URL
* time taken for that run

This helps you quickly confirm the most recent execution context.

**Key metrics (high signal, not noise)**

You’ll see a small set of core metrics that summarize test outcomes, for example:

* **Steps taken by agent** (how many steps the agent executed)
* **Assertions given by user** (how many checks you asked for)
* **Passed assertions**
* **Failed assertions**

This is meant to be quick at-a-glance health, not a full report.

**Visual summary**

You’ll also see compact visuals like:

* a run preview/screenshot for the last execution (when available)
* a pass/fail summary chart showing:
  * **Total tests**
  * **Passed vs Failed**

If there were zero failures in the selected time range, the dashboard will reflect that.

***

### Starting a test from the Dashboard (common flow)

1. Go to the **Dashboard**
2. Select an **enabled module** (example: Web Test)
3. Describe your test in the prompt box
4. Confirm execution settings (device/browser)
5. Click **Run**
6. Review results once execution completes (reports, video, assertions, etc.)

***

### What happens when more modules are enabled?

The dashboard is module-aware:

* When a new module becomes enabled for your plan, its **test launcher** and **insights section** will appear.
* If a module is not enabled, you won’t see its analytics cluttering your dashboard.

This keeps the dashboard focused on what you can actually run today.