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,203 @@
1
+ id: technique-boundary-testing
2
+ version: "0.1.0"
3
+ type: technique
4
+ name: "Boundary Value Analysis"
5
+ description: >
6
+ A systematic technique for testing at and around the edges of input
7
+ domains. Bugs cluster at boundaries — the transition points where
8
+ behavior changes. Test the boundary itself, one below, and one above.
9
+ author: "Classic testing technique"
10
+ source: "Adapted from multiple sources for exploratory testing context"
11
+ tags: [boundaries, edge-cases, input-testing]
12
+ domains: [all]
13
+ priority: high
14
+ added: "2026-03-28"
15
+
16
+ content:
17
+ summary: >
18
+ For every input, there are boundaries where the system's behavior changes.
19
+ Testing at those exact boundaries (and immediately on either side) catches
20
+ off-by-one errors, incorrect comparisons, and missed edge cases. Apply this
21
+ technique to every input field, parameter, and constraint you encounter.
22
+
23
+ strategies:
24
+ - name: Exact Boundaries
25
+ description: "Test the precise values where behavior is defined to change."
26
+ approach:
27
+ - "Identify the specified minimum and maximum values."
28
+ - "Test at min, min-1, min+1."
29
+ - "Test at max, max-1, max+1."
30
+ - "Test at zero (even if not a boundary — it often is implicitly)."
31
+ examples:
32
+ - input: "Age field (18-120)"
33
+ test_values:
34
+ - { value: 17, expected: "Rejected — below minimum" }
35
+ - { value: 18, expected: "Accepted — minimum boundary" }
36
+ - { value: 19, expected: "Accepted — just above minimum" }
37
+ - { value: 119, expected: "Accepted — just below maximum" }
38
+ - { value: 120, expected: "Accepted — maximum boundary" }
39
+ - { value: 121, expected: "Rejected — above maximum" }
40
+ - { value: 0, expected: "Rejected — zero" }
41
+ - { value: -1, expected: "Rejected — negative" }
42
+
43
+ - input: "Quantity field (1-99)"
44
+ test_values:
45
+ - { value: 0, expected: "Rejected" }
46
+ - { value: 1, expected: "Accepted — minimum" }
47
+ - { value: 99, expected: "Accepted — maximum" }
48
+ - { value: 100, expected: "Rejected" }
49
+
50
+ - name: Type Boundaries
51
+ description: "Test at the limits of the data type itself, not just the business rule."
52
+ approach:
53
+ - "Consider the underlying data type (int32, int64, float, etc.)."
54
+ - "Test at type overflow boundaries."
55
+ - "Test type coercion boundaries — what happens when a float is expected but an int is given, or vice versa."
56
+ - "Test with the wrong type entirely."
57
+ examples:
58
+ - input: "Integer field"
59
+ test_values:
60
+ - { value: 2147483647, expected: "Max int32 — should handle or reject gracefully" }
61
+ - { value: 2147483648, expected: "Int32 overflow — should not wrap to negative" }
62
+ - { value: -2147483648, expected: "Min int32 — boundary" }
63
+ - { value: -2147483649, expected: "Int32 underflow" }
64
+ - { value: 9999999999999999, expected: "Beyond int32, test int64 handling" }
65
+ - { value: "3.14", expected: "Float in integer field — truncation? rejection?" }
66
+ - { value: "1e10", expected: "Scientific notation — accepted or rejected?" }
67
+ - { value: "abc", expected: "Wrong type entirely — must be rejected" }
68
+
69
+ - input: "Price/money field"
70
+ test_values:
71
+ - { value: "0.00", expected: "Zero price — allowed or not?" }
72
+ - { value: "0.001", expected: "Three decimal places — rounding behavior?" }
73
+ - { value: "0.1 + 0.2", expected: "Floating point imprecision (0.30000000000000004)" }
74
+ - { value: "999999999.99", expected: "Very large price — display and storage" }
75
+ - { value: "-10.00", expected: "Negative price — refund context?" }
76
+
77
+ - name: Numeric Boundaries
78
+ description: "Common numeric edge cases that catch bugs regardless of specific business rules."
79
+ approach:
80
+ - "Always test zero, negative, and very large positive values."
81
+ - "Test decimal precision boundaries."
82
+ - "Test numeric strings vs. actual numbers."
83
+ - "Test special numeric values (NaN, Infinity)."
84
+ examples:
85
+ - category: "Universal numeric tests"
86
+ test_values:
87
+ - { value: 0, note: "Zero — the most common boundary bug trigger" }
88
+ - { value: -1, note: "First negative — sign handling" }
89
+ - { value: -0, note: "Negative zero — JS treats this specially" }
90
+ - { value: 0.1, note: "Simple decimal" }
91
+ - { value: 0.123456789012345, note: "High precision decimal" }
92
+ - { value: "NaN", note: "Not a number — should be caught by validation" }
93
+ - { value: "Infinity", note: "Infinity — division by zero result" }
94
+ - { value: "-Infinity", note: "Negative infinity" }
95
+ - { value: "1e308", note: "Near max float64" }
96
+ - { value: "5e-324", note: "Near min positive float64" }
97
+
98
+ - name: String Boundaries
99
+ description: "Test string length limits, empty strings, and content boundaries."
100
+ approach:
101
+ - "Test empty string and whitespace-only strings."
102
+ - "Test at the character limit and one beyond."
103
+ - "Test single character."
104
+ - "Test with very long strings."
105
+ - "Test with different character types at boundaries."
106
+ examples:
107
+ - input: "Name field (max 50 characters)"
108
+ test_values:
109
+ - { value: "", expected: "Empty — required field check" }
110
+ - { value: " ", expected: "Single space — trimming behavior?" }
111
+ - { value: " ", expected: "Multiple spaces — whitespace-only handling" }
112
+ - { value: "A", expected: "Single character — minimum viable input" }
113
+ - { value: "A" , note: "Repeat 49 times = 49 chars — one below limit" }
114
+ - { value: "A" , note: "Repeat 50 times = 50 chars — exactly at limit" }
115
+ - { value: "A" , note: "Repeat 51 times = 51 chars — one above limit, should truncate or reject" }
116
+ - { value: "A" , note: "Repeat 1000 times — far beyond limit" }
117
+
118
+ - input: "General string edge cases"
119
+ test_values:
120
+ - { value: " leading spaces", expected: "Trimming on left?" }
121
+ - { value: "trailing spaces ", expected: "Trimming on right?" }
122
+ - { value: "line1\\nline2", expected: "Newline in single-line field" }
123
+ - { value: "tab\\there", expected: "Tab character in input" }
124
+ - { value: "null", expected: "String 'null' — not confused with null value" }
125
+ - { value: "undefined", expected: "String 'undefined'" }
126
+ - { value: "true", expected: "String 'true' — not coerced to boolean" }
127
+ - { value: "0", expected: "String '0' — not treated as falsy" }
128
+
129
+ - name: Date Boundaries
130
+ description: "Test at calendar boundaries, time zone edges, and format limits."
131
+ approach:
132
+ - "Test at month and year boundaries."
133
+ - "Test leap year dates."
134
+ - "Test DST transition dates."
135
+ - "Test minimum and maximum dates the system should handle."
136
+ - "Test date format boundaries."
137
+ examples:
138
+ - category: "Calendar boundary dates"
139
+ test_values:
140
+ - { value: "2026-01-01", note: "Start of year" }
141
+ - { value: "2026-12-31", note: "End of year" }
142
+ - { value: "2026-02-28", note: "End of February (non-leap year)" }
143
+ - { value: "2024-02-29", note: "Leap day (2024 is a leap year)" }
144
+ - { value: "2025-02-29", note: "Invalid — 2025 is not a leap year" }
145
+ - { value: "2026-04-30", note: "Last day of 30-day month" }
146
+ - { value: "2026-04-31", note: "Invalid — April has 30 days" }
147
+ - { value: "2026-03-08", note: "DST spring forward (US)" }
148
+ - { value: "2026-11-01", note: "DST fall back (US)" }
149
+ - { value: "1970-01-01", note: "Unix epoch — common system minimum" }
150
+ - { value: "2038-01-19", note: "Unix timestamp overflow (Y2K38)" }
151
+ - { value: "1900-01-01", note: "Pre-epoch date" }
152
+ - { value: "9999-12-31", note: "Far future date" }
153
+
154
+ - category: "Time boundary values"
155
+ test_values:
156
+ - { value: "00:00:00", note: "Midnight — start of day" }
157
+ - { value: "23:59:59", note: "Last second of day" }
158
+ - { value: "12:00:00", note: "Noon — AM/PM boundary" }
159
+ - { value: "24:00:00", note: "Invalid in most systems — should be 00:00:00 next day" }
160
+ - { value: "23:59:60", note: "Leap second — most systems reject this" }
161
+
162
+ - name: Collection Boundaries
163
+ description: "Test at the edges of lists, arrays, sets, and paginated results."
164
+ approach:
165
+ - "Test with empty collections."
166
+ - "Test with a single item."
167
+ - "Test at pagination boundaries."
168
+ - "Test at the system's maximum allowed items."
169
+ - "Test bulk operations at boundaries."
170
+ examples:
171
+ - category: "Collection size boundaries"
172
+ test_values:
173
+ - { value: "0 items", note: "Empty state — what does the UI show?" }
174
+ - { value: "1 item", note: "Single item — plural/singular labels?" }
175
+ - { value: "2 items", note: "Minimum plural — layout edge case" }
176
+ - { value: "page_size - 1", note: "Just under one page — no pagination shown?" }
177
+ - { value: "page_size", note: "Exactly one page — pagination appears or not?" }
178
+ - { value: "page_size + 1", note: "Just over one page — second page has 1 item" }
179
+ - { value: "1000 items", note: "Large list — performance and scrolling" }
180
+ - { value: "max_limit", note: "System maximum — does it enforce the cap?" }
181
+ - { value: "max_limit + 1", note: "One beyond maximum — rejection message?" }
182
+
183
+ - category: "Selection and multi-select boundaries"
184
+ test_values:
185
+ - { value: "Select 0", note: "No selection — action buttons disabled?" }
186
+ - { value: "Select 1", note: "Single selection" }
187
+ - { value: "Select all", note: "Select all on current page vs. all pages" }
188
+ - { value: "Select all then deselect one", note: "Mixed state handling" }
189
+
190
+ when_to_use:
191
+ - "Every time you encounter an input field — boundaries are always worth testing."
192
+ - "When you know the validation rules — test at the exact boundaries."
193
+ - "When you do not know the rules — probe with boundary values to discover them."
194
+ - "When testing calculations — precision and overflow boundaries."
195
+ - "When testing lists and pagination — collection boundaries."
196
+
197
+ gotchas:
198
+ - "The spec says max is 100, but does the code use < or <=? Always test the exact boundary."
199
+ - "Client-side validation may differ from server-side — test both (submit via devtools to bypass client)."
200
+ - "Floating point arithmetic is imprecise — 0.1 + 0.2 !== 0.3 in most languages."
201
+ - "Empty string and null are different — test both."
202
+ - "Date boundaries depend on timezone — midnight in UTC may be yesterday in Pacific."
203
+ - "Collection boundaries interact with permissions — can a user with 'read' access trigger bulk operations?"
@@ -0,0 +1,146 @@
1
+ id: technique-business-logic-race-conditions
2
+ version: "0.1.0"
3
+ type: technique
4
+ name: "Business Logic Flaws & Race Condition Testing"
5
+ description: >
6
+ Advanced technique for finding high-impact bugs in mature applications — hidden
7
+ endpoints, state transition attacks, parameter tampering, and race conditions.
8
+ Sourced from experienced bug bounty hunters.
9
+ author: "Compiled from bug bounty community (Reddit r/bugbounty)"
10
+ source: "Bug bounty practitioner methodologies"
11
+ tags: [security, business-logic, race-condition, state-transition, advanced]
12
+ domains: [all]
13
+ priority: high
14
+ added: "2026-03-28"
15
+ updated: "2026-03-28"
16
+
17
+ content:
18
+ summary: >
19
+ Most obvious bugs get found first. High-impact bugs live in business logic
20
+ (wrong state transitions, parameter tampering, privilege escalation) and race
21
+ conditions (parallel requests exploiting timing windows). The key insight:
22
+ treat the frontend JS as your real API map to find hidden surface area,
23
+ then stress-test every state transition.
24
+
25
+ hidden_surface_area:
26
+ description: >
27
+ Mature apps have hidden endpoints — old flows, admin helpers, feature-flagged
28
+ routes, mobile-only APIs. These are less tested and often miss newer validation.
29
+ how_to_find:
30
+ - "Check page source and JS bundles for API endpoints, fetch/axios calls"
31
+ - "Look for /api/, /v1/, /v2/, /graphql, /internal/ patterns in JS"
32
+ - "Check network tab for requests not visible in the UI"
33
+ - "Look for commented-out features, feature flags, A/B test routes"
34
+ - "Try common endpoint patterns: /admin, /debug, /status, /health, /metrics"
35
+ playwright_cli_approach:
36
+ - "npx playwright-cli network — capture all API calls during normal usage"
37
+ - "npx playwright-cli eval \"Array.from(document.querySelectorAll('script[src]')).map(s => s.src)\" — find JS bundles"
38
+ - "npx playwright-cli eval \"performance.getEntriesByType('resource').filter(r => r.name.includes('api')).map(r => r.name)\" — find API calls"
39
+
40
+ logic_stress_testing:
41
+ description: >
42
+ For every state-changing endpoint (create, update, delete, transfer, confirm),
43
+ test what happens when you break the expected flow.
44
+ attack_patterns:
45
+ - name: "Wrong state order"
46
+ description: "Call step 3 before step 1 — skip prerequisites"
47
+ examples:
48
+ - "Submit payment confirmation without adding items to cart"
49
+ - "Access order confirmation page directly without checkout"
50
+ - "Call 'confirm transfer' without initiating transfer"
51
+ playwright_cli: "Navigate directly to confirmation URLs, skip intermediate steps"
52
+
53
+ - name: "Parameter tampering"
54
+ description: "Change values that should be server-controlled"
55
+ examples:
56
+ - "Modify price/amount in the request"
57
+ - "Change user ID to access another user's data"
58
+ - "Change role/permission level in request body"
59
+ - "Modify quantity to negative or zero"
60
+ - "Change currency or payment method mid-flow"
61
+ playwright_cli: >
62
+ Fill forms with tampered values, use eval to modify hidden fields:
63
+ npx playwright-cli eval "document.querySelector('input[name=price]').value = '0.01'"
64
+
65
+ - name: "Replay attacks"
66
+ description: "Repeat a request that should only work once"
67
+ examples:
68
+ - "Submit the same discount code twice"
69
+ - "Confirm the same order multiple times"
70
+ - "Redeem the same gift card/coupon again"
71
+ - "Apply referral bonus after already used"
72
+
73
+ - name: "State transition bypasses"
74
+ description: "Skip or reorder steps in a multi-step flow"
75
+ examples:
76
+ - "Go from cart directly to order confirmation (skip payment)"
77
+ - "Change shipping address after payment confirmed"
78
+ - "Cancel then un-cancel an order"
79
+ - "Downgrade account then access premium features"
80
+
81
+ race_condition_testing:
82
+ description: >
83
+ Fire parallel requests against the same state transition to exploit
84
+ timing windows where validation hasn't completed yet.
85
+ high_value_targets:
86
+ - "Double-submit: payment, transfer, order placement"
87
+ - "Duplicate redeem: coupons, gift cards, rewards"
88
+ - "Quota bypass: rate limits, usage caps, free tier limits"
89
+ - "Double-like/follow/vote: social actions"
90
+ - "Multiple withdrawals: before balance check completes"
91
+ - "Invitation/role change: race between invite and revoke"
92
+ - "Inventory: buy last item simultaneously from two sessions"
93
+
94
+ how_to_test:
95
+ - description: "Multi-tab approach (with playwright-cli)"
96
+ steps:
97
+ - "Open two browser sessions: -s=race1 and -s=race2"
98
+ - "Navigate both to the same state-changing page"
99
+ - "Fill forms in both sessions"
100
+ - "Submit both as close together as possible"
101
+ - "Check if both succeeded (e.g., double charge, double credit)"
102
+
103
+ - description: "Rapid sequential approach"
104
+ steps:
105
+ - "Complete action once normally"
106
+ - "Immediately repeat the same action before state updates"
107
+ - "Check for duplicate records, double charges, or bypassed limits"
108
+
109
+ what_to_look_for:
110
+ - "Two successful responses when only one should succeed"
111
+ - "Balance debited twice or credited twice"
112
+ - "Duplicate records in database (orders, transactions)"
113
+ - "Rate limit bypassed"
114
+ - "Coupon/discount applied multiple times"
115
+
116
+ mindset:
117
+ principles:
118
+ - name: "Use the app as a real user first"
119
+ description: "Before hunting bugs, understand the product's business logic by actually using it. Know what SHOULD happen before testing what SHOULDN'T."
120
+
121
+ - name: "Dev experience reveals patterns"
122
+ description: "Understanding how developers build things helps predict where they cut corners. Common shortcuts: client-side validation only, trusting user-supplied IDs, missing server-side state checks."
123
+
124
+ - name: "Creativity over checklists"
125
+ description: "Stop when you catch yourself mechanically following steps. Ask: 'What would happen if...?' and follow your curiosity."
126
+
127
+ - name: "Hidden endpoints = highest ROI"
128
+ description: "Endpoints with no GUI path are less tested. Old flows, admin helpers, and feature-flagged routes often miss newer security controls."
129
+
130
+ - name: "Every state transition is a target"
131
+ description: "Any action that changes data (create, update, delete, transfer, confirm) is worth testing for logic flaws and race conditions."
132
+
133
+ when_to_use:
134
+ - "After functional testing passes — these bugs live BEYOND happy-path validation"
135
+ - "On any app with financial transactions (transfers, payments, credits)"
136
+ - "On any app with user-generated content (likes, votes, reviews)"
137
+ - "On any app with inventory or quotas (e-commerce, SaaS tiers)"
138
+ - "On multi-step flows (checkout, onboarding, approval workflows)"
139
+ - "When the app feels 'mature' and obvious bugs are already fixed"
140
+
141
+ gotchas:
142
+ - "Race conditions are hard to reproduce reliably — may need multiple attempts"
143
+ - "Don't test destructive race conditions on production without authorization"
144
+ - "Parameter tampering via browser tools may be blocked by CSRF tokens — check for them"
145
+ - "Hidden endpoints may require valid auth tokens — capture them from a normal session first"
146
+ - "AI agents tend to skip this entirely because it requires creative 'what if' thinking"
@@ -0,0 +1,269 @@
1
+ id: technique-data-integrity-testing
2
+ version: "0.1.0"
3
+ type: technique
4
+ name: "Data Integrity & Cross-Feature Verification"
5
+ description: >
6
+ After every state-changing action, verify that data is correct on ALL related
7
+ pages. This technique goes beyond testing a single feature in isolation — it
8
+ checks that data remains consistent, accurate, and complete as it flows
9
+ through the entire system. The most impactful bugs are often not in the
10
+ action itself but in how the result appears elsewhere.
11
+ author: "Classic testing technique"
12
+ source: "Adapted from data quality engineering and exploratory testing practice"
13
+ tags: [data-integrity, verification, cross-feature, calculations, audit]
14
+ domains: [all]
15
+ priority: high
16
+ added: "2026-03-28"
17
+
18
+ content:
19
+ summary: >
20
+ Most testers verify that an action worked on the page where they performed
21
+ it. Data integrity testing goes further: after every create, update, or
22
+ delete, navigate to every other page that displays or uses that data and
23
+ verify it is correct there too. This catches stale caches, missing event
24
+ propagation, incorrect aggregations, timezone mismatches, and a host of
25
+ other cross-feature bugs that functional testing misses.
26
+
27
+ core_principle: >
28
+ "If data changes in one place, verify it everywhere."
29
+ Every state-changing action (create, update, delete, transfer, calculate)
30
+ produces data that appears in multiple locations: detail pages, list views,
31
+ dashboards, reports, notifications, audit logs, and API responses. A bug
32
+ in any one of these locations means the system's data integrity is
33
+ compromised.
34
+
35
+ categories:
36
+ - name: Calculation Verification
37
+ description: "Does the math add up? Verify all arithmetic, aggregations, and derived values."
38
+ checks:
39
+ - "Price x Quantity = Line Total (no floating point errors)"
40
+ - "Sum of line totals = Subtotal"
41
+ - "Subtotal + Tax + Shipping - Discount = Grand Total"
42
+ - "Debit entries = Credit entries (accounting balance)"
43
+ - "Percentage calculations (e.g., discount %, tax %) are correct"
44
+ - "Running totals and cumulative values are accurate"
45
+ - "Averages, medians, and statistical aggregations are correct"
46
+ - "Currency conversion uses the correct rate and rounds properly"
47
+ common_bugs:
48
+ - "Floating point: 0.1 + 0.2 = 0.30000000000000004 instead of 0.3"
49
+ - "Rounding: $10.005 rounds to $10.00 or $10.01 depending on implementation"
50
+ - "Integer overflow: quantity 999999 x price 9999.99 exceeds int32"
51
+ - "Division by zero: percentage of 0 items, average of empty list"
52
+ - "Tax calculated on discounted price vs. original price"
53
+ - "Running total not updated after item removal"
54
+ test_approach:
55
+ - "Manually calculate the expected result and compare with the displayed value."
56
+ - "Use at least 3 decimal places in test data to expose rounding issues."
57
+ - "Test with quantities and prices that produce repeating decimals (1/3, 1/7)."
58
+ - "Verify totals after adding, removing, and modifying items."
59
+
60
+ - name: Cross-Page Consistency
61
+ description: "Is data the same when viewed from different pages and contexts?"
62
+ checks:
63
+ - "Data on the detail page matches data in the list view"
64
+ - "Dashboard summary matches the sum of individual records"
65
+ - "Search results show the same data as the detail page"
66
+ - "API response matches what the UI displays"
67
+ - "Export (CSV, PDF) matches what is displayed on screen"
68
+ - "Notification content matches the actual data"
69
+ - "Mobile view shows the same data as desktop view"
70
+ - "Cached pages show updated data after changes"
71
+ common_bugs:
72
+ - "List view shows old name after record was renamed"
73
+ - "Dashboard count does not update after creating or deleting records"
74
+ - "Search index is stale — recently created records are not found"
75
+ - "CSV export uses a different date format than the UI"
76
+ - "Notification email shows the old value, not the updated one"
77
+ - "Mobile API returns a different data shape than web API"
78
+ test_approach:
79
+ - "After every create/update/delete, visit at least 3 other pages that display the data."
80
+ - "Compare the exact values — not just 'it shows something' but 'it shows the right thing.'"
81
+ - "Check totals and counts on dashboard pages after every data change."
82
+ - "Trigger an export after changes and verify data matches the UI."
83
+
84
+ - name: Persistence
85
+ description: "Does data survive actions that should not change it?"
86
+ checks:
87
+ - "Data persists after page reload (F5 / Cmd+R)"
88
+ - "Data persists after browser back and forward navigation"
89
+ - "Data persists after logout and login"
90
+ - "Data persists after closing and reopening the browser"
91
+ - "Data persists after clearing browser cache (if server-stored)"
92
+ - "Form data is preserved when switching between tabs in a multi-tab form"
93
+ - "Draft or unsaved data is recovered after accidental navigation"
94
+ common_bugs:
95
+ - "Data stored only in component state, lost on navigation"
96
+ - "LocalStorage data cleared by browser privacy settings"
97
+ - "Session data lost after token refresh"
98
+ - "Form values reset when switching between tabs within the form"
99
+ - "File upload reference lost on page reload before submit"
100
+ test_approach:
101
+ - "After every successful save, reload the page and verify data is still there."
102
+ - "Navigate away and come back using browser back button."
103
+ - "Logout, login, and verify all data is intact."
104
+ - "Close the browser tab, reopen the URL, and check."
105
+
106
+ - name: Audit Trail
107
+ description: "Do history and logs accurately reflect what happened?"
108
+ checks:
109
+ - "Every create, update, and delete action is logged"
110
+ - "Log entries include who, what, when, and the old/new values"
111
+ - "The audit trail timestamp matches the action time"
112
+ - "Bulk operations generate individual log entries for each affected record"
113
+ - "Failed operations are logged (not just successful ones)"
114
+ - "Audit logs cannot be modified or deleted by regular users"
115
+ - "The log accurately reflects which user performed the action (not a system user)"
116
+ common_bugs:
117
+ - "Missing audit log entries for certain action types (delete, bulk update)"
118
+ - "Audit log shows 'system' instead of the actual user"
119
+ - "Timestamp in audit log is in server timezone, not the user's timezone"
120
+ - "Bulk operations logged as a single entry instead of per-record"
121
+ - "Audit log entry created even when the action failed"
122
+ - "Old value not captured — log only shows new value"
123
+ test_approach:
124
+ - "Perform an action, then immediately check the audit log or activity history."
125
+ - "Verify the log contains who, what, when, old value, and new value."
126
+ - "Perform a bulk operation and check that each affected record has its own log entry."
127
+ - "Attempt an action that fails and verify the failure is or is not logged as expected."
128
+
129
+ - name: Uniqueness
130
+ description: "Are IDs, order numbers, and transaction identifiers unique across operations?"
131
+ checks:
132
+ - "Every created record has a unique ID"
133
+ - "Order numbers, invoice numbers, and transaction IDs are unique"
134
+ - "Rapid sequential creation does not produce duplicate IDs"
135
+ - "Concurrent creation from multiple sessions does not produce duplicate IDs"
136
+ - "IDs follow the expected format (UUID, sequential, prefixed)"
137
+ - "Deleted IDs are not reused (or are reused intentionally with documentation)"
138
+ common_bugs:
139
+ - "Duplicate order numbers generated under concurrent load"
140
+ - "Sequential IDs skip numbers after failed operations"
141
+ - "UUID generation uses a weak random seed producing collisions"
142
+ - "Counter reset after service restart producing duplicate IDs"
143
+ - "Race condition: two records created in the same millisecond share a timestamp-based ID"
144
+ test_approach:
145
+ - "Create multiple records in rapid succession and compare their IDs."
146
+ - "Create records from two different sessions simultaneously and verify unique IDs."
147
+ - "Record the IDs and search for duplicates after a batch of operations."
148
+ - "Check that the ID format is consistent across all created records."
149
+
150
+ - name: Temporal
151
+ description: "Are timestamps correct, in the right timezone, and in the right order?"
152
+ checks:
153
+ - "Created-at timestamp matches the time the action was performed"
154
+ - "Updated-at timestamp changes on every modification"
155
+ - "Timestamps are displayed in the user's timezone (not UTC or server timezone)"
156
+ - "Chronological order is correct — newer events appear before older ones (or vice versa, depending on sort)"
157
+ - "Duration calculations are correct (end time - start time)"
158
+ - "Scheduled actions execute at the correct time in the correct timezone"
159
+ - "DST transitions do not cause duplicate or missing time slots"
160
+ common_bugs:
161
+ - "Timestamps shown in UTC instead of user's local timezone"
162
+ - "Created-at and updated-at are identical even after multiple edits"
163
+ - "Events sorted by string comparison of timestamps instead of actual time"
164
+ - "Timezone offset applied twice (double-conversion)"
165
+ - "Scheduled event fires 1 hour early or late after DST change"
166
+ - "Relative time display ('2 hours ago') calculated from server time, not user time"
167
+ test_approach:
168
+ - "Note the current time before an action, perform it, then verify the timestamp."
169
+ - "Edit a record and verify updated-at changed while created-at did not."
170
+ - "Compare timestamps between the detail page, list view, audit log, and API response."
171
+ - "If the system supports multiple timezones, create data in one timezone and view in another."
172
+
173
+ playwright_cli_approach:
174
+ description: "How to verify data integrity using Playwright CLI commands."
175
+ workflows:
176
+ - name: "Action then cross-page verification"
177
+ steps:
178
+ - "Perform the state-changing action (fill form, click submit)."
179
+ - "Take a snapshot of the confirmation/success page — capture the key data values."
180
+ - "Navigate to a related page (list view, dashboard, detail page)."
181
+ - "Take a snapshot — verify the data matches what was just created/modified."
182
+ - "Navigate to another related page (reports, export, search)."
183
+ - "Take a snapshot — verify consistency again."
184
+ example: >
185
+ 1. fill [order-form] with test data, click submit
186
+ 2. snapshot — capture order number and total
187
+ 3. navigate to /orders — verify order appears in list with correct total
188
+ 4. navigate to /dashboard — verify order count and revenue updated
189
+ 5. navigate to /orders/{id} — verify detail page shows all correct data
190
+
191
+ - name: "Repeat action then verify uniqueness"
192
+ steps:
193
+ - "Perform the same action twice in quick succession."
194
+ - "Capture the IDs or reference numbers from both operations."
195
+ - "Verify the IDs are different."
196
+ - "Navigate to the list view and verify both records exist as separate entries."
197
+ example: >
198
+ 1. fill [create-form], click submit — note ID: ORD-001
199
+ 2. fill [create-form] with same data, click submit — note ID: ORD-002
200
+ 3. navigate to /orders — verify both ORD-001 and ORD-002 exist
201
+ 4. verify each has unique timestamps
202
+
203
+ - name: "Reload page then verify persistence"
204
+ steps:
205
+ - "Perform a state-changing action."
206
+ - "Take a snapshot to capture the current state."
207
+ - "Reload the page."
208
+ - "Take another snapshot."
209
+ - "Compare the two snapshots — data should be identical."
210
+ example: >
211
+ 1. edit a record, click save
212
+ 2. snapshot — capture all field values
213
+ 3. reload the page (navigate to current URL)
214
+ 4. snapshot — verify all field values are unchanged
215
+
216
+ common_integrity_bugs:
217
+ - name: "Floating point errors in financial calculations"
218
+ description: "JavaScript and most languages represent decimals as IEEE 754 floats, which cannot precisely represent all decimal fractions."
219
+ example: "Cart shows $30.00 but actual charge is $30.000000000000004 — visible in API response."
220
+ detection: "Compare displayed total with manually calculated total using at least 3 decimal places."
221
+
222
+ - name: "Stale data after state changes (cached pages)"
223
+ description: "CDN caches, browser caches, or in-memory caches serve old data after a record was modified."
224
+ example: "User updates profile name but the header still shows the old name until hard refresh."
225
+ detection: "After every update, visit all pages that display the data without clearing cache."
226
+
227
+ - name: "Missing audit log entries"
228
+ description: "Some action types are not logged, or the logging mechanism fails silently."
229
+ example: "Bulk delete removes 50 records but only logs 1 audit entry."
230
+ detection: "Perform each type of CRUD operation and verify audit log has a corresponding entry."
231
+
232
+ - name: "Duplicate IDs on repeated operations"
233
+ description: "ID generation relies on timestamps or non-atomic counters, producing collisions under concurrent load."
234
+ example: "Two orders created simultaneously both get order number ORD-20260328-001."
235
+ detection: "Create multiple records rapidly (within 1 second) and compare IDs."
236
+
237
+ - name: "Timezone mismatches between server and display"
238
+ description: "Server stores UTC, but display code applies timezone offset incorrectly or inconsistently."
239
+ example: "Order placed at 11 PM EST shows as next day (March 29) because server stores UTC (4 AM March 29)."
240
+ detection: "Note the exact local time before an action, then verify the displayed timestamp matches."
241
+
242
+ - name: "Aggregation drift"
243
+ description: "Dashboard totals and counts drift from actual values because they are calculated independently or cached."
244
+ example: "Dashboard shows 99 orders but the order list has 100 entries."
245
+ detection: "Count records manually on the list page and compare with the dashboard counter."
246
+
247
+ - name: "Orphaned references"
248
+ description: "Deleting a parent record leaves child records pointing to a non-existent parent."
249
+ example: "Delete a category but products still reference it, showing 'undefined' as category name."
250
+ detection: "Delete a record that has dependent data, then check how dependents display."
251
+
252
+ when_to_use:
253
+ - "After EVERY state-changing action during exploratory testing — make it a habit, not an afterthought."
254
+ - "When testing features that aggregate or summarize data (dashboards, reports, totals)."
255
+ - "When testing e-commerce (prices, quantities, totals, taxes, discounts — calculation verification is critical)."
256
+ - "When testing multi-page workflows (data entered in step 1 must appear correctly in steps 2-5)."
257
+ - "When the FedEx Tour (Whittaker) reveals data flowing through multiple touchpoints."
258
+ - "After import/export operations — verify data round-trips correctly."
259
+ - "When testing systems with audit or compliance requirements."
260
+
261
+ gotchas:
262
+ - "Do not assume data is correct just because the success message appeared — always verify on a different page."
263
+ - "Cache invalidation is one of the two hard problems in CS — always test data freshness after updates."
264
+ - "Floating point arithmetic is NOT a rounding error you can ignore — in financial systems it is a legal liability."
265
+ - "Cross-page verification is the highest-ROI technique most testers skip — it catches bugs that no single-page test will find."
266
+ - "Audit trail testing is often skipped because it feels boring — but auditors and compliance officers will find the gaps you missed."
267
+ - "Timezone bugs are almost guaranteed in any system that serves users across timezones — test explicitly."
268
+ - "AI agents tend to verify only the page where the action was performed — explicitly navigate to 2-3 other pages after every action."
269
+ - "Uniqueness testing requires creating records in rapid succession — slow, one-at-a-time creation will not trigger race conditions."