exploratory-testing
/exploratory-testing
Independent black-box exploratory testing and user acceptance (UAT): charters, tours, oracles, bug reports, sign-off with evidence. Use for acceptance testing, manual verification of the real app, bug triage, and acting as the customer.
- Author
- swap-cameroon ↗
- Repository
- kuro-antigravity-config ↗
- Licence
- MIT
- Last repository change
- 11.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 11.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Independent black-box exploratory testing and user acceptance (UAT): charters, tours, oracles, bug reports, sign-off with evidence. Use for acceptance testing, manual verification of the real app, bug triage, and acting as the customer.
Original author description
Independent black-box exploratory testing and user acceptance (UAT): charters, tours, oracles, bug reports, sign-off with evidence. Use for acceptance testing, manual verification of the real app, bug triage, and acting as the customer.
How it works
- Independence rules (UAT mode)
- Session method
- Bug report (one file per bug: BUG-NNN.md)
- UAT sign-off (UATREPORT.md)
- After a fix
- Tone
SKILL.md preview
--- name: exploratory-testing description: "Independent black-box exploratory testing and user acceptance (UAT): charters, tours, oracles, bug reports, sign-off with evidence. Use for acceptance testing, manual verification of the real app, bug triage, and acting as the customer." license: MIT metadata: version: "1.0.0" --- # Exploratory testing and UAT (the independent tester) The tester is the customer's proxy. **Independence is the whole point**: builders cannot certify their own work, and a test that only mirrors the implementation cannot find what the implementation got wrong. Automation of the same journeys lives in `e2e-testing`. ## Independence rules (UAT mode) - **Black box**: use only the running app, the PRD and its acceptance criteria. Do not read the source or the builders' tests before the first full pass; do not ask builders for hints. - **Do not fix** what you find. Report it. A tester who fixes loses independence and hides the defect from the process. - **Real conditions**: real browser, the documented start command, a fresh data state, the accounts the documentation gives. If the documented way does not work, that is the first bug. - Evidence or it did not happen: screenshots, exact inputs, console/network errors, timestamps. ## Session method 1. **Charter** (60-90 min, one per session): `Explore <area> with <data/accounts/tools> to discover <risk or information>`. 2. **Journeys first**: execute every PRD journey as each persona/role, by hand, end to end. Record pass/fail per acceptance id. 3. **Tours** to go beyond the happy path: *money* (what the product is for), *landmark* (every main screen), *back-alley* (rarely used features), *saboteur* (invalid, extreme, malicious input; double submit; back button; two tabs/two users at once), *impatient* (fast clicks, interrupts), *after-hours* (time/timezone/expiry), *rotate roles* (can this role see or do what it should not?). 4. **Heuristics**: SFDIPOT (Structure, Function, Data, Interfaces, Platform, Operations, Time); boundaries and equivalence classes; CRUD completeness; state transitions; permissions matrix. 5. **Oracles** (how you know it is wrong): PRD, consistency with itself, similar products, user expectations, standards, common sense, and history (did it work before?). 6. Take notes as you go: what was tried, what was seen, questions, risks. ## Bug report (one file per bug: `BUG-NNN.md`) `Title (symptom, not guess) - Severity - Frequency - Environment (URL, commit, browser) - Steps to reproduce (numbered, exact data) - Expected - Actual - Evidence - Notes`. Describe **what you observed**, not the suspected cause. Severity: **S1** blocks a primary journey or loses/corrupts data or breaks security; **S2** a main feature wrong with a workaround; **S3** minor/cosmetic; **S4** suggestion. Any S1 fails the acceptance gate. ## UAT sign-off (`UAT_REPORT.md`) | Journey / AC id | Persona | Result | Evidence | Bugs | | :-- | :-- | :-- | :-- | :-- | Then: sessions run, areas **not** tested and why, open bugs by severity, a clear **GO / NO-GO** with reasons. GO requires: every primary journey passed by hand in the real UI, no open S1, S2s accepted explicitly by the product owner. ## After a fix Re-test the reproduction exactly, then run a short regression tour around the changed area, and confirm a regression test exists (`e2e-testing`). Verify the fix in the real UI, not by reading the diff. ## Tone Factual and specific. "I clicked 'Save' with an empty title and the page reloaded with no message" beats "the form is broken". Never blame; never claim coverage you did not exercise.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · swap-cameroon/kuro-antigravity-config | 90 | MIT |
| mahdavipanah/exploratory-testing-skill | 100 | MIT |
| mattwynne/yaks | 100 | MIT |
| testland/qa | 100 | MIT |
| qa-aman/claude-skills | 100 | MIT |
| bdfinst/agentic-dev-team | 100 | MIT |
| petrkindlmann/qa-skills | 100 | MIT |
| Amey-Thakur/AI-SKILLS | 90 | MIT |
| upex-galaxy/agentic-qa-boilerplate | 87 | MIT |
Database snapshot: 13.11.2026 · package version 893992600297 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100planning-exploratory-testing
Runs session-based exploratory testing: writes charters, timeboxes sessions, applies coverage heuristics and tours, captures notes as evidence, debriefs, and converts findings into bug reports and automation candidates. Use when a feature needs testing before requirements… - 90exploratory
Create exploratory testing charters and session ideas for a feature — where to look for bugs, what to try, tours and heuristics. Use when the user wants exploratory testing ideas, a testing tour, or "what should I test" guidance for a feature. - 100exploratory-charter
Create focused exploratory testing charters (\"Explore <target> with <resources> to discover <information>\") using the SFDIPOT product elements and Whittaker's testing tours, with time-boxes and a session sheet. Use when planning exploratory testing of a feature, a release or a… - 100bugmagnet
Lightweight bug discovery and test coverage analysis for a code module. Use when the user asks to find bugs, analyze test coverage, write edge case tests, or do exploratory testing on a file. Triggers on "bugmagnet", "find bugs in", "test coverage gaps", "edge cases for", or… - 90qa-methodology
Design and apply QA methodology for software teams: test strategy, regression testing, CI failure triage, test automation, quality gates and metrics, risk-based testing, exploratory testing, test design techniques, AI code quality gates (independent verification, artifact… - 98exploratory-heuristics
Exploratory testing toolkit — session-based test management (charters, time boxes, session sheets, debriefs), test heuristics (SFDPOT, FEW HICCUPPS consistency oracles, CRUD, goldilocks, interruptions), tours (money, landmark, back-alley, saboteur, all-nighter), a cheat sheet of…