> ## 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. 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. Exploratory sessions start on the **Pro** plan. Pro allows 5 sessions per project, Team allows 50, and Enterprise is custom. Deleting a session frees a slot. The Free plan does not include sessions. See [Pricing](/pricing#plan-limits-at-a-glance). Sessions list showing search, options, active and closed tabs, and session rows grouped by release ## Create Or Edit Session Click **Create Session** to open the session form. 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 10,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 | | `Configuration` | The environment or configuration to test against, for example `Chrome / macOS` (up to 200 characters) | | `Release` | Optional linked release | | `Assigned To` | Single session owner | | `Estimate (min)` | Planned duration in minutes | | `Tags` | Up to 10 tags; pick existing ones or type a new one | | `Linked issues` | Session-level Jira or Linear issues, by key or URL; same field as on runs, see [Link Work Items](/test-management/manual-testing/manual-runs#link-work-items) | | `Attachments` | Session-level files (up to 20) | Create Session dialog showing session fields, mission, type, state, environment, release, assignee, estimate, issues, tags, and attachments **Note** The `Release` field is optional. A session without a release appears in the **No release** group on the list. ## 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. 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. The **Finding Logs** list shows the newest finding first. Filter it by contributor, status, or whether a finding has linked issues, attachments, or elapsed time. ### Summary Panel The summary panel shows the finding count and status mix, linked issues and attachments, owner, created and ended time, time estimate, release, and contributors. The session state is the badge in the header. ## 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 4 default statuses: `passed`, `failed`, `blocked`, and `issue_found`. These statuses can be customized in ** Test Case Settings → `Test Execution → Sessions → Session 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. In the finding composer, the **Issues** button opens the same Jira / Linear field used on runs. ## Closing A Session Closing a session is permanent. Click **Close Session** in the session detail header and confirm. 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 ** Test Case Settings → `Test Execution → 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` | Settings page showing Sessions tab with session status, type, and result status options Use runs for structured case by case validation Group sessions into releases and sub-releases This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.