Logging Results

The session log is where you capture what you find during a live exploration. Post quick notes and findings from the composer, or open the Result logger for full status + evidence. Every entry is timestamped, attributed, and preserved in the merged timeline.

Log entry types

Step by step (live session)

1. Open an exploration and click Start.
2. In the Session log, write in the composer at the bottom and click Note for a freeform observation or Finding for a defect or concern. ⌘/Ctrl+Enter logs a finding directly.
3. For a classified result, click Result to open the result logger.
4. Find and pick the test case the result is about — the modal opens on a case search and there is no Record button until you have chosen one.
5. Choose a status, add a comment if you want, and click Record result. The footer confirms what you are about to write, e.g. Records against C-214 at the current minute mark.
6. The entry appears immediately in the timeline (optimistic save).

Logging is only available while the session is Live (or after Resume on a debriefed session). Planned and read-only debriefed states disable the composer.

A result needs a test case; a note or finding does not. Notes and findings are free-form and belong to the exploration alone. A result is always recorded against a case from the test case repository — that is what lets exploratory work feed the same coverage and status data as a structured run. If you want to capture something with no case behind it, log it as a finding.

The notes editor

The rich-text editor supports: bold, italic, underline, strikethrough, headings, bullet and numbered lists, code blocks, blockquotes, links, and inline images. Use these tools to write clear, structured observations.

The composer is only active while the session is Live. It is disabled in the Planned state (start the session first) and in the read-only Debriefed state (Resume the session to log again).

Choosing a result status

The Result Type dropdown shows all statuses that are scoped for explorations. The “Untested” status is excluded since every logged result represents an active observation.

Statuses are configurable. Status names, icons, and colours are managed in Statuses. Which statuses appear in the dropdown is controlled by scope availability — see Scope Availability.

Uploading images

1. Drag an image file into the editor area, or paste from your clipboard.
2. The image uploads in the background and a preview appears inline in the editor.
3. Post the entry with Note or Finding to commit it. There is no separate Add button.

Post before navigating away. Images uploaded into an unposted composer draft are stored temporarily. If you leave the page without posting the note or finding, those draft uploads may be discarded. An upload that is never posted is permanently deleted 48 hours after it was uploaded; anything already posted is unaffected.

External issues

You cannot link an issue to an exploration result. Per-result issue linking, the count badge on the result card, and the sidebar Issues card were all removed. The runner’s right rail now holds four cards — Time box, Details, Results, and Findings — and none of them links issues.

Link issues from a test case or a test run instead. Links created against exploration results before the change still exist and remain visible in the project’s issues dashboard; they simply cannot be created or removed from an exploration any more. See External References.

Filtering the log

Use the filter chips above the timeline (All / Notes / Findings / Results) to focus on one entry type. Count badges show how many entries exist in each category.

Result history

Every result entry is preserved permanently in reverse-chronological order. Results are never overwritten or deleted — each entry is a standalone record. This provides a complete audit trail of what was discovered, when, by whom, and what status was assigned.

Exploration results vs test run results