Explorations
Explorations are freeform testing sessions where testers investigate the product without a predefined script. Instead of executing pre-written test cases step by step, you create an exploration, then log your discoveries as you go — each entry combines rich-text notes with a result status. Explorations capture the unscripted, curiosity-driven side of testing.
Think of it as a field journal
Test runs are structured exams with marked answer sheets. Explorations are field journals — you head out into the product with a purpose (the exploration title and metadata), and you write down what you find as you go. Each journal entry (a result) records what you observed (rich-text notes), what you concluded (a status like Passed or Failed), and any evidence you collected (attachments and linked issues). The journal tracks who wrote it, when entries were added, and how the session went overall.
How explorations differ from test runs
| Aspect | Explorations | Test Runs |
|---|---|---|
| Structure | Freeform — no predefined test cases or steps | Structured — execute pre-selected test cases with defined steps |
| Results | Logged directly from the detail page as notes + status | Recorded per test case via the Add Result modal |
| Test cases | Not involved — results belong to the exploration itself | Selected from the repository at creation time |
| Assignment | Single assignee on the exploration | Per-case assignment within the run |
| Template fields | Set at creation, displayed read-only on detail page | Attached to test cases and recorded with each result |
| Primary use case | Ad-hoc discovery, bug hunts, new feature investigation | Regression, acceptance, and scripted test execution |
The list page layout
The EXPLORATIONS tab inside a project shows three summary cards at the top (total explorations, latest result distribution, recently closed), an Active/Closed lifecycle toggle, a search bar, filter controls, and a data table listing explorations. See Browsing & Filtering for full detail.
How the pieces fit together
| Admin entity | How it is used in Explorations |
|---|---|
| Cycles | Group explorations into sprints, releases, or iterations. The Cycle column and filter organise the table. See Cycles. |
| Lifecycle States | Track an exploration's progress — e.g. Planned, In Progress, Closed. The lifecycle toggle switches Active and Closed views. See Lifecycles. |
| Environments | Record the platform/browser combination being explored. See Environments. |
| Statuses | Set the outcome of each logged result — Passed, Failed, Blocked, etc. Statuses power the Latest Results donut chart and the activity grid. See Statuses. |
| Tags | Label explorations for filtering and categorisation. See Tags. |
| Templates | Control which custom fields appear on the exploration. See Exploration Templates. |
| Fields | Define custom metadata fields attached to explorations via templates. See Exploration Fields. |
| External References | Link result entries to Jira, GitHub, Azure DevOps, and other issue trackers. See External References. |
Getting started
- Open a project and click the EXPLORATIONS tab.
- Browse existing explorations or click New Exploration.
- Fill in the exploration name, select a template, cycle, environment, and any custom fields.
- Open an exploration and use the Session Log to record findings — write notes, choose a result status, and click Add.
- Track progress on the detail page — the summary shows total results, pass rate, and an activity grid.
- Close the exploration when the session is complete.
Permissions
| Permission | What it allows |
|---|---|
| View explorations | See the EXPLORATIONS tab, browse the list, and open detail pages. |
| Create explorations | Create new explorations. |
| Edit explorations | Edit exploration metadata, custom fields, and close explorations. |
| Delete explorations | Permanently delete an exploration and all its results. |
| Add exploration results | Log result entries (notes + status) on the detail page. |
| View external references | See linked issues on result entries. |
| Manage external references | Link and unlink external issues on result entries. |
All action permissions require View. A user cannot create, edit, or delete explorations unless they can also view them.
Common permission combinations
| Goal | Permissions needed |
|---|---|
| Browse explorations and view results (read-only) | View explorations |
| Create and configure explorations, but not log results | View explorations + Create explorations |
| Log results on existing explorations | View explorations + Add exploration results |
| Full exploration management | View + Create + Edit + Add results + Delete explorations |
Browsing & Filtering
Search, filter, and monitor explorations with summary cards, lifecycle tabs, and a filterable data table.
Creating an Exploration
Set up a new exploration with metadata, templates, custom fields, and time estimates.
Exploration Detail
Navigate the detail page — template fields, the session log, results timeline, and metadata sidebar.
Logging Results
Write rich-text notes, pick a result status, upload images, and link external issues.
Managing Explorations
Edit, close, reopen, and delete explorations.