Skip to main content

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.

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
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. 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.
FieldDescription
NameRequired session name (up to 500 characters)
MissionSession charter or goal (up to 50,000 characters, supports inline images)
TypeSession type from project settings
StateWorkflow state from project settings; defaults to New
ConfigurationSetup label (e.g. device, build); free text up to 200 characters
EnvironmentTarget environment (free text up to 200 characters)
ReleaseOptional linked release
Assigned ToSingle session owner
Estimate (min)Planned duration in minutes
TagsUp to 50 tags
Linked issuesSession-level external issue references
AttachmentsSession-level files (up to 20)
Create Session dialog showing session fields, mission, type, state, environment, release, assignee, estimate, issues, tags, and attachments
NoteThe 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. 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 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 Test Case Settings → Sessions in the header.
SettingDefault Values
Session StatusNew, In Progress, Under Review, Done, Rejected
Session TypeExploratory, Regression, Feature Test
Result Statuspassed, failed, blocked, issue_found
Settings page showing Sessions tab with session status, type, and result status options

Manual Runs

Use runs for structured manual case execution

Releases

Group sessions into releases and sub-releases