← ClaudeAtlas

exploratory-testinglisted

Plans and records session-based exploratory testing — time-boxed charters aimed at what scripted cases cannot cover, with session notes, findings and coverage of the areas explored. Use this skill when a feature is too new or too uncertain for scripted cases, after scripted execution finds nothing, when the user asks how to find bugs the test cases missed, or when testing a third-party integration or a legacy area with no requirements. Also use it to turn a vague "have a look at this" request into something with a scope and a record.
YevheniiaQA/qa-agent-toolkit · ★ 0 · Testing & QA · score 72
Install: claude install-skill YevheniiaQA/qa-agent-toolkit
# Exploratory Testing Scripted cases verify what somebody thought of. Everything else is found by somebody looking — and on most products, the most serious defects are in that second category. The failure mode of exploratory testing is that it leaves no record, so nobody can say what was covered and it cannot be repeated. Session-based testing fixes that without turning it back into a script. ## Charters A charter is a mission, not a procedure. Time-boxed, with an area and a risk in mind, and deliberately open about method. ```markdown ## CH-03 — Confluence connection under adverse conditions **Explore** the connect flow **With** network interruption, slow responses, and concurrent sessions **To discover** whether partial connections leave recoverable state **Time-box** 60 minutes · **Risk** medium — partial state is invisible to the user ``` Good charters come from where the scripted cases are weakest: - **Where requirements were silent.** Every open question is a charter. - **Where the design showed states nobody specified** — empty, loading, error. - **Interruption and concurrency.** Scripted cases almost never cover a second tab, a back button mid-flow, or a session expiring at the wrong moment. - **Data that is unusual rather than invalid.** Very long names, right-to-left text, emoji, a leading zero, a value that looks numeric but is not. - **Boundaries between systems.** Integrations are where ownership is unclear and nobody tested both sides. - **Areas whe