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,178 @@
1
+ # Bug Report
2
+
3
+ ## Title
4
+
5
+ `[Component] fails [Condition] causing [Impact]`
6
+
7
+ > _Example: [Login Form] fails [when password contains special characters] causing [authentication error and user lockout]_
8
+
9
+ ---
10
+
11
+ ## Severity
12
+
13
+ > Select one. See definitions below.
14
+
15
+ - [ ] **Critical**
16
+ - [ ] **High**
17
+ - [ ] **Medium**
18
+ - [ ] **Low**
19
+
20
+ ### Severity Level Definitions
21
+
22
+ | Level | Definition | Examples |
23
+ |----------|----------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------|
24
+ | Critical | System down, data loss, security breach. Blocks all users immediately. | Payment gateway crashes on all transactions; user passwords exposed in API response; database corruption losing customer orders. |
25
+ | High | Major feature broken, many users affected. No reasonable workaround. | Checkout fails for all credit card payments; search returns zero results for every query; login broken on mobile devices. |
26
+ | Medium | Partial break, workaround exists. Some users affected under certain paths. | Discount code applies twice if user clicks fast; filter resets after pagination; profile photo upload fails on Safari only. |
27
+ | Low | Cosmetic issue, rare edge case. Minimal user or business impact. | Footer alignment off by 2px on wide screens; tooltip text truncated in German locale; hover state missing on disabled button. |
28
+
29
+ > **Note: When in doubt, go one level LOWER. Severity inflation destroys credibility.** A bug report rated "Critical" that turns out to be cosmetic undermines every future report you file. Reserve Critical for genuine emergencies. If you hesitate between two levels, pick the lower one and let the evidence speak for itself.
30
+
31
+ ---
32
+
33
+ ## URL
34
+
35
+ `[URL where the bug was found]`
36
+
37
+ ## Environment
38
+
39
+ | Property | Value |
40
+ |-----------|---------------------------|
41
+ | Browser | [e.g., Chrome 125.0] |
42
+ | Viewport | [e.g., 1920x1080] |
43
+ | OS | [e.g., macOS 15.x] |
44
+ | Auth | [e.g., logged in as X] |
45
+ | Device | [e.g., Desktop / Mobile] |
46
+
47
+ ---
48
+
49
+ ## Expected Behavior
50
+
51
+ _What should happen according to requirements, conventions, or reasonable user expectations._
52
+
53
+ > [Describe the expected outcome clearly.]
54
+
55
+ ## Actual Behavior
56
+
57
+ _What actually happens instead._
58
+
59
+ > [Describe the actual outcome. Be precise -- include error messages verbatim if applicable.]
60
+
61
+ ---
62
+
63
+ ## Steps to Reproduce
64
+
65
+ 1. Navigate to `[URL]`
66
+ 2. [Action 2]
67
+ 3. [Action 3]
68
+ 4. [Action 4]
69
+ 5. Observe: [what goes wrong]
70
+
71
+ > _Reproduction rate: [Always / Intermittent (~X%) / Once]_
72
+
73
+ ---
74
+
75
+ ## Business Impact
76
+
77
+ > This section is **mandatory**. Every bug exists in a business context. Articulating impact helps engineering prioritize correctly and helps stakeholders understand the risk without needing to read technical details.
78
+
79
+ ### Revenue Impact
80
+
81
+ > [Does this bug prevent purchases, cause incorrect charges, block upgrades, or reduce conversion? Quantify if possible -- e.g., "Blocks all guest checkout, which represents ~30% of orders."]
82
+
83
+ ### Trust Impact
84
+
85
+ > [Would a user lose confidence in the product? Would they contact support, leave a negative review, or churn? e.g., "User sees a $0.00 balance briefly before correct amount loads -- creates panic."]
86
+
87
+ ### Regulatory Risk
88
+
89
+ > [Does this violate any compliance requirements? Specify the regulation. e.g., "Credit card number visible in URL query string -- PCI DSS violation." If none, write "No known regulatory risk."]
90
+ >
91
+ > Common frameworks to consider: SOX, PCI DSS, GDPR, CCPA, HIPAA, WCAG 2.1 AA, CAN-SPAM, KYC/AML, Regulation E.
92
+
93
+ ### Data Risk
94
+
95
+ > [Is data corrupted, lost, or exposed? e.g., "Order total saved as $0 in database when coupon equals cart value -- data integrity failure." If none, write "No data risk identified."]
96
+
97
+ ### Scale
98
+
99
+ > [How many users are affected and under what conditions? e.g., "All users on iOS Safari 17+ (~18% of mobile traffic)" or "Only affects accounts created before the migration on 2025-01-15 (~200 accounts)."]
100
+
101
+ ---
102
+
103
+ ## Risk Priority
104
+
105
+ > Use this matrix to communicate urgency objectively.
106
+
107
+ | Factor | Rating | Justification |
108
+ |-------------|------------------|----------------------------------------------------|
109
+ | Likelihood | High / Med / Low | [How likely is a user to hit this? Every time? Rare edge case?] |
110
+ | Impact | High / Med / Low | [How bad is it when they do? Data loss? Mild annoyance?] |
111
+ | **Risk** | **[Result]** | **Risk = Likelihood x Impact** (see matrix below) |
112
+
113
+ ### Risk Matrix
114
+
115
+ | | **Impact: Low** | **Impact: Med** | **Impact: High** |
116
+ |--------------------|-----------------|-----------------|-------------------|
117
+ | **Likelihood: High** | Medium | High | Critical |
118
+ | **Likelihood: Med** | Low | Medium | High |
119
+ | **Likelihood: Low** | Low | Low | Medium |
120
+
121
+ ---
122
+
123
+ ## Recommended Fix Priority
124
+
125
+ > **Priority: [P0 / P1 / P2 / P3]**
126
+
127
+ | Priority | Meaning | Typical SLA |
128
+ |----------|--------------------------------------|----------------------|
129
+ | P0 | Fix immediately, interrupt sprint | Hours |
130
+ | P1 | Fix this sprint | Days |
131
+ | P2 | Fix next sprint | 1-2 weeks |
132
+ | P3 | Backlog, fix when convenient | When capacity allows |
133
+
134
+ **Justification:** [Explain why this priority level is appropriate given the risk assessment and business impact above. e.g., "Risk is High (likely + revenue-impacting), but a workaround exists (users can switch payment method), so P1 rather than P0."]
135
+
136
+ ---
137
+
138
+ ## Impact
139
+
140
+ ### User Impact
141
+
142
+ > [How does this affect the end user? Can they complete their task? What is the degraded experience?]
143
+
144
+ ### Business Impact Summary
145
+
146
+ > [One-sentence summary referencing the detailed Business Impact section above. e.g., "Blocks ~30% of revenue through guest checkout with no workaround."]
147
+
148
+ ---
149
+
150
+ ## Evidence
151
+
152
+ ### Screenshots
153
+
154
+ > _Path: `output/sessions/[session-id]/screenshots/[filename].png`_
155
+
156
+ ### Console Errors
157
+
158
+ ```
159
+ [Paste any relevant console errors here]
160
+ ```
161
+
162
+ ### Network Failures
163
+
164
+ ```
165
+ [Paste any failed requests -- method, URL, status code, response body excerpt]
166
+ ```
167
+
168
+ ### Additional Logs
169
+
170
+ ```
171
+ [Any other diagnostic output -- application logs, state dumps, etc.]
172
+ ```
173
+
174
+ ---
175
+
176
+ ## Additional Context
177
+
178
+ > [Any other relevant information: related bugs, recent deploys, feature flags, user reports, etc.]
@@ -0,0 +1,70 @@
1
+ # Coverage Map
2
+
3
+ ## Session Reference
4
+
5
+ | Property | Value |
6
+ |------------|--------------------------------|
7
+ | Session ID | [e.g., SESSION-2026-03-28-001] |
8
+ | Target | [application or feature name] |
9
+ | Date | [YYYY-MM-DD] |
10
+
11
+ ---
12
+
13
+ ## Overall Coverage
14
+
15
+ | Area | Status | Heuristics Applied | Bugs Found | Notes |
16
+ |------|--------|--------------------|------------|-------|
17
+ | [Area 1] | tested / partial / not-tested | [list] | 0 | [notes] |
18
+ | [Area 2] | tested / partial / not-tested | [list] | 0 | [notes] |
19
+ | [Area 3] | tested / partial / not-tested | [list] | 0 | [notes] |
20
+
21
+ ### Status Legend
22
+
23
+ - **tested** -- Area was fully explored with the planned heuristics.
24
+ - **partial** -- Area was visited but not all heuristics or paths were exercised.
25
+ - **not-tested** -- Area was in scope but was not reached during the session.
26
+
27
+ ---
28
+
29
+ ## SFDIPOT Dimension Coverage
30
+
31
+ _Coverage across each dimension of the SFDIPOT heuristic._
32
+
33
+ | Dimension | Description | Status | Bugs Found | Notes |
34
+ |--------------|------------------------------------|--------|------------|-------|
35
+ | **Structure** | UI layout, elements, visual hierarchy | tested / partial / not-tested | 0 | [notes] |
36
+ | **Function** | Features work as expected | tested / partial / not-tested | 0 | [notes] |
37
+ | **Data** | Input handling, storage, retrieval | tested / partial / not-tested | 0 | [notes] |
38
+ | **Interface** | Interactions between components/APIs | tested / partial / not-tested | 0 | [notes] |
39
+ | **Platform** | Browser, OS, device compatibility | tested / partial / not-tested | 0 | [notes] |
40
+ | **Operations** | Performance, logging, error handling | tested / partial / not-tested | 0 | [notes] |
41
+ | **Time** | Timeouts, sessions, scheduling | tested / partial / not-tested | 0 | [notes] |
42
+
43
+ ---
44
+
45
+ ## Page / Feature Coverage
46
+
47
+ _Detailed tracking of individual pages or features tested._
48
+
49
+ | Page / Feature | URL / Path | Status | Actions Tested | Bugs Found | Notes |
50
+ |----------------|------------|--------|----------------|------------|-------|
51
+ | [e.g., Login Page] | /login | tested / partial / not-tested | [e.g., valid login, invalid password, empty fields] | 0 | [notes] |
52
+ | [e.g., Dashboard] | /dashboard | tested / partial / not-tested | [e.g., load, filter, sort] | 0 | [notes] |
53
+ | [e.g., Settings] | /settings | tested / partial / not-tested | [e.g., update profile, change password] | 0 | [notes] |
54
+
55
+ ---
56
+
57
+ ## Test Tour Coverage
58
+
59
+ _Tracking which exploration tours were executed and their outcomes._
60
+
61
+ | Tour | Description | Status | Areas Covered | Bugs Found | Notes |
62
+ |------|-------------|--------|---------------|------------|-------|
63
+ | **Guidebook Tour** | Follow documentation, verify stated behaviors | completed / partial / not-started | [areas] | 0 | [notes] |
64
+ | **Money Tour** | Test the most critical business features | completed / partial / not-started | [areas] | 0 | [notes] |
65
+ | **Landmark Tour** | Hit all major navigation points | completed / partial / not-started | [areas] | 0 | [notes] |
66
+ | **FedEx Tour** | Follow data through the entire system | completed / partial / not-started | [areas] | 0 | [notes] |
67
+ | **Garbage Collector Tour**| Test least-used features | completed / partial / not-started | [areas] | 0 | [notes] |
68
+ | **Bad Neighborhood Tour** | Revisit areas known for previous bugs | completed / partial / not-started | [areas] | 0 | [notes] |
69
+ | **Supermodel Tour** | Test with various screen sizes and viewports | completed / partial / not-started | [areas] | 0 | [notes] |
70
+ | **Antisocial Tour** | Provide invalid, unexpected, or hostile inputs | completed / partial / not-started | [areas] | 0 | [notes] |
@@ -0,0 +1,77 @@
1
+ # Session Charter
2
+
3
+ ```
4
+ CHARTER: Explore [target area]
5
+ WITH: [resources/tools/heuristics]
6
+ TO DISCOVER: [what we're looking for]
7
+ TIME BOX: [duration]
8
+ PRIORITY: [P0/P1/P2]
9
+ ```
10
+
11
+ ---
12
+
13
+ ## Mission
14
+
15
+ _Clear, one-sentence statement of what this session aims to accomplish._
16
+
17
+ > [Describe the primary testing objective for this session.]
18
+
19
+ ## Areas to Explore
20
+
21
+ _Specific pages, features, or flows to cover during this session._
22
+
23
+ - [ ] [Area 1 - e.g., Login flow]
24
+ - [ ] [Area 2 - e.g., Dashboard rendering]
25
+ - [ ] [Area 3 - e.g., Form validation on settings page]
26
+
27
+ ## Heuristics to Apply
28
+
29
+ _Testing heuristics selected from the knowledge base to guide exploration._
30
+
31
+ - [ ] **SFDIPOT**: Structure, Function, Data, Interface, Platform, Operations, Time
32
+ - [ ] **Consistency**: Compare behavior across similar features
33
+ - [ ] **CRUD**: Create, Read, Update, Delete operations
34
+ - [ ] **Boundaries**: Edge values, empty states, limits
35
+ - [ ] **Interruptions**: Cancel mid-flow, navigate away, timeout
36
+ - [ ] **Input Variation**: Special characters, long strings, empty fields, SQL injection patterns
37
+ - [ ] [Add or remove heuristics as needed]
38
+
39
+ ## Test Tours Selected
40
+
41
+ _Exploration strategies from the tours framework to follow._
42
+
43
+ - [ ] **Guidebook Tour**: Follow documentation, verify stated behaviors
44
+ - [ ] **Money Tour**: Test the most critical business features
45
+ - [ ] **Landmark Tour**: Hit all major navigation points
46
+ - [ ] **FedEx Tour**: Follow data through the entire system
47
+ - [ ] **Garbage Collector Tour**: Test least-used features
48
+ - [ ] **Bad Neighborhood Tour**: Revisit areas known for previous bugs
49
+ - [ ] [Add or remove tours as needed]
50
+
51
+ ## Focus Constraints
52
+
53
+ _Boundaries for the session -- what is in scope and what is explicitly out of scope._
54
+
55
+ ### In Scope
56
+
57
+ - [Feature/area 1]
58
+ - [Feature/area 2]
59
+
60
+ ### Out of Scope
61
+
62
+ - [Feature/area excluded and reason]
63
+ - [Feature/area excluded and reason]
64
+
65
+ ## Environment Notes
66
+
67
+ _Technical details about the testing environment._
68
+
69
+ | Property | Value |
70
+ |----------------|--------------------------------|
71
+ | URL | [target URL] |
72
+ | Browser | [e.g., Chrome 125] |
73
+ | Viewport | [e.g., 1920x1080] |
74
+ | OS | [e.g., macOS 15.x] |
75
+ | Auth State | [e.g., logged in as test user] |
76
+ | Test Data | [any pre-conditions or seeds] |
77
+ | Tools Used | [Playwright, DevTools, etc.] |
@@ -0,0 +1,112 @@
1
+ # Session Report
2
+
3
+ ## Session Metadata
4
+
5
+ | Property | Value |
6
+ |------------|--------------------------------|
7
+ | Session ID | [e.g., SESSION-2026-03-28-001] |
8
+ | Target | [application or feature name] |
9
+ | URL | [target URL] |
10
+ | Date | [YYYY-MM-DD] |
11
+ | Duration | [e.g., 45 minutes] |
12
+ | Tester | Claude AI |
13
+ | Charter | [link to charter file] |
14
+
15
+ ---
16
+
17
+ ## Charter Summary
18
+
19
+ > [One-paragraph summary of the session charter: what was explored, with what tools/heuristics, and what we hoped to discover.]
20
+
21
+ ---
22
+
23
+ ## Summary Stats
24
+
25
+ | Metric | Count |
26
+ |------------------------|-------|
27
+ | Pages Explored | 0 |
28
+ | Actions Performed | 0 |
29
+ | Bugs Found -- Critical | 0 |
30
+ | Bugs Found -- High | 0 |
31
+ | Bugs Found -- Medium | 0 |
32
+ | Bugs Found -- Low | 0 |
33
+ | **Total Bugs** | **0** |
34
+
35
+ ---
36
+
37
+ ## Coverage Map
38
+
39
+ _High-level view of what was tested. For full details see the dedicated coverage map file._
40
+
41
+ | Area | Status | Heuristics Applied | Bugs Found | Notes |
42
+ |------|--------|--------------------|------------|-------|
43
+ | [Area 1] | tested / partial / not-tested | [list] | 0 | [notes] |
44
+ | [Area 2] | tested / partial / not-tested | [list] | 0 | [notes] |
45
+ | [Area 3] | tested / partial / not-tested | [list] | 0 | [notes] |
46
+
47
+ ---
48
+
49
+ ## Bugs Found
50
+
51
+ _Each bug links to its individual report in `output/bugs/`._
52
+
53
+ | # | ID | Title | Severity | Report |
54
+ |---|-----|-------|----------|--------|
55
+ | 1 | [BUG-XXX] | [Component] fails [Condition] causing [Impact] | Critical/High/Medium/Low | [link] |
56
+
57
+ > _If no bugs were found, state: "No bugs were found during this session."_
58
+
59
+ ---
60
+
61
+ ## Observations
62
+
63
+ _Things noticed during testing that are not bugs but may be worth discussing._
64
+
65
+ - [Observation 1 -- e.g., page load time felt slow on dashboard but did not exceed threshold]
66
+ - [Observation 2 -- e.g., tooltip text seems inconsistent with other similar features]
67
+ - [Observation 3]
68
+
69
+ ---
70
+
71
+ ## Questions
72
+
73
+ _Unclear behaviors that need human review to determine if they are bugs or intended._
74
+
75
+ - [ ] [Question 1 -- e.g., Is the empty state message on /reports intentional when no data exists?]
76
+ - [ ] [Question 2 -- e.g., Should the "Save" button remain enabled when no changes have been made?]
77
+ - [ ] [Question 3]
78
+
79
+ ---
80
+
81
+ ## Areas Not Tested
82
+
83
+ _Parts of the charter or scope that were not covered, with reasons._
84
+
85
+ | Area | Reason |
86
+ |------|--------|
87
+ | [Area 1] | [e.g., Blocked by authentication issue] |
88
+ | [Area 2] | [e.g., Time box expired before reaching this area] |
89
+ | [Area 3] | [e.g., Feature not yet deployed to test environment] |
90
+
91
+ ---
92
+
93
+ ## Recommendations
94
+
95
+ _What should be tested next, based on findings from this session._
96
+
97
+ - [ ] [Recommendation 1 -- e.g., Deep-dive into payment flow edge cases]
98
+ - [ ] [Recommendation 2 -- e.g., Regression test the login form after fix for BUG-001]
99
+ - [ ] [Recommendation 3 -- e.g., Cross-browser testing on Safari for the dashboard]
100
+
101
+ ---
102
+
103
+ ## Session Quality Metrics
104
+
105
+ _How time was spent during this session._
106
+
107
+ | Activity | % of Time | Notes |
108
+ |---------------------|-----------|--------------------------------|
109
+ | Exploration | 0% | [Navigating and testing] |
110
+ | Bug Investigation | 0% | [Reproducing and documenting] |
111
+ | Setup | 0% | [Environment, auth, tooling] |
112
+ | **Total** | **100%** | |
@@ -0,0 +1 @@
1
+ #!/usr/bin/env node