Back to the Playbook
Define & DesignDD-16
How to run exploratory testing
Explore adaptively within a bounded question; document what was actually exercised and what remains unknown.
Product statusAssisted workflowTeklens writes the charter, suggests variations and structures the findings; the exploration itself is hands-on work by people.
Input3 required inputsProduct version and exploration question · User goals, known risks and observation tools · Initiative focus and approved Product Brain guidance
SkillsPrepare or assess exploratory testing · Prepare task context · Review an artifact against agreed criteriaQA + Software Engineer Agent
OutcomeExploratory test charter and session evidence: goal, risk and scope, exploration ideas, actual paths and results, findings and proposed checks.Artifact: Exploratory test charter
Owner
QA
Human-led
Participants · Agents
EngineerProduct ManagerSoftware Engineer Agent
Trigger
A working product version raises an exploration question.
Required context
CodeProduct version and exploration questionProduct BrainUser goals, known risks and observation toolsProduct BrainInitiative focus and approved Product Brain guidance
Optional context
JiraKnown issuesFilesSession notes and recordings
Skills
Prepare or assess exploratory testingPrepare task contextReview an artifact against agreed criteria
Suggested conversation arc
- 1Define the exploration charterChoose the user goal, product version, risks and time boundary; clarify that this exploration supplements rather than replaces repeatable checks.Skills: Prepare task context
- 2Prepare risk-focused variationsSuggest realistic edge paths, state transitions and recovery scenarios from the charter. Treat them as probes, not a rigid proof of coverage.Skills: Prepare or assess exploratory testing
- 3Explore the actual productExercise scenarios, follow discoveries and capture the path, environment and observed results. Keep suspected causes separate from reproducible evidence.
- 4Review findings and repeatable checksPrioritise evidenced problems and propose bug reports or repeatable regression checks. Preserve unknowns rather than claiming the product is defect-free.Skills: Prepare or assess exploratory testing · Review an artifact against agreed criteria
Output
Exploratory test charter and session evidence: goal, risk and scope, exploration ideas, actual paths and results, findings and proposed checks.
Artifacts
Creates: Exploratory test charter
What good looks like
- Observed findings are distinguishable from suggested checks.
- Defects retain reproduction evidence.
- No completed-test claim without interaction evidence.
Quality gate
QA decides which findings become bug reports or regression checks.
Destination
JiraTeklens only
Usually next
People and agents work from the same Product Brain. The owner stays accountable. Assigned agents prepare and check. A named person approves at the gate.
Choose the path that matches your role.
Set the Product AI direction with us, or test the shared Product Brain on real work with Jira and code.