exploratory-testing

Guide structured exploratory testing sessions with charters, heuristics, and debrief templates.

64|12|Updated Mar 23, 2026
One-click install
npx skills add https://github.com/petrkindlmann/qa-skills --skill exploratory-testing-petrkindlmann
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: exploratory-testing
Source: https://github.com/petrkindlmann/qa-skills/tree/main/skills/exploratory-testing
Command: npx skills add https://github.com/petrkindlmann/qa-skills --skill exploratory-testing-petrkindlmann

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Structured exploratory testing provides a repeatable framework to discover defects that automated tests may miss, through charter-based sessions, systematic note-taking, and post-session debriefs.

Core Features & Use Cases

  • Session-Based Test Management (SBTM) with charter templates and structured logging.
  • Heuristics like HICCUPS and FEW HICCUPS to guide bug discovery and domain exploration.
  • Conversion of session findings into automated tests to prevent regression.

Quick Start

Write a charter for a target area, run a 45-90 minute exploratory session, and capture observations and follow-up actions using the templates.

Frequently Asked Questions about exploratory-testing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is session-based test management and how does it structure exploratory testing?▼

Session-based test management structures exploratory testing by defining target areas with charter templates and capturing observations through structured session logs, ensuring systematic defect discovery.

How do I use HICCUPS and FEW HICCUPS heuristics to guide bug discovery?▼

HICCUPS and FEW HICCUPS heuristics guide bug discovery by providing structured mnemonic frameworks to systematically evaluate application domains and uncover defects that automated tests miss.

How do I convert exploratory testing session findings into automated tests?▼

You convert exploratory testing findings into automated tests by documenting observations and follow-up actions during the debrief phase, generating documentation for automation handoff to prevent future regressions.

Does structured exploratory testing work for both web and mobile app testing?▼

Structured exploratory testing supports both web and mobile apps by applying charter-based workflows, session logs, and debrief templates across new features, regression work, and risk-based testing scenarios.

What is the best way to document an exploratory testing session?▼

The best way to document exploratory testing is by using SBTM session logs and debrief templates to record observations, charter progress, and follow-up actions immediately after a 45-90 minute testing session.