> ## Documentation Index
> Fetch the complete documentation index at: https://docs.testdino.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Manual Testing Sessions

> Run exploratory testing sessions, log findings with attachments and linked issues, and roll up activity per release.

<Callout icon="book-open" color="#3B82F6">
  **What you'll learn**

  * How to create and configure a session
  * What a finding records and how its issues link back
  * What the session detail page shows: mission, findings, and the summary panel
  * When and how sessions close
</Callout>

A session is used for exploratory testing in TestDino. Each session includes a mission, current state, optional release link, and a list of findings discovered during testing. Findings can include comments, attachments, statuses, and linked issues.

<img src="https://testdinostr.blob.core.windows.net/docs/docs/manual-testing/manual-testing-sessions-list.webp" alt="Sessions list showing search, options, active and closed tabs, and session rows grouped by release" />

## Create Or Edit Session

You can create a session from the **+ Session** button. To edit an existing session, open it from the list and click **Edit** in the header.

| Field            | Description                                                               |
| :--------------- | :------------------------------------------------------------------------ |
| `Name`           | Required session name (up to 500 characters)                              |
| `Mission`        | Session charter or goal (up to 50,000 characters, supports inline images) |
| `Type`           | Session type from project settings                                        |
| `State`          | Workflow state from project settings; defaults to `New`                   |
| `Configuration`  | Setup label (e.g. device, build); free text up to 200 characters          |
| `Environment`    | Target environment (free text up to 200 characters)                       |
| `Release`        | Optional linked release                                                   |
| `Assigned To`    | Single session owner                                                      |
| `Estimate (min)` | Planned duration in minutes                                               |
| `Tags`           | Up to 50 tags                                                             |
| `Linked issues`  | Session-level external issue references                                   |
| `Attachments`    | Session-level files (up to 20)                                            |

<img src="https://testdinostr.blob.core.windows.net/docs/docs/manual-testing/manual-testing-sessions-create-dialog.webp" alt="Create Session dialog showing session fields, mission, type, state, environment, release, assignee, estimate, issues, tags, and attachments" style={{ maxWidth: "100%" }} />

<Callout icon="circle-info" color="#3B82F6">
  **Note**

  The `Release` field is optional. A session without a release appears in the **No release** group on the list.
</Callout>

## Session Detail

The Session Detail page is where teams record and manage findings during exploratory testing. It includes the mission, finding log, activity details, and a session summary panel.

<img src="https://testdinostr.blob.core.windows.net/docs/docs/manual-testing/manual-testing-sessions-detail.webp" alt="Session detail page showing session header, mission, findings, logs, and summary panel" />

### Mission and Findings

The main panel displays the session mission, `Add Finding` editor, and the finding log. Findings are shown in chronological order and can be filtered by status.

### Summary Panel

The `Summary` panel provides an overview of the session, including current state, created and closed time, creator, estimated and elapsed time, linked release, finding counts by status, and contributors who recorded findings.

## Findings

A finding is an individual observation recorded during a session. Each finding includes its own status, comment, elapsed time, attachments, and linked issues. Comments support rich text and inline images.

Findings use four default statuses: `passed`, `failed`, `blocked`, and `issue_found`. These statuses can be customized in **<Icon icon="gear" /> Test Case Settings → `Sessions → Result Status`**.

Issues linked to a finding are separate from session-level linked issues. Use finding-level links for specific observations and session-level links for issues affecting the entire session.

## Closing A Session

Closing a session is permanent. Use **Close** in the session detail header. After close, the session stays viewable but new findings, status changes, and field edits are blocked.

## Session Settings

Session-related project settings are managed via **<Icon icon="gear" /> Test Case Settings → `Sessions`** in the header.

| Setting          | Default Values                                           |
| :--------------- | :------------------------------------------------------- |
| `Session Status` | `New`, `In Progress`, `Under Review`, `Done`, `Rejected` |
| `Session Type`   | `Exploratory`, `Regression`, `Feature Test`              |
| `Result Status`  | `passed`, `failed`, `blocked`, `issue_found`             |

<img src="https://testdinostr.blob.core.windows.net/docs/docs/manual-testing/manual-testing-sessions-settings.webp" alt="Settings page showing Sessions tab with session status, type, and result status options" />

<CardGroup cols={2}>
  <Card title="Manual Runs" icon="play" href="/test-management/manual-testing/manual-runs">
    Use runs for structured manual case execution
  </Card>

  <Card title="Releases" icon="flag" href="/test-management/manual-testing/releases">
    Group sessions into releases and sub-releases
  </Card>
</CardGroup>