planning-exploratory-testing

Plans and runs session-based exploratory testing with charters, timeboxes, heuristics, and debriefs.

113|17|Updated Oct 5, 2025
One-click install
npx skills add https://github.com/jaktestowac/awesome-copilot-for-testers --skill planning-exploratory-testing-jaktestowac
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: planning-exploratory-testing
Source: https://github.com/jaktestowac/awesome-copilot-for-testers/tree/main/plugins/planning-exploratory-testing/skills/planning-exploratory-testing
Command: npx skills add https://github.com/jaktestowac/awesome-copilot-for-testers --skill planning-exploratory-testing-jaktestowac

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Scripted test cases cannot answer "what do we not know about this yet" when requirements are moving, regression suites pass while users report problems, or a release needs a risk sweep with no time to write cases. This Skill structures exploratory testing so it produces accountable, reviewable coverage instead of unscripted clicking. ## Core Features & Use Cases - Charter Writing and Prioritization: Creates mission-style charters (target, resources, discovery goal) and sorts them into must-run, run-if-time, and backlog buckets based on risk signals. - Heuristic-Guided Sessions: Applies SFDIPOT, CRUSSPIC STMPL, tours, and input/state/data heuristics during strictly timeboxed 45/60/90-minute sessions with evidence-capturing notes. - Debrief and Output Routing: Runs PROOF debriefs and routes findings to bug reports, automation candidates, requirement questions, or follow-up charters, then aggregates a coverage report for release decisions. - Use Case: A payment flow changed before release and scripted tests all pass. Use this Skill to write risk-prioritized charters, run timeboxed sessions with named heuristics, capture evidence-backed notes, and deliver a coverage report stating what was and was not tested. ## Quick Start Plan and run a 60-minute exploratory testing session on the checkout payment flow, focusing on the risk that saved cards behave incorrectly after a settings change.

Frequently Asked Questions about planning-exploratory-testing

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

FAQPage Schema
How do I write a good exploratory testing charter?▼

A charter states a mission in three clauses: Explore a target, With specific resources like a role or data condition, To discover a concrete risk or question. It never contains numbered steps or expected results, and each charter covers exactly one area.

What is session-based exploratory testing?▼

Session-based exploratory testing is simultaneous learning, test design, and execution made accountable by a charter, a strict timebox of 45 to 90 minutes, and notes written during the session. It ends with a debrief that routes findings to bugs, automation candidates, or follow-up charters.

When should I use exploratory testing instead of scripted test cases?▼

Use it when requirements are still moving, scripted regression passes while users report problems, a release needs a risk sweep with limited time, or an area has no documentation or coverage. Scripted cases suit stable, well-specified behavior; exploration suits unknowns.

How do I report exploratory testing coverage to stakeholders?▼

Report charters planned versus run, total session time, the time split across design, investigation, and setup, and confidence per area. Always state which areas were deliberately not covered and why, since that is what makes the report usable in a release decision.

Why is bug count a bad metric for exploratory testing sessions?▼

Bug count measures both the session's luck and the code's state without separating them, rewarding shallow sweeps over deep investigation. A session that finds no bugs but maps an area and answers its charter question is a successful session.