Skip to main content
A session is used for exploratory testing in TestDino. Each session includes a mission, current state, optional milestone 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.
Sessions live on the Test Execution page, under the Runs & Sessions tab, in one list with runs. Pick Sessions above the list to show sessions only. See Runs and sessions list.

Create Or Edit Session

Click Create, then Create session, to open the session form. To edit an existing session, open it from the list and click Edit in the header. The form shows Name, Configuration, State, Mission, and Linked Issues first. The other fields sit under More options at the bottom, which starts closed. When you edit a session that already has any of them set, including saved attachments, More options opens by itself.
NoteThe Milestone field is optional. A session without a milestone appears in the No milestone 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, milestone, 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. Settings page showing Sessions tab with session status, type, and result status options

Runs

Use runs for structured case by case validation

Milestones

Group sessions into milestones and sub-milestones
Last modified on November 11, 2026