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,194 @@
|
|
|
1
|
+
id: heuristic-few-hiccupps
|
|
2
|
+
version: "0.1.0"
|
|
3
|
+
type: heuristic
|
|
4
|
+
name: "FEW HICCUPPS - Consistency Oracles"
|
|
5
|
+
description: >
|
|
6
|
+
A set of 11 oracle heuristics for recognizing problems during testing.
|
|
7
|
+
A bug is anything that threatens the value of the product. FEW HICCUPPS
|
|
8
|
+
helps you detect bugs by checking whether the product is consistent with
|
|
9
|
+
various reference points. If the product violates any of these consistency
|
|
10
|
+
checks, you may have found a bug worth reporting.
|
|
11
|
+
author: "James Bach & Michael Bolton"
|
|
12
|
+
source: "Rapid Software Testing"
|
|
13
|
+
tags: [oracles, bug-recognition, consistency, rst]
|
|
14
|
+
domains: [all]
|
|
15
|
+
priority: high
|
|
16
|
+
added: "2026-03-28"
|
|
17
|
+
|
|
18
|
+
content:
|
|
19
|
+
summary: >
|
|
20
|
+
An oracle is a mechanism for recognizing a problem. FEW HICCUPPS provides
|
|
21
|
+
11 consistency heuristics — reference frames against which you compare the
|
|
22
|
+
product's actual behavior. When behavior is inconsistent with any of these
|
|
23
|
+
references, investigate further. Not every inconsistency is a bug, but
|
|
24
|
+
every bug is an inconsistency with something that matters.
|
|
25
|
+
|
|
26
|
+
oracles:
|
|
27
|
+
- name: Familiar
|
|
28
|
+
letter: F
|
|
29
|
+
description: "Is the product consistent with things we have seen before — patterns, conventions, prior experience?"
|
|
30
|
+
questions:
|
|
31
|
+
- "Does this behave like similar features I have tested in other products?"
|
|
32
|
+
- "Does the interaction pattern match what I have seen in well-known apps?"
|
|
33
|
+
- "Does the error handling follow familiar conventions?"
|
|
34
|
+
- "Would an experienced user find this behavior surprising?"
|
|
35
|
+
examples:
|
|
36
|
+
- "A delete button that does not ask for confirmation — most products do."
|
|
37
|
+
- "A form that clears all fields when one validation fails — unusual and frustrating."
|
|
38
|
+
- "A 'Save' button that does not give any feedback — most apps show a toast or change button state."
|
|
39
|
+
- "Search results that are not ranked by relevance — Google has set the expectation."
|
|
40
|
+
|
|
41
|
+
- name: Explainable
|
|
42
|
+
letter: E
|
|
43
|
+
description: "Can the behavior be explained rationally? If not, it might be a bug."
|
|
44
|
+
questions:
|
|
45
|
+
- "Can I explain why the product behaves this way?"
|
|
46
|
+
- "Is there a logical reason for this output given this input?"
|
|
47
|
+
- "If a user asked me why this happened, could I give a clear answer?"
|
|
48
|
+
- "Does the response time make sense for this operation?"
|
|
49
|
+
examples:
|
|
50
|
+
- "A page takes 12 seconds to load but only displays 5 items — unexplainable slowness."
|
|
51
|
+
- "Clicking 'Cancel' saves the form — behavior contradicts the label."
|
|
52
|
+
- "A price calculation shows a negative total — no rational explanation."
|
|
53
|
+
- "Two identical searches return different results — nondeterminism without cause."
|
|
54
|
+
|
|
55
|
+
- name: World
|
|
56
|
+
letter: W
|
|
57
|
+
description: "Is the product consistent with the real world — laws of physics, business rules, domain knowledge?"
|
|
58
|
+
questions:
|
|
59
|
+
- "Does this match how the real-world process works?"
|
|
60
|
+
- "Are business rules correctly enforced?"
|
|
61
|
+
- "Does the data make sense in a real-world context?"
|
|
62
|
+
- "Are regulatory or legal requirements met?"
|
|
63
|
+
examples:
|
|
64
|
+
- "An ecommerce site allowing a delivery date in the past."
|
|
65
|
+
- "A banking app that permits a negative account balance without overdraft protection."
|
|
66
|
+
- "A calendar that allows scheduling a meeting for February 30."
|
|
67
|
+
- "A shipping calculator that charges less for international than domestic delivery."
|
|
68
|
+
|
|
69
|
+
- name: History
|
|
70
|
+
letter: H
|
|
71
|
+
description: "Is the product consistent with its own past behavior — previous versions, established patterns?"
|
|
72
|
+
questions:
|
|
73
|
+
- "Did this feature work differently in the previous version?"
|
|
74
|
+
- "Has a regression been introduced?"
|
|
75
|
+
- "Does this behavior match the release notes?"
|
|
76
|
+
- "Are deprecated features still accessible when they should not be?"
|
|
77
|
+
examples:
|
|
78
|
+
- "Export feature used to produce CSV with headers, now it omits them."
|
|
79
|
+
- "Login used to remember the last email, now it clears the field."
|
|
80
|
+
- "API response format changed without a version bump."
|
|
81
|
+
- "A feature that worked on the previous build now throws a 500 error."
|
|
82
|
+
|
|
83
|
+
- name: Image
|
|
84
|
+
letter: I
|
|
85
|
+
description: "Is the product consistent with the organization's image, brand, and reputation?"
|
|
86
|
+
questions:
|
|
87
|
+
- "Does the quality level match the company's brand promise?"
|
|
88
|
+
- "Would this bug embarrass the company if a customer found it?"
|
|
89
|
+
- "Does the tone and language match the brand voice?"
|
|
90
|
+
- "Is the polish level consistent with the price point?"
|
|
91
|
+
examples:
|
|
92
|
+
- "Typos on a banking app's homepage — inconsistent with a trust-based brand."
|
|
93
|
+
- "A premium SaaS product with broken layout on mobile — damages credibility."
|
|
94
|
+
- "Error messages with technical jargon in a consumer-facing app."
|
|
95
|
+
- "A healthcare app that casually says 'Oops!' when displaying medical results."
|
|
96
|
+
|
|
97
|
+
- name: Comparable
|
|
98
|
+
letter: C
|
|
99
|
+
description: "Is the product consistent with comparable products — competitors, similar tools, industry standards?"
|
|
100
|
+
questions:
|
|
101
|
+
- "How do competitors handle this same feature?"
|
|
102
|
+
- "Is there an industry-standard way to implement this?"
|
|
103
|
+
- "Does this meet the baseline that users expect from this product category?"
|
|
104
|
+
- "Are there well-known UI patterns this feature should follow?"
|
|
105
|
+
examples:
|
|
106
|
+
- "A checkout flow that requires 7 steps when competitors do it in 3."
|
|
107
|
+
- "No auto-save in a document editor — Google Docs and Notion both do this."
|
|
108
|
+
- "No keyboard shortcut for the most common action — all competitors have one."
|
|
109
|
+
- "Requiring page refresh to see updates — competitors use real-time sync."
|
|
110
|
+
|
|
111
|
+
- name: Claims
|
|
112
|
+
letter: C
|
|
113
|
+
description: "Is the product consistent with what it claims to do — docs, marketing, help text, tooltips?"
|
|
114
|
+
questions:
|
|
115
|
+
- "Does the product do what the documentation says it does?"
|
|
116
|
+
- "Do marketing claims match actual capabilities?"
|
|
117
|
+
- "Are help text and tooltips accurate?"
|
|
118
|
+
- "Do error messages correctly describe what went wrong and how to fix it?"
|
|
119
|
+
examples:
|
|
120
|
+
- "Documentation says 'supports CSV and Excel' but Excel import fails."
|
|
121
|
+
- "Marketing page claims '99.9% uptime' but status page shows frequent incidents."
|
|
122
|
+
- "Tooltip says 'maximum 100 characters' but the field accepts 200."
|
|
123
|
+
- "Help article describes a settings page that no longer exists."
|
|
124
|
+
|
|
125
|
+
- name: Users
|
|
126
|
+
letter: U
|
|
127
|
+
description: "Is the product consistent with what users want, need, and expect?"
|
|
128
|
+
questions:
|
|
129
|
+
- "Would the target user find this workflow intuitive?"
|
|
130
|
+
- "Does the feature solve the user's actual problem?"
|
|
131
|
+
- "Are there unnecessary steps that frustrate users?"
|
|
132
|
+
- "Is the feature discoverable — can users find it without a manual?"
|
|
133
|
+
examples:
|
|
134
|
+
- "A required field that 90% of users leave blank — they do not understand why it is needed."
|
|
135
|
+
- "An important action buried three levels deep in settings."
|
|
136
|
+
- "A dashboard that shows data no one asked for and hides what they need."
|
|
137
|
+
- "Mobile users cannot complete a task that desktop users can."
|
|
138
|
+
|
|
139
|
+
- name: Product
|
|
140
|
+
letter: P
|
|
141
|
+
description: "Is the product consistent with itself — do all parts work together coherently?"
|
|
142
|
+
questions:
|
|
143
|
+
- "Does this feature behave the same way in all places it appears?"
|
|
144
|
+
- "Is the terminology consistent throughout the product?"
|
|
145
|
+
- "Does the same action produce the same result everywhere?"
|
|
146
|
+
- "Are visual styles, spacing, and components consistent across pages?"
|
|
147
|
+
examples:
|
|
148
|
+
- "Date format is DD/MM/YYYY on one page and MM/DD/YYYY on another."
|
|
149
|
+
- "'Remove' in one place, 'Delete' in another, 'Trash' in a third — all do the same thing."
|
|
150
|
+
- "Button styles differ between the settings page and the main app."
|
|
151
|
+
- "Pagination works differently on the users list vs. the orders list."
|
|
152
|
+
|
|
153
|
+
- name: Purpose
|
|
154
|
+
letter: P
|
|
155
|
+
description: "Is the product consistent with its explicit and implicit purpose — does it fulfill its reason for existing?"
|
|
156
|
+
questions:
|
|
157
|
+
- "Does this feature serve the product's core mission?"
|
|
158
|
+
- "Could a critical user journey fail because of this issue?"
|
|
159
|
+
- "Does the product achieve the outcome users bought it for?"
|
|
160
|
+
- "Are there features that actively work against the product's purpose?"
|
|
161
|
+
examples:
|
|
162
|
+
- "A project management tool where you cannot assign tasks to team members."
|
|
163
|
+
- "A search engine that returns irrelevant results for common queries."
|
|
164
|
+
- "An analytics dashboard that shows data with a 24-hour delay when real-time is the selling point."
|
|
165
|
+
- "A collaboration tool where changes are not visible to other users without refreshing."
|
|
166
|
+
|
|
167
|
+
- name: Standards
|
|
168
|
+
letter: S
|
|
169
|
+
description: "Is the product consistent with applicable standards — industry, legal, accessibility, technical?"
|
|
170
|
+
questions:
|
|
171
|
+
- "Does it meet WCAG 2.1 AA accessibility standards?"
|
|
172
|
+
- "Is it compliant with GDPR, CCPA, or other privacy regulations?"
|
|
173
|
+
- "Does the API follow REST conventions or the declared spec?"
|
|
174
|
+
- "Does it meet the organization's coding and UX standards?"
|
|
175
|
+
examples:
|
|
176
|
+
- "Images without alt text — violates WCAG 1.1.1."
|
|
177
|
+
- "No cookie consent banner in the EU — violates GDPR."
|
|
178
|
+
- "API returns 200 for errors instead of proper HTTP status codes."
|
|
179
|
+
- "Password stored in plain text in a cookie — violates security standards."
|
|
180
|
+
|
|
181
|
+
when_to_use:
|
|
182
|
+
- "Constantly during testing — this is your primary bug-detection lens."
|
|
183
|
+
- "When you see something odd but are not sure if it is a bug — check it against each oracle."
|
|
184
|
+
- "When writing bug reports — name which oracle the product violates to strengthen the argument."
|
|
185
|
+
- "During risk assessment — which oracles matter most for this product's context?"
|
|
186
|
+
- "In debriefs — categorize found bugs by which oracle detected them."
|
|
187
|
+
|
|
188
|
+
gotchas:
|
|
189
|
+
- "Not every inconsistency is a bug — some are deliberate design decisions. Investigate before reporting."
|
|
190
|
+
- "Multiple oracles can apply to the same bug. Name the strongest one in the report."
|
|
191
|
+
- "Users and Claims are the most concrete oracles — they give you the strongest arguments for filing a bug."
|
|
192
|
+
- "Standards is often the most actionable — you can cite specific regulations or specs."
|
|
193
|
+
- "Do not ignore Image — brand damage from quality issues can be more costly than functional bugs."
|
|
194
|
+
- "World is especially important for domain-specific testing (fintech, healthcare, ecommerce)."
|
|
@@ -0,0 +1,143 @@
|
|
|
1
|
+
id: heuristic-goldilocks
|
|
2
|
+
version: "0.1.0"
|
|
3
|
+
type: heuristic
|
|
4
|
+
name: "Goldilocks Heuristic"
|
|
5
|
+
description: >
|
|
6
|
+
"Too big, too small, just right" — a simple but powerful heuristic for testing
|
|
7
|
+
with extremes and typical values. For every input, ask: what happens when the
|
|
8
|
+
value is absurdly large, absurdly small, and perfectly normal? Apply this lens
|
|
9
|
+
to numbers, text, dates, selections, and file sizes to surface validation gaps,
|
|
10
|
+
display issues, and processing failures.
|
|
11
|
+
author: "Elisabeth Hendrickson"
|
|
12
|
+
source: "Explore It! — Reduce Risk and Increase Confidence with Exploratory Testing"
|
|
13
|
+
tags: [input-testing, boundaries, exploration, goldilocks]
|
|
14
|
+
domains: [all]
|
|
15
|
+
priority: high
|
|
16
|
+
added: "2026-03-28"
|
|
17
|
+
|
|
18
|
+
content:
|
|
19
|
+
summary: >
|
|
20
|
+
The Goldilocks heuristic borrows from the fairy tale: test with values that are
|
|
21
|
+
too big, too small, and just right. It complements formal boundary analysis by
|
|
22
|
+
encouraging you to think in terms of extremes and typicality rather than only
|
|
23
|
+
precise boundary values. For every input field, parameter, or configuration
|
|
24
|
+
value, generate at least one "too big," one "too small," and one "just right"
|
|
25
|
+
test case. This surfaces bugs in validation, storage, display, and calculation
|
|
26
|
+
that formal specs often miss.
|
|
27
|
+
|
|
28
|
+
principle: >
|
|
29
|
+
Every input has a "Goldilocks zone" — the range of values the system was
|
|
30
|
+
designed and tested to handle. Bugs live outside that zone (extremes the
|
|
31
|
+
developer never imagined) and sometimes inside it (typical values with
|
|
32
|
+
unexpected edge properties). Always test all three zones.
|
|
33
|
+
|
|
34
|
+
categories:
|
|
35
|
+
- name: Numbers (Currency, Quantities, Scores)
|
|
36
|
+
too_big:
|
|
37
|
+
- { value: "10000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 (googol)", note: "Far beyond any reasonable value — tests overflow, display truncation, storage limits" }
|
|
38
|
+
- { value: "999999999.99", note: "Maximum practical currency — does the UI handle it? Does the total overflow?" }
|
|
39
|
+
- { value: "2147483647", note: "Max int32 — common overflow boundary" }
|
|
40
|
+
- { value: "9999999", note: "Large quantity — performance, display, and calculation stress" }
|
|
41
|
+
too_small:
|
|
42
|
+
- { value: "-1", note: "Negative — does a quantity or price field allow negatives?" }
|
|
43
|
+
- { value: "-999999999.99", note: "Large negative — what happens to totals and calculations?" }
|
|
44
|
+
- { value: "0", note: "Zero — often a special case (division by zero, free items, zero balance)" }
|
|
45
|
+
- { value: "0.001", note: "Sub-penny amount — rounding behavior in financial calculations" }
|
|
46
|
+
- { value: "-0", note: "Negative zero — some languages treat this differently" }
|
|
47
|
+
just_right:
|
|
48
|
+
- { value: "42.50", note: "Typical price — happy path with decimals" }
|
|
49
|
+
- { value: "3", note: "Typical small quantity" }
|
|
50
|
+
- { value: "100.00", note: "Round number — common in real usage" }
|
|
51
|
+
- { value: "19.99", note: "Common retail price point" }
|
|
52
|
+
|
|
53
|
+
- name: Strings (Names, Descriptions, Text Fields)
|
|
54
|
+
too_big:
|
|
55
|
+
- { value: "'A' x 10000", note: "10K characters — far beyond most field limits" }
|
|
56
|
+
- { value: "'word ' x 5000", note: "25K characters of words — tests word-wrap, storage, and rendering" }
|
|
57
|
+
- { value: "A single paragraph repeated 100 times", note: "Realistic but excessive content" }
|
|
58
|
+
- { value: "URL or path string 2000+ characters long", note: "Tests URL length limits and parameter handling" }
|
|
59
|
+
too_small:
|
|
60
|
+
- { value: "", note: "Empty string — the most common too-small value" }
|
|
61
|
+
- { value: " ", note: "Single space — is whitespace-only accepted?" }
|
|
62
|
+
- { value: "A", note: "Single character — minimum meaningful input" }
|
|
63
|
+
- { value: "\\t", note: "Tab only — invisible but non-empty" }
|
|
64
|
+
just_right:
|
|
65
|
+
- { value: "John Smith", note: "Typical Western name" }
|
|
66
|
+
- { value: "Maria Garcia de la Cruz", note: "Longer name with spaces and special handling" }
|
|
67
|
+
- { value: "A 50-word product description", note: "Typical paragraph-length content" }
|
|
68
|
+
- { value: "user@example.com", note: "Standard email format" }
|
|
69
|
+
|
|
70
|
+
- name: Dates and Times
|
|
71
|
+
too_big:
|
|
72
|
+
- { value: "9999-12-31", note: "Far future — maximum representable date in many systems" }
|
|
73
|
+
- { value: "2099-01-01", note: "Distant future — valid but unlikely" }
|
|
74
|
+
- { value: "2038-01-19T03:14:08Z", note: "Unix Y2K38 overflow — int32 timestamp limit" }
|
|
75
|
+
too_small:
|
|
76
|
+
- { value: "1900-01-01", note: "Very old date — before Unix epoch" }
|
|
77
|
+
- { value: "1970-01-01", note: "Unix epoch — timestamp zero" }
|
|
78
|
+
- { value: "0000-01-01", note: "Year zero — invalid in many date libraries" }
|
|
79
|
+
- { value: "1969-12-31", note: "Day before Unix epoch — negative timestamp" }
|
|
80
|
+
just_right:
|
|
81
|
+
- { value: "2026-03-28", note: "Today's date — standard current date" }
|
|
82
|
+
- { value: "2026-06-15", note: "Near future — typical scheduling date" }
|
|
83
|
+
- { value: "2025-12-25", note: "Recent past — typical historical lookup" }
|
|
84
|
+
boundary_dates:
|
|
85
|
+
- { value: "2024-02-29", note: "Leap day (2024 is leap year) — valid" }
|
|
86
|
+
- { value: "2025-02-29", note: "Not a leap year — invalid, should be rejected" }
|
|
87
|
+
- { value: "2026-04-31", note: "April has 30 days — invalid" }
|
|
88
|
+
- { value: "2026-12-31 23:59:59", note: "Last second of the year — rollover boundary" }
|
|
89
|
+
- { value: "2026-03-08 02:30:00 US/Eastern", note: "During DST spring-forward gap — this time does not exist" }
|
|
90
|
+
|
|
91
|
+
- name: Selections (Dropdowns, Radio Buttons, Multi-selects)
|
|
92
|
+
too_big:
|
|
93
|
+
- { value: "Select all options in a multi-select", note: "Maximum selection — does the UI and API handle it?" }
|
|
94
|
+
- { value: "Select 100+ items in a list and perform bulk action", note: "Bulk operation at scale" }
|
|
95
|
+
- { value: "Submit with a value not in the dropdown (tampered request)", note: "Server-side validation of enum values" }
|
|
96
|
+
too_small:
|
|
97
|
+
- { value: "No selection (skip required dropdown)", note: "Empty selection — validation check" }
|
|
98
|
+
- { value: "Deselect all in a multi-select that requires at least one", note: "Below minimum selection" }
|
|
99
|
+
- { value: "Submit form without touching the dropdown (default placeholder)", note: "Default value handling" }
|
|
100
|
+
just_right:
|
|
101
|
+
- { value: "Select one typical option", note: "Happy path — single valid selection" }
|
|
102
|
+
- { value: "Select 2-3 options in a multi-select", note: "Typical multi-selection" }
|
|
103
|
+
- { value: "Change selection from A to B before submitting", note: "Changed mind — state update" }
|
|
104
|
+
|
|
105
|
+
- name: File Sizes and Uploads
|
|
106
|
+
too_big:
|
|
107
|
+
- { value: "100MB+ file", note: "Exceeds typical upload limits — timeout, memory, error handling" }
|
|
108
|
+
- { value: "File with 10000-character filename", note: "Filename length limit on filesystem" }
|
|
109
|
+
- { value: "ZIP bomb (small file that expands to GB)", note: "Decompression-based denial of service" }
|
|
110
|
+
- { value: "Image with 50000x50000 pixel dimensions", note: "Memory exhaustion during image processing" }
|
|
111
|
+
too_small:
|
|
112
|
+
- { value: "0-byte empty file", note: "Empty file — does the system accept and handle it?" }
|
|
113
|
+
- { value: "1-byte file", note: "Minimum viable file — corrupt or valid?" }
|
|
114
|
+
- { value: "File with no extension", note: "Missing file type — how is it classified?" }
|
|
115
|
+
just_right:
|
|
116
|
+
- { value: "500KB JPEG image", note: "Typical photo upload" }
|
|
117
|
+
- { value: "50KB PDF document", note: "Typical document upload" }
|
|
118
|
+
- { value: "2KB CSV file with 50 rows", note: "Typical data import file" }
|
|
119
|
+
|
|
120
|
+
application_process:
|
|
121
|
+
description: "How to apply Goldilocks systematically during exploratory testing."
|
|
122
|
+
steps:
|
|
123
|
+
- "Identify every input on the page (visible fields, hidden parameters, URL params, file uploads)."
|
|
124
|
+
- "For each input, determine its expected data type (number, string, date, selection, file)."
|
|
125
|
+
- "Generate at least one 'too big,' one 'too small,' and one 'just right' value from the category above."
|
|
126
|
+
- "Enter each value, submit, and observe: Does validation catch it? Does the UI handle it? Does the data persist correctly?"
|
|
127
|
+
- "Pay special attention to what happens AFTER submission — does the data display correctly on other pages, in reports, in exports?"
|
|
128
|
+
- "Combine Goldilocks with other inputs — one field too big while another is too small."
|
|
129
|
+
|
|
130
|
+
when_to_use:
|
|
131
|
+
- "Every time you encounter an input field — Goldilocks takes 30 seconds and catches real bugs."
|
|
132
|
+
- "During initial exploration of a new form or feature."
|
|
133
|
+
- "When boundary values are not documented — Goldilocks helps discover the actual limits."
|
|
134
|
+
- "When testing calculations — extreme values reveal overflow, precision, and rounding bugs."
|
|
135
|
+
- "When combined with FedEx Tour — enter extreme data and track it through the entire system."
|
|
136
|
+
|
|
137
|
+
gotchas:
|
|
138
|
+
- "Too small often catches more bugs than too big — developers think about maximum limits but forget about zero, empty, and negative."
|
|
139
|
+
- "Just right is not always safe — a typical name like O'Brien has an apostrophe that breaks SQL and display."
|
|
140
|
+
- "Test Goldilocks on BOTH client and server side — bypass client validation to send extreme values directly to the API."
|
|
141
|
+
- "Combine categories — enter a too-big number in a too-small form field with a too-big date in the same submission."
|
|
142
|
+
- "The 'just right' values should include realistic data from the target domain, not just generic test data."
|
|
143
|
+
- "File uploads are often forgotten — apply Goldilocks to file size, filename length, file type, and file content."
|
|
@@ -0,0 +1,207 @@
|
|
|
1
|
+
id: heuristic-rcrcrc
|
|
2
|
+
version: "0.1.0"
|
|
3
|
+
type: heuristic
|
|
4
|
+
name: "RCRCRC(R) — Regression Testing Focus Areas"
|
|
5
|
+
description: >
|
|
6
|
+
A mnemonic for deciding what to test during regression testing: Recent, Core,
|
|
7
|
+
Risky, Configuration, Repaired, Chronic. Extended with Revenue (from Richard
|
|
8
|
+
Bradshaw) as the seventh R. Each letter identifies a category of features
|
|
9
|
+
that deserve priority attention after changes are deployed.
|
|
10
|
+
author: "Karen N. Johnson"
|
|
11
|
+
source: "Karen N. Johnson — RCRCRC regression testing heuristic"
|
|
12
|
+
tags: [regression, prioritization, change-management]
|
|
13
|
+
domains: [all]
|
|
14
|
+
priority: high
|
|
15
|
+
added: "2026-03-28"
|
|
16
|
+
|
|
17
|
+
content:
|
|
18
|
+
summary: >
|
|
19
|
+
When you cannot test everything after a change (and you never can), RCRCRC
|
|
20
|
+
tells you WHERE to focus. Each letter identifies a category of the product
|
|
21
|
+
that is more likely to contain regression bugs. Prioritize testing in these
|
|
22
|
+
areas first, then expand coverage if time permits. The extended version
|
|
23
|
+
(RCRCRCR) adds Revenue — features that generate business income and must
|
|
24
|
+
never break.
|
|
25
|
+
|
|
26
|
+
mnemonic:
|
|
27
|
+
- name: Recent
|
|
28
|
+
letter: R
|
|
29
|
+
description: "New code or recently changed features — fresh code has fresh bugs."
|
|
30
|
+
why_it_matters: >
|
|
31
|
+
Code that was just written or modified has not been battle-tested yet.
|
|
32
|
+
New features, recent refactors, and recently merged pull requests are
|
|
33
|
+
the most likely places for regressions to appear.
|
|
34
|
+
what_to_test:
|
|
35
|
+
- "Features added or modified in this sprint or release."
|
|
36
|
+
- "Files with the most recent commits (check git log)."
|
|
37
|
+
- "Recently merged pull requests — especially large ones."
|
|
38
|
+
- "New integrations or dependency upgrades."
|
|
39
|
+
- "Features behind newly toggled feature flags."
|
|
40
|
+
questions:
|
|
41
|
+
- "What changed in this release?"
|
|
42
|
+
- "Which files were touched in the last sprint?"
|
|
43
|
+
- "Are there any new feature flags that were just enabled?"
|
|
44
|
+
|
|
45
|
+
- name: Core
|
|
46
|
+
letter: C
|
|
47
|
+
description: "Features critical to the product's purpose — the reason the product exists."
|
|
48
|
+
why_it_matters: >
|
|
49
|
+
If core features break, the product is fundamentally broken. These are
|
|
50
|
+
the features that users bought the product for and use every day. A bug
|
|
51
|
+
in a core feature has maximum user impact.
|
|
52
|
+
what_to_test:
|
|
53
|
+
- "The product's primary value proposition (search for Google, payments for Stripe, messaging for Slack)."
|
|
54
|
+
- "The top 5 most-used features from analytics."
|
|
55
|
+
- "Critical user journeys — signup, login, primary workflow, checkout."
|
|
56
|
+
- "Features mentioned in marketing as key differentiators."
|
|
57
|
+
- "Features that, if broken, would generate immediate support tickets."
|
|
58
|
+
questions:
|
|
59
|
+
- "What would users complain about first if it broke?"
|
|
60
|
+
- "What features define this product?"
|
|
61
|
+
- "What are the top 5 user journeys by frequency?"
|
|
62
|
+
|
|
63
|
+
- name: Risky
|
|
64
|
+
letter: R
|
|
65
|
+
description: "Complex areas with many dependencies, integrations, or known fragility."
|
|
66
|
+
why_it_matters: >
|
|
67
|
+
Complexity breeds bugs. Features with many dependencies, complex
|
|
68
|
+
algorithms, heavy integrations, or historically fragile code are more
|
|
69
|
+
likely to break when anything in their dependency chain changes.
|
|
70
|
+
what_to_test:
|
|
71
|
+
- "Features with the most external dependencies (payment gateways, third-party APIs)."
|
|
72
|
+
- "Complex algorithms (pricing engines, recommendation systems, search ranking)."
|
|
73
|
+
- "Features with many database joins or complex queries."
|
|
74
|
+
- "Code written under time pressure or technical debt."
|
|
75
|
+
- "Features with high cyclomatic complexity."
|
|
76
|
+
- "Areas where junior developers made significant contributions (higher risk of overlooked edge cases)."
|
|
77
|
+
questions:
|
|
78
|
+
- "Which features have the most moving parts?"
|
|
79
|
+
- "What integrations could fail independently?"
|
|
80
|
+
- "Where is the most complex business logic?"
|
|
81
|
+
- "Who wrote this code and how experienced were they with this codebase?"
|
|
82
|
+
|
|
83
|
+
- name: Configuration
|
|
84
|
+
letter: C
|
|
85
|
+
description: "Features affected by settings, environments, feature flags, and deployment configurations."
|
|
86
|
+
why_it_matters: >
|
|
87
|
+
Configuration changes are silent — they do not show up in code diffs
|
|
88
|
+
but can dramatically change behavior. Environment differences between
|
|
89
|
+
dev, staging, and production cause bugs that only appear in production.
|
|
90
|
+
what_to_test:
|
|
91
|
+
- "Features controlled by feature flags — test both on and off states."
|
|
92
|
+
- "Environment-specific behavior (dev vs. staging vs. production)."
|
|
93
|
+
- "Locale and language settings — does the app work in all configured locales?"
|
|
94
|
+
- "User role and permission configurations — test each role."
|
|
95
|
+
- "Database connection strings, API keys, and service URLs."
|
|
96
|
+
- "Browser and device configurations that the product claims to support."
|
|
97
|
+
- "Notification settings, email templates, and communication preferences."
|
|
98
|
+
questions:
|
|
99
|
+
- "What feature flags changed in this release?"
|
|
100
|
+
- "Are there environment-specific configurations that differ between staging and production?"
|
|
101
|
+
- "What user roles exist and have their permissions changed?"
|
|
102
|
+
|
|
103
|
+
- name: Repaired
|
|
104
|
+
letter: R
|
|
105
|
+
description: "Recently fixed bugs — the fix itself may introduce a new regression."
|
|
106
|
+
why_it_matters: >
|
|
107
|
+
Bug fixes are code changes, and code changes introduce risk. The fix
|
|
108
|
+
for bug A might break feature B. Additionally, the area where the bug
|
|
109
|
+
existed was already proven fragile — more bugs likely hide nearby.
|
|
110
|
+
what_to_test:
|
|
111
|
+
- "The exact scenario from the original bug report — does the fix actually work?"
|
|
112
|
+
- "Related scenarios near the fix — did the fix break neighboring functionality?"
|
|
113
|
+
- "The same bug in other similar features — if it was wrong here, it might be wrong everywhere."
|
|
114
|
+
- "Edge cases around the fix — the developer may have fixed the reported case but missed variations."
|
|
115
|
+
- "The fix under different conditions (different user roles, different data, different browsers)."
|
|
116
|
+
questions:
|
|
117
|
+
- "What bugs were fixed in this release?"
|
|
118
|
+
- "Do the original bug reports have clear reproduction steps I can re-run?"
|
|
119
|
+
- "Are there similar features that might have the same underlying bug?"
|
|
120
|
+
|
|
121
|
+
- name: Chronic
|
|
122
|
+
letter: C
|
|
123
|
+
description: "Areas with a history of recurring issues — some code is perpetually broken."
|
|
124
|
+
why_it_matters: >
|
|
125
|
+
Bug clusters are real. Some areas of the codebase are structurally
|
|
126
|
+
fragile and produce bugs repeatedly. These chronic problem areas
|
|
127
|
+
deserve extra scrutiny every release because they are likely to
|
|
128
|
+
break again.
|
|
129
|
+
what_to_test:
|
|
130
|
+
- "Features that have had 3+ bugs filed in the last 6 months."
|
|
131
|
+
- "Areas flagged as technical debt in team discussions."
|
|
132
|
+
- "Features that have been 'fixed' multiple times for the same issue."
|
|
133
|
+
- "Code with low test coverage (check coverage reports)."
|
|
134
|
+
- "Features that frequently appear in production incident reports."
|
|
135
|
+
- "Legacy code that nobody on the current team wrote or fully understands."
|
|
136
|
+
questions:
|
|
137
|
+
- "Which areas of the product have the highest bug density historically?"
|
|
138
|
+
- "Are there any features the team jokes about being 'always broken'?"
|
|
139
|
+
- "What shows up repeatedly in retrospectives as a quality concern?"
|
|
140
|
+
|
|
141
|
+
- name: Revenue (Extended)
|
|
142
|
+
letter: R
|
|
143
|
+
description: "Features that directly generate business revenue — if these break, the business loses money."
|
|
144
|
+
why_it_matters: >
|
|
145
|
+
Added by Richard Bradshaw as the seventh R. Revenue-generating features
|
|
146
|
+
have a direct financial impact when they fail. A broken checkout costs
|
|
147
|
+
real money every minute it is down. These features justify the highest
|
|
148
|
+
testing priority regardless of recent changes.
|
|
149
|
+
what_to_test:
|
|
150
|
+
- "Payment and checkout flows — end to end."
|
|
151
|
+
- "Subscription and billing management."
|
|
152
|
+
- "Pricing display and calculation accuracy."
|
|
153
|
+
- "Promotional codes, discounts, and special offers."
|
|
154
|
+
- "Upsell and cross-sell features."
|
|
155
|
+
- "Trial-to-paid conversion flows."
|
|
156
|
+
- "Invoice generation and receipt delivery."
|
|
157
|
+
- "Refund and cancellation processes."
|
|
158
|
+
questions:
|
|
159
|
+
- "Which features directly generate revenue?"
|
|
160
|
+
- "What is the per-minute cost of downtime for the checkout flow?"
|
|
161
|
+
- "Are pricing calculations accurate across all products and currencies?"
|
|
162
|
+
|
|
163
|
+
application_process:
|
|
164
|
+
description: "How to use RCRCRC(R) to prioritize regression testing."
|
|
165
|
+
steps:
|
|
166
|
+
- "List all features or areas affected by the release (use git diff, release notes, sprint board)."
|
|
167
|
+
- "For each RCRCRC(R) category, identify which features or areas qualify."
|
|
168
|
+
- "Features that appear in multiple categories get highest priority (e.g., a recently changed core feature that handles revenue)."
|
|
169
|
+
- "Allocate testing time proportionally — features in 3+ categories get tested first and deepest."
|
|
170
|
+
- "For each prioritized area, apply appropriate testing techniques (boundary testing, error guessing, tours)."
|
|
171
|
+
- "Document which RCRCRC(R) categories drove your test selection — this helps justify coverage decisions."
|
|
172
|
+
|
|
173
|
+
priority_matrix:
|
|
174
|
+
description: "Score each feature area against RCRCRC(R) — higher scores mean higher test priority."
|
|
175
|
+
scoring:
|
|
176
|
+
- "Award 1 point for each RCRCRC(R) category the feature matches."
|
|
177
|
+
- "Features scoring 4+ points: test first and deepest."
|
|
178
|
+
- "Features scoring 2-3 points: test thoroughly."
|
|
179
|
+
- "Features scoring 1 point: basic smoke test."
|
|
180
|
+
- "Features scoring 0 points: skip unless time permits."
|
|
181
|
+
example:
|
|
182
|
+
feature: "Checkout flow after payment provider migration"
|
|
183
|
+
recent: "Yes — payment provider changed this sprint (1 point)"
|
|
184
|
+
core: "Yes — checkout is a primary user journey (1 point)"
|
|
185
|
+
risky: "Yes — external payment integration, complex flow (1 point)"
|
|
186
|
+
configuration: "Yes — payment provider API keys changed (1 point)"
|
|
187
|
+
repaired: "No — no recent bugs fixed here (0 points)"
|
|
188
|
+
chronic: "No — checkout has been stable historically (0 points)"
|
|
189
|
+
revenue: "Yes — directly generates all revenue (1 point)"
|
|
190
|
+
total: "5/7 — highest priority, test exhaustively"
|
|
191
|
+
|
|
192
|
+
when_to_use:
|
|
193
|
+
- "After every deployment or release — the primary regression prioritization tool."
|
|
194
|
+
- "During sprint planning — identify which areas need regression testing based on planned changes."
|
|
195
|
+
- "When time is limited — RCRCRC(R) tells you where the highest-risk areas are."
|
|
196
|
+
- "After hotfixes — the Repaired category is especially important."
|
|
197
|
+
- "Before major releases — score every feature area to create a risk-ranked test plan."
|
|
198
|
+
- "During incident response — check if the broken area scores high on Chronic."
|
|
199
|
+
|
|
200
|
+
gotchas:
|
|
201
|
+
- "RCRCRC is for prioritization, not exclusion — low-scoring areas still deserve occasional testing."
|
|
202
|
+
- "Recent does not only mean 'this sprint' — consider changes in the last 2-3 releases that have not been thoroughly tested."
|
|
203
|
+
- "Risky and Chronic overlap but are different — Risky is about inherent complexity, Chronic is about historical evidence of bugs."
|
|
204
|
+
- "Revenue features should be tested every release, even if nothing changed — the cost of a missed regression is too high."
|
|
205
|
+
- "Configuration changes are invisible in code reviews — always ask 'did any configuration change?' before a release."
|
|
206
|
+
- "Use the priority matrix as a communication tool with stakeholders — it explains WHY you chose to test what you tested."
|
|
207
|
+
- "Combine with SFDIPOT — use RCRCRC(R) to decide WHERE to test, then SFDIPOT to decide WHAT to test within that area."
|