Exploratory Testing Advanced

Identify quality risks through structured exploratory testing with SBTM and heuristics.

6|3|Updated Dec 3, 2025
One-click install
npx skills add https://github.com/pacphi/ampel --skill exploratory-testing-advanced-pacphi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill:  Exploratory Testing Advanced
Source: https://github.com/pacphi/ampel/tree/main/.claude/skills/exploratory-testing-advanced
Command: npx skills add https://github.com/pacphi/ampel --skill exploratory-testing-advanced-pacphi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Advanced exploratory testing using SBTM, RST heuristics, and test tours to reveal unknown quality risks.

Core Features & Use Cases

  • Charter-based exploration: Define mission, scope, and time-box.
  • RST heuristics: Apply Structure, Function, Data, Interfaces, Platform, Operations, Time and FEW HICCUPPS.
  • Test tours: Navigate areas of risk and complexity.

Quick Start

Instruction: "Plan a 60-minute exploration session targeting critical business flows."

Frequently Asked Questions about Exploratory Testing Advanced

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

FAQPage Schema
How do I conduct exploratory testing systematically to find quality risks?

Exploratory testing uses Session-Based Test Management (SBTM) with time-boxed charters (45-90 minutes) to systematically explore software. Apply heuristics like SFDIPOT and FEW HICCUPPS alongside test tours to navigate risk areas, document findings in real time, and surface actionable quality risks across web, mobile, and enterprise systems.

What are RST heuristics and how do they guide exploratory testing?

RST heuristics—Structure, Function, Data, Interfaces, Platform, Operations, and Time—combined with FEW HICCUPPS, provide systematic lenses for exploration. They direct your test tours toward high-risk areas and ensure coverage of critical business flows, enabling structured discovery of unknown defects during charter-based sessions.

How do I plan and execute a time-boxed exploration session?

Define a charter that specifies mission, scope, and time-box (typically 45-90 minutes). Apply test tours to navigate software areas by risk and complexity, systematically apply heuristics to reveal gaps, document evidence in real time, and conduct debriefing to extract and share findings for team memory.

Can I use exploratory testing for bug investigations and risk discovery?

Yes. Exploratory testing with SBTM is applied during planning of exploration sessions, bug investigations, and risk discovery across web, mobile, and enterprise systems. Charter-based exploration with test tours and heuristic application enables systematic investigation of suspected problem areas.

When should I use test tours versus traditional exploratory testing?

Test tours provide a structured navigation method through software focused on high-risk and complex areas. They work within SBTM charters to guide exploration systematically. Use test tours when you need repeatable, documented exploration paths that can be debriefed and shared across teams for consistent risk discovery.

What's the difference between SBTM and ad-hoc exploratory testing?

Session-Based Test Management (SBTM) structures exploration through time-boxed charters with defined mission and scope, systematic heuristic application, real-time documentation, and debriefing. This differs from ad-hoc testing by providing repeatable methodology, evidence trails, and team memory for consistent quality risk identification.