> ## Documentation Index > Fetch the complete documentation index at: https://docs.atconseil.info/llms.txt > Use this file to discover all available pages before exploring further. # Sessions hub > Find every exploratory session of a project in one place: filter by scope, read each session's outcome, export one session or the whole scope as a PDF. A session archived on a user story is easy to find — as long as you remember which story. The **Explore** tab in the TestPulse hub answers the other question: *what has actually been explored on this project?* ## Every session of the project, grouped by work item The tab lists **all exploratory sessions of the project**, grouped by the work item they were run on, most recent activity first. Each group shows its work item, its **type**, the number of sessions it carries, and the date of its last activity — then expands into **one row per session**. That row is the unit that matters: **status**, charter, tester, duration, counts of notes, captures, files and bugs, and a link — to the archived Task once the session is closed, or to the work item itself while it is still running, where the Explore tab picks it back up. For an active session, that link tells you whether it is **yours**: your own shows your name and offers to resume it, a colleague's only opens the work item. Azure DevOps restores a session solely to the account that started it, so promising more would be promising something that cannot happen. A story explored three times shows three distinct rows, not a pile of merged badges. ## The verdict, when there is one Since v2.60.0 a closed session can carry a **verdict** — Passed, Failed or Blocked — chosen by the tester at closure. It renders as its own badge **beside** the status badge, never in its place: the status says where the session stands in its life, the verdict says how it went. The **Verdict** filter narrows the list to one value, or to sessions carrying **none** — a distinct answer from "all", since the verdict is optional and skipping it is legitimate. A verdict is **never counted anywhere**. A session marked Failed increments no failure indicator, in no report and in no quality gate — it is a tester's judgement on a session, not a test result. The same value is written as a tag on the tracking Task so you can query it from Azure DevOps; if someone edits that tag by hand, the session document is what TestPulse reads. ## Read the status at a glance Each session carries a **status with its own colour and its own icon** — complete, active, interrupted, abandoned, or incomplete. Colour alone is never the signal, so the list stays readable in dark mode and for colour-blind readers. **Incomplete** deserves a word: it marks a session whose close didn't finish. Nothing is lost — the archived Task holds the truth — so the row links straight to it. ## Narrow the scope Filters cover **area path, iteration path, campaign tag, tester, period and verdict**, plus a switch to include archived sessions. Area and iteration filters **match sub-paths**: pick a root and you get everything underneath it, the way Azure DevOps itself treats these paths. Each filter option carries **its own result count**, so you can judge how selective a choice is before making it. The **Tester** filter pre-sets itself to you when the hub opens, with a visible **"Filtered to my sessions"** chip you can remove in one click. **Active sessions are exempt from it**: a session only gets a tracking Task — and with it a resolvable tester name — at closure, so filtering by tester would otherwise hide every session in progress, your own included. Every other filter still applies to them. This filter reduces noise; it grants no confidentiality. Sessions are stored at **project scope** and readable by anyone with access to the project, regardless of Azure DevOps teams. ## Archived, never deleted Beyond a threshold, older sessions leave the default view — they are **archived for display only**. TestPulse **never deletes a session**: the switch brings them back, and the real total is always shown. ## Export one session, or the whole scope Any session holding at least one entry offers **Export session** — the same signed PDF you get from the work item form. A session with nothing recorded offers no button, because there would be nothing to report. **Export report** produces the **aggregated scope report**: cover page, summary, sessions by area and by iteration, a section per work item, and an appendix. Both exports open a dialog with a **pre-filled title** you can accept as-is or rewrite, and both follow the **branding you configured in Settings** — label, theme colour and cover logo. ## What the indicators say — and don't The tab shows **covered work items**, a **session count** and **interrupted sessions**. The session count matches the rows actually listed — incomplete sessions included — so you can verify it by counting them. A **"Discoveries"** tile used to sit here, summing the work items created from inside a session. It was retired in v2.57.2: a tester who logged the same findings straight into Azure DevOps by hand scored zero, so the number never measured what its name promised. There is deliberately **no total effort**: a session left open overnight produces a duration that is arithmetically exact and practically meaningless, and summing it would have made the figure untrustworthy. Per-session duration remains, next to its charter, where a human can judge it. Work items created by TestPulse to archive a session are **marked as such** and excluded from coverage — they are records, not subjects of exploration. Indicators to examine, never a verdict: you decide. ## Strictly read-only The tab **reads and exports**. It never writes to Azure DevOps — attaching a report to a work item stays on the work item form, where the session lives. ## Related Start a session from a user story. What the exported PDF contains. Annotate captures and raise work items. What stays in your tenant.