DocsExploratory

Exploratory

Exploratory is Testably's tool for exploratory testing. Start a session, freely explore your application, and record observations as you go โ€” notes, bugs, and test steps. Later, convert your findings into formal test cases.

Starting an Exploratory Session

Navigate to the Sessions tab in your project and click "+ New Session". The six-step setup flow gets your session ready in under a minute.

  1. 1

    Name your session

    Use a descriptive name that captures the scope (e.g. "Checkout Flow Exploration", "Mobile Navigation Edge Cases").

  2. 2

    Define the mission (Charter)

    Write a brief charter describing what to explore. E.g. "Explore the checkout flow for edge cases: empty cart, expired coupon, address validation."

  3. 3

    Set time estimate (optional)

    Time-box the session (30 min, 1 hour, etc.). A live timer tracks how long the session has been active.

  4. 4

    Assign participants (optional)

    Add one or more team members. Multiple participants can contribute observations to the same session.

  5. 5

    Link to milestone (optional)

    Associate the session with a milestone to track exploratory coverage alongside formal test runs.

  6. 6

    Start exploring

    Click "Create". The session begins immediately and the live timer starts. You can pause and resume as needed.

Recording Observations

Once the session is active, record observations in real-time. Each entry is automatically timestamped and added to the chronological timeline. Testably supports four entry types:

TypeIconPurpose
Step๐Ÿงช PurpleRecord a test step or observed behavior that works correctly. Use for documenting what you tested.
Bug๐Ÿ› RedRecord a defect or unexpected behavior found during exploration.
Blockedโ›” AmberRecord a scenario you could not test due to an environment or dependency issue.
Note๐Ÿ“ IndigoGeneral observations, improvement ideas, or questions to investigate later.

Adding an Entry

  1. 1

    Select entry type

    Choose from Step, Bug, Blocked, or Note using the bottom toolbar.

  2. 2

    Write your observation

    Use the rich text editor (powered by Quill) to describe what you found. Supports bold, italic, lists, and code blocks.

  3. 3

    Add attachments (optional)

    Attach screenshots or files to provide visual evidence alongside your observation.

  4. 4

    Submit

    Press Enter or click Submit. The entry appears timestamped in the chronological timeline.

Rich Text Editor

The observation editor is powered by Quill and supports rich formatting: bold, italic, ordered and unordered lists, code blocks, and more. Click the edit icon on any submitted entry to modify its content or change its type.

Timeline View

All observations appear in a chronological timeline. Each entry displays the following information at a glance:

  • Type indicator: Color-coded icon (purple=Step, red=Bug, amber=Blocked, indigo=Note).
  • Content: Observation text with full rich-text formatting preserved.
  • Timestamp: Exact time the entry was recorded during the session.
  • Attachments: Inline screenshots and files attached to the entry.
  • Issues: Linked Jira issues, if any were added to the entry.

Live Timer

The live timer at the top of the session detail shows elapsed time in HH:MM:SS format. The timer pauses automatically when the session is paused, so duration accurately reflects active testing time.

Session Metadata

The right sidebar of the session detail page shows all metadata and controls for managing the session's state.

Status

Active โ€” timer running
Paused โ€” timer stopped
Completed โ€” session ended

Tracked Fields

  • Mission / Charter
  • Assignees (participants)
  • Time Box (estimated duration)
  • Duration (actual elapsed time)
  • Linked Milestone
  • Tags

Session Controls

  • Pause / Resume: Temporarily stop the timer during breaks without ending the session.
  • Complete: End the session permanently. Timer stops and status changes to Completed.
  • Edit: Modify the session name, mission, assignees, or linked milestone after creation.

Converting to Test Cases

The most powerful feature of Exploratory is the ability to convert exploratory findings directly into formal, structured test cases โ€” either manually or with AI assistance.

Manual Conversion

Click "Convert to Test Case" on any individual entry in the timeline. Testably creates a new test case with the entry content pre-populated as steps. You can then add an expected result, set priority, and assign a folder before saving.

AI-Assisted Conversion (Professional+)

Use the AI Generate feature with Session-based mode. Select a completed session and the AI analyzes all timeline entries โ€” steps, bugs, notes, and blocked items โ€” to generate a set of structured test cases with steps, expected results, and suggested priorities.

Pro Tip โ€” Fastest Path to Coverage

Run a 30-minute exploratory session on a new feature, record all observations, then use AI Generate to convert the session into test cases. This is the fastest way to build comprehensive test coverage for a new feature โ€” often generating 10โ€“20 structured test cases from a single session.

Next Steps

Learn how to manage the test cases you generate from sessions, or configure the Jira integration to link issues from bug entries.

Product

Use Cases

Compare

Resources

Legal

ยฉ 2026 Testably. All rights reserved.

We use cookies to improve your experience.

Strictly necessary cookies are required for login and security. Optional cookies help us analyze usage and improve our service. Learn more โ†’