qualiow-exploratory-testing 1.0.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/LICENSE +21 -0
- package/README.md +214 -0
- package/data/domains/_default.yml +167 -0
- package/data/domains/ecommerce.yml +198 -0
- package/data/domains/fintech.yml +207 -0
- package/data/domains/marketing.yml +202 -0
- package/data/domains/saas.yml +206 -0
- package/data/knowledge/changelog.yml +75 -0
- package/data/knowledge/custom/.gitkeep +0 -0
- package/data/knowledge/learned-patterns.md +40 -0
- package/data/knowledge/manifest.yml +141 -0
- package/data/knowledge/releases/v0.1.0/entries/checklist-accessibility-wcag.yml +326 -0
- package/data/knowledge/releases/v0.1.0/entries/heuristic-few-hiccupps.yml +194 -0
- package/data/knowledge/releases/v0.1.0/entries/heuristic-goldilocks.yml +143 -0
- package/data/knowledge/releases/v0.1.0/entries/heuristic-rcrcrc.yml +207 -0
- package/data/knowledge/releases/v0.1.0/entries/heuristic-sfdipot.yml +171 -0
- package/data/knowledge/releases/v0.1.0/entries/heuristic-test-tours.yml +253 -0
- package/data/knowledge/releases/v0.1.0/entries/reference-exploratory-testing-types.yml +84 -0
- package/data/knowledge/releases/v0.1.0/entries/reference-heuristic-praxis.yml +95 -0
- package/data/knowledge/releases/v0.1.0/entries/technique-boundary-testing.yml +203 -0
- package/data/knowledge/releases/v0.1.0/entries/technique-business-logic-race-conditions.yml +146 -0
- package/data/knowledge/releases/v0.1.0/entries/technique-data-integrity-testing.yml +269 -0
- package/data/knowledge/releases/v0.1.0/entries/technique-error-guessing.yml +216 -0
- package/data/knowledge/releases/v0.1.0/entries/technique-risk-based-testing.yml +298 -0
- package/data/knowledge/releases/v0.1.0/release.yml +22 -0
- package/data/targets/_default.yml +11 -0
- package/data/targets/testers-ai.yml +14 -0
- package/data/templates/bug-report.md +178 -0
- package/data/templates/coverage-map.md +70 -0
- package/data/templates/session-charter.md +77 -0
- package/data/templates/session-report.md +112 -0
- package/dist/cli/index.d.ts +1 -0
- package/dist/cli/index.js +1757 -0
- package/dist/cli/index.js.map +1 -0
- package/dist/index.d.ts +899 -0
- package/dist/index.js +1133 -0
- package/dist/index.js.map +1 -0
- package/docs/GETTING-STARTED.md +265 -0
- package/package.json +70 -0
- package/skills/qa-explore/SKILL.md +70 -0
- package/skills/qa-explore/phases/00-setup.md +96 -0
- package/skills/qa-explore/phases/01-auth.md +34 -0
- package/skills/qa-explore/phases/02-charter.md +112 -0
- package/skills/qa-explore/phases/03-discovery.md +49 -0
- package/skills/qa-explore/phases/04-journeys.md +51 -0
- package/skills/qa-explore/phases/05-features.md +55 -0
- package/skills/qa-explore/phases/06-edge-cases.md +69 -0
- package/skills/qa-explore/phases/07-reporting.md +162 -0
- package/skills/qa-explore/references/context-integration.md +44 -0
- package/skills/qa-explore/references/security-rules.md +43 -0
- package/skills/qa-explore/references/session-rules.md +33 -0
- package/skills/qa-explore/references/severity-guide.md +14 -0
- package/skills/qa-explore-cleanup/SKILL.md +39 -0
- package/skills/qa-explore-feedback/SKILL.md +73 -0
- package/skills/qa-explore-quick/SKILL.md +80 -0
- package/skills/qa-explore-report/SKILL.md +62 -0
- package/skills/qa-gather/SKILL.md +198 -0
- package/skills/qa-knowledge-add/SKILL.md +91 -0
- package/skills/qa-knowledge-list/SKILL.md +54 -0
- package/skills/qa-target-setup/SKILL.md +106 -0
|
@@ -0,0 +1,171 @@
|
|
|
1
|
+
id: heuristic-sfdipot
|
|
2
|
+
version: "0.1.0"
|
|
3
|
+
type: heuristic
|
|
4
|
+
name: "SFDIPOT - Product Elements"
|
|
5
|
+
description: >
|
|
6
|
+
A mnemonic for the seven product elements that deserve exploration.
|
|
7
|
+
Use SFDIPOT to systematically generate test ideas by examining each
|
|
8
|
+
dimension of the product under test. It prevents tunnel vision by
|
|
9
|
+
ensuring you consider the product from multiple angles.
|
|
10
|
+
author: "James Bach"
|
|
11
|
+
source: "Rapid Software Testing"
|
|
12
|
+
tags: [exploration, what-to-test, systematic, rst]
|
|
13
|
+
domains: [all]
|
|
14
|
+
priority: high
|
|
15
|
+
added: "2026-03-28"
|
|
16
|
+
|
|
17
|
+
content:
|
|
18
|
+
summary: >
|
|
19
|
+
SFDIPOT stands for Structure, Function, Data, Interfaces, Platform,
|
|
20
|
+
Operations, and Time. Each dimension prompts a different lens through
|
|
21
|
+
which to examine the product. Walk through all seven during the
|
|
22
|
+
reconnaissance phase to build a comprehensive test charter.
|
|
23
|
+
|
|
24
|
+
dimensions:
|
|
25
|
+
- name: Structure
|
|
26
|
+
letter: S
|
|
27
|
+
description: "What the product IS — its physical and logical composition."
|
|
28
|
+
questions:
|
|
29
|
+
- "What are the major components, modules, or pages?"
|
|
30
|
+
- "How is the navigation organized — what is the sitemap?"
|
|
31
|
+
- "What are the code layers (UI, API, DB, services)?"
|
|
32
|
+
- "Where are the configuration files, feature flags, or admin settings?"
|
|
33
|
+
- "What is the URL structure — are there hidden or undocumented routes?"
|
|
34
|
+
- "How is the database schema organized — what are the key entities?"
|
|
35
|
+
test_ideas:
|
|
36
|
+
- "Map every navigable page and check for orphan pages."
|
|
37
|
+
- "Inspect HTML/DOM structure for semantic correctness."
|
|
38
|
+
- "Check that all links resolve — no 404s."
|
|
39
|
+
- "Verify the component hierarchy matches the design system."
|
|
40
|
+
- "Look for exposed debug endpoints, admin panels, or status pages."
|
|
41
|
+
- "Check that the URL structure is logical and consistent."
|
|
42
|
+
|
|
43
|
+
- name: Function
|
|
44
|
+
letter: F
|
|
45
|
+
description: "What the product DOES — every feature, capability, and workflow."
|
|
46
|
+
questions:
|
|
47
|
+
- "What are the primary user workflows (happy paths)?"
|
|
48
|
+
- "What can each user role do? What should they NOT be able to do?"
|
|
49
|
+
- "What are the CRUD operations and where do they happen?"
|
|
50
|
+
- "What happens on form submission — validation, confirmation, side effects?"
|
|
51
|
+
- "Are there background jobs, scheduled tasks, or async operations?"
|
|
52
|
+
- "What are the search, filter, and sort capabilities?"
|
|
53
|
+
test_ideas:
|
|
54
|
+
- "Execute every happy path end to end."
|
|
55
|
+
- "Test each user role's permissions — try actions outside your role."
|
|
56
|
+
- "Submit every form with valid data, then with invalid data."
|
|
57
|
+
- "Test all search/filter/sort combinations."
|
|
58
|
+
- "Verify confirmation dialogs before destructive actions."
|
|
59
|
+
- "Check that undo/redo works where available."
|
|
60
|
+
- "Test pagination and infinite scroll behavior."
|
|
61
|
+
|
|
62
|
+
- name: Data
|
|
63
|
+
letter: D
|
|
64
|
+
description: "What the product PROCESSES — inputs, outputs, stored state."
|
|
65
|
+
questions:
|
|
66
|
+
- "What are all the input fields and what data types do they accept?"
|
|
67
|
+
- "What are the validation rules — min, max, required, format?"
|
|
68
|
+
- "What data is persisted and where (DB, localStorage, cookies, session)?"
|
|
69
|
+
- "What data is displayed and how is it formatted?"
|
|
70
|
+
- "Are there import/export features? What formats?"
|
|
71
|
+
- "How is sensitive data (PII, passwords, tokens) handled?"
|
|
72
|
+
test_ideas:
|
|
73
|
+
- "Test every input at its boundaries (see boundary-testing technique)."
|
|
74
|
+
- "Enter data with special characters, Unicode, emoji, RTL text."
|
|
75
|
+
- "Check that data survives a round trip — enter, save, reload, verify."
|
|
76
|
+
- "Test with empty datasets and with very large datasets."
|
|
77
|
+
- "Verify sensitive data is masked in the UI and not leaked in network responses."
|
|
78
|
+
- "Check localStorage/sessionStorage/cookies for unencrypted sensitive data."
|
|
79
|
+
- "Test file uploads with wrong extensions, oversized files, empty files."
|
|
80
|
+
|
|
81
|
+
- name: Interfaces
|
|
82
|
+
letter: I
|
|
83
|
+
description: "How the product CONNECTS — APIs, integrations, UI touchpoints."
|
|
84
|
+
questions:
|
|
85
|
+
- "What external APIs or services does the product call?"
|
|
86
|
+
- "What APIs does the product expose?"
|
|
87
|
+
- "How does the frontend communicate with the backend (REST, GraphQL, WebSocket)?"
|
|
88
|
+
- "Are there third-party integrations (payment, email, analytics, SSO)?"
|
|
89
|
+
- "What happens when an external dependency is slow or unavailable?"
|
|
90
|
+
- "Are there webhooks, callbacks, or event-driven integrations?"
|
|
91
|
+
test_ideas:
|
|
92
|
+
- "Monitor network traffic for unexpected API calls or failed requests."
|
|
93
|
+
- "Test with a slow network (throttle to 3G in devtools)."
|
|
94
|
+
- "Block third-party domains and check graceful degradation."
|
|
95
|
+
- "Verify API error responses are handled in the UI (not raw JSON displayed)."
|
|
96
|
+
- "Check CORS headers on API endpoints."
|
|
97
|
+
- "Test SSO/OAuth login flows including token expiry."
|
|
98
|
+
- "Verify webhook payloads match the documented schema."
|
|
99
|
+
|
|
100
|
+
- name: Platform
|
|
101
|
+
letter: P
|
|
102
|
+
description: "What the product DEPENDS ON — OS, browser, hardware, infrastructure."
|
|
103
|
+
questions:
|
|
104
|
+
- "Which browsers and versions are supported?"
|
|
105
|
+
- "Is it responsive — does it work on mobile, tablet, desktop?"
|
|
106
|
+
- "What OS or hardware requirements exist?"
|
|
107
|
+
- "What is the hosting environment (cloud, on-prem, serverless)?"
|
|
108
|
+
- "Are there dependencies on specific runtimes, libraries, or versions?"
|
|
109
|
+
- "Does it work offline or with intermittent connectivity?"
|
|
110
|
+
test_ideas:
|
|
111
|
+
- "Test on Chrome, Firefox, Safari, and Edge."
|
|
112
|
+
- "Test at mobile (375px), tablet (768px), and desktop (1440px) viewports."
|
|
113
|
+
- "Check touch interactions on mobile — swipe, pinch, long press."
|
|
114
|
+
- "Test with browser zoom at 50%, 100%, 150%, 200%."
|
|
115
|
+
- "Disable JavaScript and check for graceful degradation or SSR."
|
|
116
|
+
- "Test with ad blockers and privacy extensions enabled."
|
|
117
|
+
- "Verify the app works with different locale/language settings."
|
|
118
|
+
|
|
119
|
+
- name: Operations
|
|
120
|
+
letter: O
|
|
121
|
+
description: "How the product is USED in practice — real-world usage patterns."
|
|
122
|
+
questions:
|
|
123
|
+
- "How do real users actually use the product (vs. how designers intended)?"
|
|
124
|
+
- "What are the most common user journeys from analytics?"
|
|
125
|
+
- "How do users recover from errors — is the error guidance sufficient?"
|
|
126
|
+
- "What does the onboarding experience look like for a new user?"
|
|
127
|
+
- "How do users manage their accounts, settings, and preferences?"
|
|
128
|
+
- "What happens during maintenance windows or deployments?"
|
|
129
|
+
test_ideas:
|
|
130
|
+
- "Follow the most common user journey from start to finish."
|
|
131
|
+
- "Test the first-time user experience with a fresh account."
|
|
132
|
+
- "Trigger every error message and evaluate its helpfulness."
|
|
133
|
+
- "Test multi-tab usage — open the same page in two tabs, edit in both."
|
|
134
|
+
- "Test the back button extensively — does the app handle browser history well?"
|
|
135
|
+
- "Log out and in — does session state persist correctly?"
|
|
136
|
+
- "Test with multiple users interacting with the same data simultaneously."
|
|
137
|
+
|
|
138
|
+
- name: Time
|
|
139
|
+
letter: T
|
|
140
|
+
description: "How the product BEHAVES over time — performance, state, decay."
|
|
141
|
+
questions:
|
|
142
|
+
- "How does performance change as data volume grows?"
|
|
143
|
+
- "Are there timeouts, expirations, or TTLs that affect behavior?"
|
|
144
|
+
- "What happens when sessions expire mid-workflow?"
|
|
145
|
+
- "Are there scheduled events, cron jobs, or time-based triggers?"
|
|
146
|
+
- "How does the product handle timezone and DST differences?"
|
|
147
|
+
- "What happens at date boundaries (midnight, month-end, year-end)?"
|
|
148
|
+
test_ideas:
|
|
149
|
+
- "Leave the app idle for 30+ minutes, then try to interact."
|
|
150
|
+
- "Test session timeout — what is preserved vs. lost?"
|
|
151
|
+
- "Change the system clock and observe time-dependent features."
|
|
152
|
+
- "Test with dates near DST transitions."
|
|
153
|
+
- "Test across timezones — create data in one TZ, view in another."
|
|
154
|
+
- "Rapidly repeat an action 50+ times — check for rate limiting or memory leaks."
|
|
155
|
+
- "Test long-running operations — do they show progress? Can they be cancelled?"
|
|
156
|
+
- "Check cache behavior — stale data after updates?"
|
|
157
|
+
|
|
158
|
+
when_to_use:
|
|
159
|
+
- "At the start of every exploratory session during the reconnaissance phase."
|
|
160
|
+
- "When building a test charter and you need to generate test ideas systematically."
|
|
161
|
+
- "When you feel stuck — pick a dimension you have not covered yet."
|
|
162
|
+
- "During risk assessment — rate each dimension for the feature under test."
|
|
163
|
+
- "When reviewing someone else's testing — check which dimensions they missed."
|
|
164
|
+
|
|
165
|
+
gotchas:
|
|
166
|
+
- "Agents tend to skip Operations and Time — these are the easiest to forget but often where the nastiest bugs hide. Force yourself to spend time on both."
|
|
167
|
+
- "Do not treat SFDIPOT as a checklist to rush through. Each dimension deserves genuine exploration and curiosity."
|
|
168
|
+
- "Structure is not just UI structure — include backend architecture, database schema, and infrastructure."
|
|
169
|
+
- "Interfaces includes internal interfaces (module-to-module) not just external APIs."
|
|
170
|
+
- "Platform testing is not just cross-browser. Consider network conditions, locale, accessibility settings, and device capabilities."
|
|
171
|
+
- "Time bugs are intermittent and hard to reproduce — document reproduction steps carefully."
|
|
@@ -0,0 +1,253 @@
|
|
|
1
|
+
id: heuristic-test-tours
|
|
2
|
+
version: "0.1.0"
|
|
3
|
+
type: heuristic
|
|
4
|
+
name: "Whittaker's Test Tours"
|
|
5
|
+
description: >
|
|
6
|
+
12 exploration strategies modeled as city tours. Each tour provides a
|
|
7
|
+
different motivation and focus for exploring the application, ensuring
|
|
8
|
+
diverse coverage without rigid test scripts. Mix and match tours across
|
|
9
|
+
sessions for maximum discovery.
|
|
10
|
+
author: "James Whittaker"
|
|
11
|
+
source: "Exploratory Software Testing"
|
|
12
|
+
tags: [exploration, how-to-explore, tours, eet]
|
|
13
|
+
domains: [all]
|
|
14
|
+
priority: high
|
|
15
|
+
added: "2026-03-28"
|
|
16
|
+
|
|
17
|
+
content:
|
|
18
|
+
summary: >
|
|
19
|
+
Think of the application as a city you are visiting. Different tours take
|
|
20
|
+
you through different neighborhoods with different goals. A tourist follows
|
|
21
|
+
the guidebook; a local knows the back alleys. Use these tours to structure
|
|
22
|
+
your exploration while keeping it creative and thorough.
|
|
23
|
+
|
|
24
|
+
tours:
|
|
25
|
+
- name: Guidebook Tour
|
|
26
|
+
description: >
|
|
27
|
+
Follow the official documentation, user guides, tutorials, and marketing
|
|
28
|
+
materials. Do exactly what they say and verify every claim. This is the
|
|
29
|
+
tourist experience — does the guided path work flawlessly?
|
|
30
|
+
strategy:
|
|
31
|
+
- "Open the product's documentation, help center, or getting-started guide."
|
|
32
|
+
- "Follow every step literally — do not improvise or take shortcuts."
|
|
33
|
+
- "Verify every screenshot, example, and expected outcome matches reality."
|
|
34
|
+
- "Check that all links in docs are valid and point to the right place."
|
|
35
|
+
- "Try every code sample or configuration example verbatim."
|
|
36
|
+
when_to_use:
|
|
37
|
+
- "Early in testing to validate the documented happy path."
|
|
38
|
+
- "After a major release or documentation update."
|
|
39
|
+
- "When onboarding to a new product — this is your first tour."
|
|
40
|
+
oracle: "Claims — the product must match its own documentation."
|
|
41
|
+
|
|
42
|
+
- name: Money Tour
|
|
43
|
+
description: >
|
|
44
|
+
Focus on the features that generate revenue or deliver the core value
|
|
45
|
+
proposition. These are the features the company cannot afford to have
|
|
46
|
+
broken — the ones that justify the product's price tag.
|
|
47
|
+
strategy:
|
|
48
|
+
- "Identify the product's top 3-5 revenue-generating features."
|
|
49
|
+
- "Test each one end-to-end as a paying customer would."
|
|
50
|
+
- "Test the purchase, subscription, upgrade, and payment flows."
|
|
51
|
+
- "Verify pricing is displayed correctly and calculated accurately."
|
|
52
|
+
- "Test the billing cycle, invoices, receipts, and refund processes."
|
|
53
|
+
when_to_use:
|
|
54
|
+
- "Every release — these features must always work."
|
|
55
|
+
- "Before a pricing change or billing system update."
|
|
56
|
+
- "When the business team reports revenue anomalies."
|
|
57
|
+
oracle: "Purpose — if these break, the product fails its reason to exist."
|
|
58
|
+
|
|
59
|
+
- name: Landmark Tour
|
|
60
|
+
description: >
|
|
61
|
+
Identify key landmarks (major features or pages) and navigate between
|
|
62
|
+
them, testing transitions and navigation. Like a tourist visiting all
|
|
63
|
+
the famous monuments — but paying attention to the roads between them.
|
|
64
|
+
strategy:
|
|
65
|
+
- "List 8-10 key pages or features (landmarks) of the application."
|
|
66
|
+
- "Visit each landmark and verify it renders correctly."
|
|
67
|
+
- "Navigate between landmarks using different paths (menu, breadcrumbs, direct URL, back button)."
|
|
68
|
+
- "Check that navigation state is preserved correctly (selected items, scroll position, filters)."
|
|
69
|
+
- "Verify deep links work — can you reach any landmark directly via URL?"
|
|
70
|
+
when_to_use:
|
|
71
|
+
- "When testing navigation, routing, or information architecture changes."
|
|
72
|
+
- "After restructuring the sitemap or menu."
|
|
73
|
+
- "When users report difficulty finding features."
|
|
74
|
+
oracle: "Product — navigation should be internally consistent."
|
|
75
|
+
|
|
76
|
+
- name: Bad Neighborhood Tour
|
|
77
|
+
description: >
|
|
78
|
+
Find the buggiest areas and spend extra time there. Bugs cluster — if
|
|
79
|
+
you find one bug in an area, look harder because there are likely more.
|
|
80
|
+
This is the tour of the rough parts of town.
|
|
81
|
+
strategy:
|
|
82
|
+
- "Start with areas that had bugs in the past (check bug tracker history)."
|
|
83
|
+
- "Focus on recently changed code (check the git log)."
|
|
84
|
+
- "Test complex features with many edge cases."
|
|
85
|
+
- "Revisit features built under time pressure or by junior developers."
|
|
86
|
+
- "When you find a bug, test everything nearby — same page, same form, same API."
|
|
87
|
+
when_to_use:
|
|
88
|
+
- "Mid-session when you have found your first bugs and want to find more."
|
|
89
|
+
- "When regression testing — focus on historically buggy areas."
|
|
90
|
+
- "When time is limited and you want maximum bug yield."
|
|
91
|
+
oracle: "History — areas that broke before will break again."
|
|
92
|
+
|
|
93
|
+
- name: Intellectual Tour
|
|
94
|
+
description: >
|
|
95
|
+
Seek out the hardest, most complex features and try to break them with
|
|
96
|
+
sophisticated test cases. Challenge the product with the most difficult
|
|
97
|
+
inputs and scenarios you can think of.
|
|
98
|
+
strategy:
|
|
99
|
+
- "Find the most complex algorithm or calculation in the product."
|
|
100
|
+
- "Test with extreme inputs — very large, very small, very precise."
|
|
101
|
+
- "Test complex multi-step workflows with branching logic."
|
|
102
|
+
- "Combine features that were probably not designed to work together."
|
|
103
|
+
- "Test concurrent operations — what happens when two users edit the same thing?"
|
|
104
|
+
- "Look for race conditions in async operations."
|
|
105
|
+
when_to_use:
|
|
106
|
+
- "When testing features with complex business logic."
|
|
107
|
+
- "For high-risk areas like financial calculations, scheduling, or permissions."
|
|
108
|
+
- "When you want to challenge assumptions about data integrity."
|
|
109
|
+
oracle: "Explainable — complex features should still produce explainable results."
|
|
110
|
+
|
|
111
|
+
- name: FedEx Tour
|
|
112
|
+
description: >
|
|
113
|
+
Follow a piece of data through the entire system, from input to storage
|
|
114
|
+
to display to export. Like tracking a FedEx package — follow it through
|
|
115
|
+
every touchpoint and handoff.
|
|
116
|
+
strategy:
|
|
117
|
+
- "Create a piece of data with distinctive values (e.g., a product named 'FEDEX-TEST-001')."
|
|
118
|
+
- "Track it through creation, editing, display, search results, reports, notifications."
|
|
119
|
+
- "Verify it appears correctly in every context — list view, detail view, export, email."
|
|
120
|
+
- "Check that edits propagate everywhere — no stale data in caches or secondary views."
|
|
121
|
+
- "Delete it and verify it is gone from everywhere (or properly archived)."
|
|
122
|
+
- "Check the database directly if possible — is the stored data what you expect?"
|
|
123
|
+
when_to_use:
|
|
124
|
+
- "When testing data flow and data integrity."
|
|
125
|
+
- "After changes to data models, APIs, or storage layers."
|
|
126
|
+
- "When users report data inconsistencies or stale information."
|
|
127
|
+
oracle: "Product — data should be consistent across every view and context."
|
|
128
|
+
|
|
129
|
+
- name: Garbage Collector Tour
|
|
130
|
+
description: >
|
|
131
|
+
Find and test the features nobody cares about — the neglected, dusty
|
|
132
|
+
corners of the application. These are the least-used, least-tested,
|
|
133
|
+
least-loved features where bugs hide undiscovered.
|
|
134
|
+
strategy:
|
|
135
|
+
- "Find features not mentioned in marketing materials or documentation."
|
|
136
|
+
- "Look for admin pages, settings panels, and configuration screens."
|
|
137
|
+
- "Test import/export features, bulk operations, and advanced filters."
|
|
138
|
+
- "Check help pages, about pages, terms of service pages, and footers."
|
|
139
|
+
- "Look for legacy features that are still accessible but seem abandoned."
|
|
140
|
+
- "Test empty states — what does the app look like with no data?"
|
|
141
|
+
when_to_use:
|
|
142
|
+
- "When main features are already well-tested and you want broader coverage."
|
|
143
|
+
- "When looking for security issues — neglected features often lack proper auth checks."
|
|
144
|
+
- "When testing for completeness before a major release."
|
|
145
|
+
oracle: "Users — even rarely-used features should work for the users who need them."
|
|
146
|
+
|
|
147
|
+
- name: Museum Tour
|
|
148
|
+
description: >
|
|
149
|
+
Test legacy code and old features that are still in the product. Like
|
|
150
|
+
visiting a museum — these artifacts are old but still on display and
|
|
151
|
+
must be maintained. Regressions love to hide here.
|
|
152
|
+
strategy:
|
|
153
|
+
- "Identify the oldest features in the product."
|
|
154
|
+
- "Test features that have not been updated in the last 3+ releases."
|
|
155
|
+
- "Check that old features work with new data formats and new user roles."
|
|
156
|
+
- "Verify backwards compatibility — can old URLs, API versions, and data formats still be used?"
|
|
157
|
+
- "Test migration paths — what happens to old data in the new system?"
|
|
158
|
+
when_to_use:
|
|
159
|
+
- "After a major refactoring, framework upgrade, or migration."
|
|
160
|
+
- "When the product has significant technical debt."
|
|
161
|
+
- "When long-time users report that something 'used to work.'"
|
|
162
|
+
oracle: "History — old features should still behave as they always have."
|
|
163
|
+
|
|
164
|
+
- name: Rained-Out Tour
|
|
165
|
+
description: >
|
|
166
|
+
Start a task and then abandon it partway through. Like a tourist whose
|
|
167
|
+
plans are rained out — what happens when you cancel, close the tab, go
|
|
168
|
+
back, or lose connectivity mid-workflow?
|
|
169
|
+
strategy:
|
|
170
|
+
- "Start filling a form and navigate away without saving."
|
|
171
|
+
- "Begin a multi-step wizard and close the browser tab at each step."
|
|
172
|
+
- "Start an upload and cancel it midway."
|
|
173
|
+
- "Begin checkout, then hit the back button repeatedly."
|
|
174
|
+
- "Disconnect the network during a save operation."
|
|
175
|
+
- "Close a modal without completing its action."
|
|
176
|
+
- "Let a session time out during an unsaved operation."
|
|
177
|
+
when_to_use:
|
|
178
|
+
- "When testing state management and data persistence."
|
|
179
|
+
- "When testing error recovery and resilience."
|
|
180
|
+
- "When looking for data corruption or orphaned records."
|
|
181
|
+
oracle: "Users — users abandon tasks all the time; the product should handle it gracefully."
|
|
182
|
+
|
|
183
|
+
- name: Couch Potato Tour
|
|
184
|
+
description: >
|
|
185
|
+
Do as little as possible. Accept every default, skip every optional
|
|
186
|
+
field, take every shortcut. What is the laziest possible path through
|
|
187
|
+
the application? Does the product still work?
|
|
188
|
+
strategy:
|
|
189
|
+
- "Create an account with only the required fields."
|
|
190
|
+
- "Accept all default settings without changing anything."
|
|
191
|
+
- "Skip every optional step in wizards."
|
|
192
|
+
- "Leave optional fields blank everywhere."
|
|
193
|
+
- "Use the shortest possible valid input for every required field."
|
|
194
|
+
- "Never scroll down — only interact with what is above the fold."
|
|
195
|
+
when_to_use:
|
|
196
|
+
- "When testing defaults and minimal configurations."
|
|
197
|
+
- "When testing the first-time user experience."
|
|
198
|
+
- "When verifying that required vs. optional is correctly implemented."
|
|
199
|
+
oracle: "Users — the laziest path should still produce a usable outcome."
|
|
200
|
+
|
|
201
|
+
- name: Obsessive-Compulsive Tour
|
|
202
|
+
description: >
|
|
203
|
+
Repeat the same action over and over. Enter the same data twice. Click
|
|
204
|
+
the same button rapidly. Undo and redo. Do everything twice or ten times
|
|
205
|
+
to see if the product handles repetition gracefully.
|
|
206
|
+
strategy:
|
|
207
|
+
- "Double-click every single-click button."
|
|
208
|
+
- "Submit the same form multiple times rapidly."
|
|
209
|
+
- "Create a duplicate record — same name, same email, same data."
|
|
210
|
+
- "Undo and redo the same action 20 times."
|
|
211
|
+
- "Refresh the page repeatedly during a loading operation."
|
|
212
|
+
- "Resize the browser window rapidly while content is loading."
|
|
213
|
+
- "Toggle the same setting on/off/on/off rapidly."
|
|
214
|
+
when_to_use:
|
|
215
|
+
- "When testing idempotency and duplicate handling."
|
|
216
|
+
- "When looking for race conditions and concurrency bugs."
|
|
217
|
+
- "When testing UI stability under rapid interaction."
|
|
218
|
+
oracle: "Explainable — repeated actions should produce consistent, predictable results."
|
|
219
|
+
|
|
220
|
+
- name: Saboteur Tour
|
|
221
|
+
description: >
|
|
222
|
+
Actively try to break the application. Inject bad data, revoke
|
|
223
|
+
permissions mid-session, kill processes, corrupt files. You are the
|
|
224
|
+
villain — what is the worst you can do?
|
|
225
|
+
strategy:
|
|
226
|
+
- "Inject SQL, XSS, and script payloads into every input field."
|
|
227
|
+
- "Manipulate hidden form fields, cookies, and localStorage."
|
|
228
|
+
- "Modify API requests in-flight using browser devtools or a proxy."
|
|
229
|
+
- "Change user role/permissions in another tab and continue operating."
|
|
230
|
+
- "Upload malicious files — .exe renamed to .jpg, SVG with embedded script."
|
|
231
|
+
- "Exhaust resources — fill disk space, use up all licenses, exceed rate limits."
|
|
232
|
+
- "Use browser devtools to modify the DOM and bypass client-side validation."
|
|
233
|
+
when_to_use:
|
|
234
|
+
- "Security-focused testing sessions."
|
|
235
|
+
- "Before a penetration test — find the easy wins first."
|
|
236
|
+
- "When testing input validation, authorization, and error handling."
|
|
237
|
+
- "As the default negative testing tour in every session."
|
|
238
|
+
oracle: "Standards — security and validation must meet established security standards."
|
|
239
|
+
|
|
240
|
+
when_to_use:
|
|
241
|
+
- "Select 2-3 tours per exploratory session for diverse coverage."
|
|
242
|
+
- "Always include at least one negative tour (Bad Neighborhood, Saboteur, or Rained-Out)."
|
|
243
|
+
- "Guidebook Tour and Money Tour first for new products — establish the baseline."
|
|
244
|
+
- "Rotate tours across sessions to avoid testing the same way every time."
|
|
245
|
+
- "Match tours to risk — high-risk features get Intellectual and Saboteur tours."
|
|
246
|
+
|
|
247
|
+
gotchas:
|
|
248
|
+
- "Do not try to do all 12 tours in one session — pick 2-3 and go deep."
|
|
249
|
+
- "The Couch Potato Tour catches surprisingly many bugs — do not underestimate it."
|
|
250
|
+
- "Saboteur Tour should be in every session's plan — agents tend to stay on happy paths."
|
|
251
|
+
- "Rained-Out Tour is critical for mobile and SPA applications where users frequently navigate away."
|
|
252
|
+
- "FedEx Tour is the best way to find data inconsistency bugs that other tours miss."
|
|
253
|
+
- "Bad Neighborhood Tour requires historical bug data — check the bug tracker first."
|
|
@@ -0,0 +1,84 @@
|
|
|
1
|
+
id: reference-exploratory-testing-types
|
|
2
|
+
version: "0.1.0"
|
|
3
|
+
type: reference
|
|
4
|
+
name: "Exploratory Testing Types & Approach"
|
|
5
|
+
description: >
|
|
6
|
+
Three types of exploratory testing (unplanned, scenario-based, strategic) and
|
|
7
|
+
the learn-test-adapt loop. Key for AI agents: don't just use one mode — adapt
|
|
8
|
+
the approach based on familiarity with the application.
|
|
9
|
+
author: "Artem Golubev"
|
|
10
|
+
source: "testRigor Blog"
|
|
11
|
+
tags: [exploratory, methodology, approach, agile, types]
|
|
12
|
+
domains: [all]
|
|
13
|
+
priority: medium
|
|
14
|
+
added: "2026-03-28"
|
|
15
|
+
updated: "2026-03-28"
|
|
16
|
+
|
|
17
|
+
content:
|
|
18
|
+
summary: >
|
|
19
|
+
Exploratory testing is "not so much a thing you do; it's far more a way that
|
|
20
|
+
you think." Three distinct modes exist, and the AI agent should shift between
|
|
21
|
+
them during a session based on what it learns about the application.
|
|
22
|
+
|
|
23
|
+
three_types:
|
|
24
|
+
- name: "Unplanned / Ad-hoc"
|
|
25
|
+
when: "First encounter with unknown application"
|
|
26
|
+
approach: "Freestyle — click around, observe, get a feel for the app"
|
|
27
|
+
ai_mapping: "This is our Discovery Phase — map the app without preconceptions"
|
|
28
|
+
strengths: "Fast, unbiased, finds obvious UX issues"
|
|
29
|
+
weaknesses: "Shallow, may miss complex flows"
|
|
30
|
+
|
|
31
|
+
- name: "User Scenario-based"
|
|
32
|
+
when: "After understanding the app's purpose and user types"
|
|
33
|
+
approach: "Think of real user journeys and test end-to-end flows"
|
|
34
|
+
ai_mapping: "This is our Functional Testing Phase — test complete user flows (login → browse → cart → checkout)"
|
|
35
|
+
strengths: "Finds flow-breaking bugs, tests real workflows"
|
|
36
|
+
weaknesses: "Biased toward happy paths if not careful"
|
|
37
|
+
|
|
38
|
+
- name: "Strategic"
|
|
39
|
+
when: "Deep familiarity with the app, looking for complex/hidden bugs"
|
|
40
|
+
approach: "Apply specific techniques — equivalence partitioning, risk-based, error guessing, boundary testing"
|
|
41
|
+
ai_mapping: "This is our Edge Case Phase — apply targeted heuristics and negative testing"
|
|
42
|
+
strengths: "Finds subtle bugs that survive other testing"
|
|
43
|
+
weaknesses: "Requires domain knowledge and experience"
|
|
44
|
+
|
|
45
|
+
learn_test_adapt_loop:
|
|
46
|
+
description: >
|
|
47
|
+
The core cycle of exploratory testing. Unlike scripted testing, you adapt
|
|
48
|
+
your approach based on what you discover. Each action informs the next.
|
|
49
|
+
steps:
|
|
50
|
+
- "OBSERVE: Take a snapshot, read the page, check console/network"
|
|
51
|
+
- "THINK: Based on what I see, what could go wrong here? What would a user try?"
|
|
52
|
+
- "TEST: Execute the test idea (fill form, click button, try edge case)"
|
|
53
|
+
- "LEARN: What happened? Was it expected? What does this tell me about the app?"
|
|
54
|
+
- "ADAPT: Based on what I learned, where should I look next?"
|
|
55
|
+
ai_implication: >
|
|
56
|
+
After every significant action, the AI agent should explicitly reason about
|
|
57
|
+
what it learned and what to test next — not just follow a predetermined script.
|
|
58
|
+
Log the reasoning ("I noticed the form accepted empty strings, so I'll now
|
|
59
|
+
test with XSS payloads to check if sanitization is also missing").
|
|
60
|
+
|
|
61
|
+
documentation_during_testing:
|
|
62
|
+
principle: "Log every finding immediately — you'll forget or lose context otherwise"
|
|
63
|
+
what_to_log:
|
|
64
|
+
- "What you tested and WHY you chose to test it"
|
|
65
|
+
- "What you observed (expected vs actual)"
|
|
66
|
+
- "Screenshots/console output as evidence"
|
|
67
|
+
- "Questions that arose (unclear behavior needing human judgment)"
|
|
68
|
+
- "Ideas for further testing that you didn't have time for"
|
|
69
|
+
|
|
70
|
+
challenges_for_ai:
|
|
71
|
+
- "Diversification: AI tends to test the same way every time — needs randomization/variation"
|
|
72
|
+
- "Measuring success: Hard to quantify ROI of exploratory sessions — track bugs found per session"
|
|
73
|
+
- "Skill level: Strategic exploratory testing requires deep domain knowledge — use domain configs"
|
|
74
|
+
- "Reproducing bugs: Always log exact steps during exploration, not after the fact"
|
|
75
|
+
|
|
76
|
+
agile_integration:
|
|
77
|
+
description: >
|
|
78
|
+
In Agile, exploratory testing complements sprint testing by finding edge cases
|
|
79
|
+
that structured test cases miss. Best run: after feature completion, before sprint review.
|
|
80
|
+
when_to_use:
|
|
81
|
+
- "New feature just completed — explore before writing formal tests"
|
|
82
|
+
- "Sprint review prep — quick sanity exploration"
|
|
83
|
+
- "After bug fix — explore around the fix to find related issues"
|
|
84
|
+
- "New team member onboarding — explore to learn the product"
|
|
@@ -0,0 +1,95 @@
|
|
|
1
|
+
id: reference-heuristic-praxis
|
|
2
|
+
version: "0.1.0"
|
|
3
|
+
type: reference
|
|
4
|
+
name: "Heuristic Praxis — Theory Meets Practice"
|
|
5
|
+
description: >
|
|
6
|
+
Understanding when and how to apply heuristics thoughtfully, not mechanically.
|
|
7
|
+
Covers the praxis gap between knowing heuristics and using them effectively.
|
|
8
|
+
Critical for AI agents: avoid applying heuristics as checklists without contextual reasoning.
|
|
9
|
+
author: "Ministry of Testing (Richard Bradshaw, Mark Winteringham)"
|
|
10
|
+
source: "Ministry of Testing"
|
|
11
|
+
tags: [heuristics, praxis, theory, meta-testing, reflection]
|
|
12
|
+
domains: [all]
|
|
13
|
+
priority: high
|
|
14
|
+
added: "2026-03-28"
|
|
15
|
+
updated: "2026-03-28"
|
|
16
|
+
|
|
17
|
+
content:
|
|
18
|
+
summary: >
|
|
19
|
+
Heuristics are cognitive shortcuts — not guaranteed solutions. The praxis gap
|
|
20
|
+
is the space between knowing heuristics (theory) and applying them effectively
|
|
21
|
+
(practice). AI agents are especially prone to this gap: mechanically applying
|
|
22
|
+
SFDIPOT or FEW HICCUPPS as checklists without adapting to context.
|
|
23
|
+
|
|
24
|
+
key_principles:
|
|
25
|
+
- name: "All heuristics are fallible"
|
|
26
|
+
description: "No heuristic guarantees finding bugs. They suggest where to look, not what you'll find."
|
|
27
|
+
ai_implication: "Don't report 'no bugs found in this dimension' as confidence — it means you didn't find any yet."
|
|
28
|
+
|
|
29
|
+
- name: "Context determines which heuristic to use"
|
|
30
|
+
description: "A heuristic that works in e-commerce may not help in fintech. Choose based on what you observe."
|
|
31
|
+
ai_implication: "After discovery phase, select 2-3 most relevant SFDIPOT dimensions rather than mechanically checking all 7."
|
|
32
|
+
|
|
33
|
+
- name: "Unknowing use causes biases"
|
|
34
|
+
description: "The availability heuristic makes you test what you recently saw succeed. Availability bias in AI means repeating patterns from training data."
|
|
35
|
+
ai_implication: "Explicitly challenge your own test ideas — ask 'what am I NOT testing that a user would care about?'"
|
|
36
|
+
|
|
37
|
+
- name: "Modify heuristics to fit your context"
|
|
38
|
+
description: "FEW HICCUPPS started as HICCUPS. RCRCRC became RCRCRCR when Revenue was added. Don't use heuristics rigidly."
|
|
39
|
+
ai_implication: "After each session, evaluate which heuristic dimensions were useful and which were noise. Adapt for next time."
|
|
40
|
+
|
|
41
|
+
- name: "Reflect on efficacy"
|
|
42
|
+
description: "After applying a heuristic, ask: did it help me find real bugs? What did I miss? What worked?"
|
|
43
|
+
ai_implication: "The /qa-explore-feedback skill should capture which heuristics led to real findings and which didn't."
|
|
44
|
+
|
|
45
|
+
additional_heuristics_to_know:
|
|
46
|
+
- name: "Goldilocks (Elisabeth Hendrickson)"
|
|
47
|
+
description: "Too big, too small, just right — test data extremes and typical values"
|
|
48
|
+
mnemonic: "Goldilocks"
|
|
49
|
+
apply_to: "Every input field, data entry, configuration value"
|
|
50
|
+
|
|
51
|
+
- name: "RCRCRC (Karen N. Johnson)"
|
|
52
|
+
description: "Recent, Core, Risky, Configuration, Repaired, Chronic — regression testing focus areas"
|
|
53
|
+
mnemonic: "RCRCRC"
|
|
54
|
+
apply_to: "Regression testing, deciding what to test after changes"
|
|
55
|
+
|
|
56
|
+
- name: "SACRED (Richard Bradshaw)"
|
|
57
|
+
description: "Automated check design heuristic"
|
|
58
|
+
apply_to: "When generating test scripts from exploratory findings"
|
|
59
|
+
|
|
60
|
+
- name: "TRIMS (Richard Bradshaw)"
|
|
61
|
+
description: "Automation strategy thinking"
|
|
62
|
+
apply_to: "When deciding what to automate from session findings"
|
|
63
|
+
|
|
64
|
+
- name: "SCAMPER (applied by John Stevenson)"
|
|
65
|
+
description: "Substitute, Combine, Adapt, Modify, Put to another use, Eliminate, Reverse — remix existing models"
|
|
66
|
+
apply_to: "When standard heuristics aren't generating enough test ideas, remix them"
|
|
67
|
+
|
|
68
|
+
praxis_gap_for_ai_agents:
|
|
69
|
+
description: >
|
|
70
|
+
AI agents are highly prone to the heuristic praxis gap. They apply heuristics
|
|
71
|
+
mechanically from training data without adapting to the specific context of
|
|
72
|
+
what they're testing. The biggest risks:
|
|
73
|
+
|
|
74
|
+
anti_patterns:
|
|
75
|
+
- "Applying ALL heuristic dimensions equally instead of prioritizing by context"
|
|
76
|
+
- "Treating heuristics as checklists to complete rather than thinking tools"
|
|
77
|
+
- "Not adapting test approach when a heuristic isn't producing useful results"
|
|
78
|
+
- "Missing domain-specific bugs because the heuristic doesn't cover business logic"
|
|
79
|
+
- "Availability bias: testing what the agent has seen before rather than what matters here"
|
|
80
|
+
|
|
81
|
+
mitigations:
|
|
82
|
+
- "After discovery, explicitly reason about WHICH heuristic dimensions matter most for THIS app"
|
|
83
|
+
- "If a heuristic dimension yields nothing after 5 minutes, switch to another"
|
|
84
|
+
- "Always ask: 'What would a real user of THIS app care about that I haven't tested?'"
|
|
85
|
+
- "Use domain configs (data/domains/) to inject business context before applying generic heuristics"
|
|
86
|
+
- "In the feedback loop, track which heuristics led to real bugs vs noise"
|
|
87
|
+
|
|
88
|
+
references:
|
|
89
|
+
- "Tversky & Kahneman — Judgment under Uncertainty: Heuristics and Biases"
|
|
90
|
+
- "Kahneman — Thinking, Fast and Slow (System 1 vs System 2)"
|
|
91
|
+
- "Elisabeth Hendrickson — Explore It!"
|
|
92
|
+
- "Michael Bolton — FEW HICCUPPS blog"
|
|
93
|
+
- "Del Dewar — Testing Mnemonics mind map"
|
|
94
|
+
- "Test Heuristics Cheat Sheet — Hendrickson, Lyndsay, Emery"
|
|
95
|
+
- "John Stevenson — Model Fatigue and How to Break It"
|