qualiow-exploratory-testing 1.3.0 → 2.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 (93) hide show
  1. package/.claude-plugin/plugin.json +22 -0
  2. package/.env.example +27 -0
  3. package/CHANGELOG.md +194 -0
  4. package/README.md +362 -205
  5. package/agents/qa-gather-agent.md +24 -0
  6. package/{scripts → bin}/doctor-mobile.sh +57 -18
  7. package/bin/mcli +15 -9
  8. package/bin/mobile-cli.mjs +574 -286
  9. package/{scripts → bin}/setup-mobile.sh +56 -19
  10. package/bin/wadb +10 -4
  11. package/bin/wk-ios +29 -17
  12. package/bin/wkeval.mjs +7 -1
  13. package/data/domains/_default.yml +1 -1
  14. package/data/knowledge/changelog.yml +30 -12
  15. package/data/knowledge/manifest.yml +333 -127
  16. package/data/knowledge/releases/v0.1.0/entries/technique-business-logic-race-conditions.yml +1 -1
  17. package/data/knowledge/releases/v0.1.0/release.yml +8 -1
  18. package/data/knowledge/releases/v0.6.0/entries/technique-async-callback-contracts.yml +98 -0
  19. package/data/knowledge/releases/v0.6.0/entries/technique-exactly-once-verification.yml +116 -0
  20. package/data/knowledge/releases/v0.6.0/release.yml +30 -0
  21. package/data/security/SECURITY-POLICY.md +273 -0
  22. package/data/targets/_default.yml +1 -1
  23. package/data/targets/_example-api-only.yml +80 -0
  24. package/data/targets/_example-mobile-emulation.yml +2 -2
  25. package/data/targets/_example-native-mobile.yml +2 -2
  26. package/data/targets/_example-sim-android-chrome.yml +1 -1
  27. package/data/targets/_example-sim-ios-safari.yml +1 -1
  28. package/data/templates/api-probe-matrix.md +3 -3
  29. package/data/templates/bug-report.md +29 -151
  30. package/data/templates/coverage-map.md +9 -6
  31. package/data/templates/expected-behaviour.md +3 -2
  32. package/data/templates/session-charter.md +3 -0
  33. package/data/templates/session-report.md +57 -80
  34. package/dist/cli/index.js +1452 -700
  35. package/dist/index.d.ts +589 -81
  36. package/dist/index.js +1612 -227
  37. package/docs/BACKEND-VERIFICATION.md +39 -9
  38. package/docs/GETTING-STARTED.md +188 -128
  39. package/docs/MOBILE-SETUP.md +149 -18
  40. package/package.json +32 -18
  41. package/skills/qa-explore/SKILL.md +31 -25
  42. package/skills/qa-explore/phases/00-setup.md +67 -41
  43. package/skills/qa-explore/phases/01-auth.md +32 -15
  44. package/skills/qa-explore/phases/02-charter.md +16 -5
  45. package/skills/qa-explore/phases/03-discovery.md +50 -26
  46. package/skills/qa-explore/phases/04-journeys.md +2 -2
  47. package/skills/qa-explore/phases/05-features.md +39 -24
  48. package/skills/qa-explore/phases/06-edge-cases.md +24 -13
  49. package/skills/qa-explore/phases/07-reporting.md +79 -140
  50. package/skills/qa-explore/references/context-integration.md +1 -1
  51. package/skills/qa-explore/references/output-contract.md +187 -0
  52. package/skills/qa-explore/references/paths.md +84 -0
  53. package/skills/qa-explore/references/playwright-agents-integration.md +61 -84
  54. package/skills/qa-explore/references/security-rules.md +66 -25
  55. package/skills/qa-explore/references/severity-guide.md +31 -4
  56. package/skills/qa-explore-cleanup/SKILL.md +17 -6
  57. package/skills/qa-explore-feedback/SKILL.md +18 -5
  58. package/skills/qa-explore-mobile/SKILL.md +86 -64
  59. package/skills/qa-explore-mobile/phases/00-setup.md +71 -62
  60. package/skills/qa-explore-mobile/phases/01-auth.md +28 -31
  61. package/skills/qa-explore-mobile/phases/02-charter.md +8 -4
  62. package/skills/qa-explore-mobile/phases/03-discovery.md +17 -11
  63. package/skills/qa-explore-mobile/phases/04-journeys.md +6 -6
  64. package/skills/qa-explore-mobile/phases/05-features.md +9 -9
  65. package/skills/qa-explore-mobile/phases/06-edge-cases.md +35 -40
  66. package/skills/qa-explore-mobile/phases/07-reporting.md +82 -56
  67. package/skills/qa-explore-mobile/references/mobile-edges.md +26 -26
  68. package/skills/qa-explore-quick/SKILL.md +60 -25
  69. package/skills/qa-explore-report/SKILL.md +40 -34
  70. package/skills/qa-gather/SKILL.md +17 -2
  71. package/skills/qa-knowledge-add/SKILL.md +20 -9
  72. package/skills/qa-knowledge-list/SKILL.md +12 -3
  73. package/skills/qa-target-setup/SKILL.md +63 -41
  74. package/skills/qa-verify-backend/SKILL.md +26 -17
  75. package/skills/qa-verify-backend/phases/00-setup.md +57 -12
  76. package/skills/qa-verify-backend/phases/01-ac-decomposition.md +2 -2
  77. package/skills/qa-verify-backend/phases/03-live-verification.md +3 -3
  78. package/skills/qa-verify-backend/phases/03b-api-verification.md +22 -9
  79. package/skills/qa-verify-backend/phases/04-e2e-trigger.md +18 -2
  80. package/skills/qa-verify-backend/phases/05-reporting.md +38 -10
  81. package/skills/qa-verify-backend/references/api-probes.md +28 -1
  82. package/skills/qa-verify-backend/references/payload-verification.md +1 -1
  83. package/skills/qa-verify-backend/references/release-readiness.md +1 -1
  84. package/skills/qa-verify-backend/references/safety-rules.md +13 -8
  85. package/data/domains/_default.md +0 -181
  86. package/data/domains/ecommerce.md +0 -192
  87. package/data/domains/fintech.md +0 -200
  88. package/data/domains/identity.md +0 -88
  89. package/data/domains/marketing.md +0 -194
  90. package/data/domains/saas.md +0 -197
  91. package/dist/cli/index.d.ts +0 -1
  92. package/dist/cli/index.js.map +0 -1
  93. package/dist/index.js.map +0 -1
@@ -1,8 +1,8 @@
1
1
  # Qualiow Exploratory Testing Skills — Knowledge Base Manifest
2
2
  # This file is the master index. Skills read it to discover available entries.
3
3
 
4
- version: "0.5.0"
5
- last_updated: "2026-09-03"
4
+ version: "0.6.0"
5
+ last_updated: "2026-09-08"
6
6
 
7
7
  active_releases:
8
8
  - "v0.1.0"
@@ -10,14 +10,15 @@ active_releases:
10
10
  - "v0.3.0"
11
11
  - "v0.4.0"
12
12
  - "v0.5.0"
13
+ - "v0.6.0"
13
14
 
14
15
  stats:
15
- total_entries: 27
16
+ total_entries: 29
16
17
  heuristics: 5
17
- techniques: 19
18
+ techniques: 21
18
19
  checklists: 1
19
20
  references: 2
20
- domain_profiles: 0
21
+ domain_profiles: 6
21
22
  custom_entries: 0
22
23
 
23
24
  # Loading strategy controls which entries are loaded into context.
@@ -34,7 +35,9 @@ loading_strategy:
34
35
  by_domain:
35
36
  ecommerce: []
36
37
  saas: []
37
- fintech: []
38
+ fintech:
39
+ - technique-exactly-once-verification
40
+ - technique-async-callback-contracts
38
41
  by_tag:
39
42
  security:
40
43
  - technique-error-guessing
@@ -48,6 +51,7 @@ loading_strategy:
48
51
  risk:
49
52
  - technique-risk-based-testing
50
53
  data-integrity:
54
+ - technique-exactly-once-verification
51
55
  - technique-data-integrity-testing
52
56
  - technique-contract-narrowing
53
57
  - technique-derived-value-verification
@@ -157,191 +161,393 @@ loading_strategy:
157
161
 
158
162
  # Entry registry — quick lookup without scanning the filesystem
159
163
  entries:
160
- - id: heuristic-sfdipot
161
- file: releases/v0.1.0/entries/heuristic-sfdipot.yml
162
- type: heuristic
163
- priority: high
164
- tags: [exploration, what-to-test, systematic, rst]
165
- domains: [all]
166
-
164
+ - id: checklist-accessibility-wcag
165
+ file: releases/v0.1.0/entries/checklist-accessibility-wcag.yml
166
+ type: checklist
167
+ priority: medium
168
+ tags:
169
+ - accessibility
170
+ - wcag
171
+ - a11y
172
+ - compliance
173
+ domains:
174
+ - all
167
175
  - id: heuristic-few-hiccupps
168
176
  file: releases/v0.1.0/entries/heuristic-few-hiccupps.yml
169
177
  type: heuristic
170
178
  priority: high
171
- tags: [oracles, bug-recognition, consistency, rst]
172
- domains: [all]
173
-
174
- - id: heuristic-test-tours
175
- file: releases/v0.1.0/entries/heuristic-test-tours.yml
176
- type: heuristic
177
- priority: high
178
- tags: [exploration, how-to-explore, tours, eet]
179
- domains: [all]
180
-
179
+ tags:
180
+ - oracles
181
+ - bug-recognition
182
+ - consistency
183
+ - rst
184
+ domains:
185
+ - all
181
186
  - id: heuristic-goldilocks
182
187
  file: releases/v0.1.0/entries/heuristic-goldilocks.yml
183
188
  type: heuristic
184
189
  priority: high
185
- tags: [input-testing, boundaries, exploration, goldilocks]
186
- domains: [all]
187
-
190
+ tags:
191
+ - input-testing
192
+ - boundaries
193
+ - exploration
194
+ - goldilocks
195
+ domains:
196
+ - all
188
197
  - id: heuristic-rcrcrc
189
198
  file: releases/v0.1.0/entries/heuristic-rcrcrc.yml
190
199
  type: heuristic
191
200
  priority: high
192
- tags: [regression, prioritization, change-management]
193
- domains: [all]
194
-
201
+ tags:
202
+ - regression
203
+ - prioritization
204
+ - change-management
205
+ domains:
206
+ - all
207
+ - id: heuristic-sfdipot
208
+ file: releases/v0.1.0/entries/heuristic-sfdipot.yml
209
+ type: heuristic
210
+ priority: high
211
+ tags:
212
+ - exploration
213
+ - what-to-test
214
+ - systematic
215
+ - rst
216
+ domains:
217
+ - all
218
+ - id: heuristic-test-tours
219
+ file: releases/v0.1.0/entries/heuristic-test-tours.yml
220
+ type: heuristic
221
+ priority: high
222
+ tags:
223
+ - exploration
224
+ - how-to-explore
225
+ - tours
226
+ - eet
227
+ domains:
228
+ - all
229
+ - id: reference-exploratory-testing-types
230
+ file: releases/v0.1.0/entries/reference-exploratory-testing-types.yml
231
+ type: reference
232
+ priority: medium
233
+ tags:
234
+ - exploratory
235
+ - methodology
236
+ - approach
237
+ - agile
238
+ - types
239
+ domains:
240
+ - all
241
+ - id: reference-heuristic-praxis
242
+ file: releases/v0.1.0/entries/reference-heuristic-praxis.yml
243
+ type: reference
244
+ priority: high
245
+ tags:
246
+ - heuristics
247
+ - praxis
248
+ - theory
249
+ - meta-testing
250
+ - reflection
251
+ domains:
252
+ - all
195
253
  - id: technique-boundary-testing
196
254
  file: releases/v0.1.0/entries/technique-boundary-testing.yml
197
255
  type: technique
198
256
  priority: high
199
- tags: [boundaries, edge-cases, input-testing]
200
- domains: [all]
201
-
202
- - id: technique-error-guessing
203
- file: releases/v0.1.0/entries/technique-error-guessing.yml
204
- type: technique
205
- priority: medium
206
- tags: [security, negative-testing, injection, error-handling]
207
- domains: [all]
208
-
257
+ tags:
258
+ - boundaries
259
+ - edge-cases
260
+ - input-testing
261
+ domains:
262
+ - all
209
263
  - id: technique-business-logic-race-conditions
210
264
  file: releases/v0.1.0/entries/technique-business-logic-race-conditions.yml
211
265
  type: technique
212
266
  priority: high
213
- tags: [security, business-logic, race-condition, state-transition, advanced]
214
- domains: [all]
215
-
216
- - id: technique-risk-based-testing
217
- file: releases/v0.1.0/entries/technique-risk-based-testing.yml
218
- type: technique
219
- priority: high
220
- tags: [risk, prioritization, strategy, planning]
221
- domains: [all]
222
-
267
+ tags:
268
+ - security
269
+ - business-logic
270
+ - race-condition
271
+ - state-transition
272
+ - advanced
273
+ domains:
274
+ - all
223
275
  - id: technique-data-integrity-testing
224
276
  file: releases/v0.1.0/entries/technique-data-integrity-testing.yml
225
277
  type: technique
226
278
  priority: high
227
- tags: [data-integrity, verification, cross-feature, calculations, audit]
228
- domains: [all]
229
-
230
- - id: checklist-accessibility-wcag
231
- file: releases/v0.1.0/entries/checklist-accessibility-wcag.yml
232
- type: checklist
233
- priority: medium
234
- tags: [accessibility, wcag, a11y, compliance]
235
- domains: [all]
236
-
237
- - id: reference-exploratory-testing-types
238
- file: releases/v0.1.0/entries/reference-exploratory-testing-types.yml
239
- type: reference
279
+ tags:
280
+ - data-integrity
281
+ - verification
282
+ - cross-feature
283
+ - calculations
284
+ - audit
285
+ domains:
286
+ - all
287
+ - id: technique-error-guessing
288
+ file: releases/v0.1.0/entries/technique-error-guessing.yml
289
+ type: technique
240
290
  priority: medium
241
- tags: [exploratory, methodology, approach, agile, types]
242
- domains: [all]
243
-
244
- - id: reference-heuristic-praxis
245
- file: releases/v0.1.0/entries/reference-heuristic-praxis.yml
246
- type: reference
291
+ tags:
292
+ - security
293
+ - negative-testing
294
+ - injection
295
+ - error-handling
296
+ domains:
297
+ - all
298
+ - id: technique-risk-based-testing
299
+ file: releases/v0.1.0/entries/technique-risk-based-testing.yml
300
+ type: technique
247
301
  priority: high
248
- tags: [heuristics, praxis, theory, meta-testing, reflection]
249
- domains: [all]
250
-
302
+ tags:
303
+ - risk
304
+ - prioritization
305
+ - strategy
306
+ - planning
307
+ domains:
308
+ - all
251
309
  - id: technique-contract-narrowing
252
310
  file: releases/v0.2.0/entries/technique-contract-narrowing.yml
253
311
  type: technique
254
312
  priority: high
255
- tags: [backend, api-contract, integration, data-integrity, refactor, silent-failure, regression]
256
- domains: [all]
257
-
313
+ tags:
314
+ - backend
315
+ - api-contract
316
+ - integration
317
+ - data-integrity
318
+ - refactor
319
+ - silent-failure
320
+ - regression
321
+ domains:
322
+ - all
258
323
  - id: technique-test-suite-audit
259
324
  file: releases/v0.2.0/entries/technique-test-suite-audit.yml
260
325
  type: technique
261
326
  priority: high
262
- tags: [test-quality, verification, ci, acceptance-criteria, backend, regression]
263
- domains: [all]
264
-
265
- - id: technique-verification-mode-selection
266
- file: releases/v0.3.0/entries/technique-verification-mode-selection.yml
267
- type: technique
268
- priority: high
269
- tags: [backend, api, verification, evidence, llm, strategy, acceptance-criteria, test-execution]
270
- domains: [all]
271
-
327
+ tags:
328
+ - test-quality
329
+ - verification
330
+ - ci
331
+ - acceptance-criteria
332
+ - backend
333
+ - regression
334
+ domains:
335
+ - all
272
336
  - id: technique-functional-diff-analysis
273
337
  file: releases/v0.3.0/entries/technique-functional-diff-analysis.yml
274
338
  type: technique
275
339
  priority: high
276
- tags: [backend, api, code-review, static-analysis, acceptance-criteria, llm, scope-creep, regression]
277
- domains: [all]
278
-
340
+ tags:
341
+ - backend
342
+ - api
343
+ - code-review
344
+ - static-analysis
345
+ - acceptance-criteria
346
+ - llm
347
+ - scope-creep
348
+ - regression
349
+ domains:
350
+ - all
279
351
  - id: technique-llm-output-verification
280
352
  file: releases/v0.3.0/entries/technique-llm-output-verification.yml
281
353
  type: technique
282
354
  priority: high
283
- tags: [llm, agent, api, verification, evidence, non-determinism, prompt, evaluation]
284
- domains: [all]
285
-
286
- - id: technique-environment-fingerprinting
287
- file: releases/v0.4.0/entries/technique-environment-fingerprinting.yml
355
+ tags:
356
+ - llm
357
+ - agent
358
+ - api
359
+ - verification
360
+ - evidence
361
+ - non-determinism
362
+ - prompt
363
+ - evaluation
364
+ domains:
365
+ - all
366
+ - id: technique-verification-mode-selection
367
+ file: releases/v0.3.0/entries/technique-verification-mode-selection.yml
288
368
  type: technique
289
369
  priority: high
290
- tags: [backend, api, verification, evidence, deployment, feature-flags, environment, acceptance-criteria, regression]
291
- domains: [all]
292
-
370
+ tags:
371
+ - backend
372
+ - api
373
+ - verification
374
+ - evidence
375
+ - llm
376
+ - strategy
377
+ - acceptance-criteria
378
+ - test-execution
379
+ domains:
380
+ - all
293
381
  - id: technique-authenticated-api-probing
294
382
  file: releases/v0.4.0/entries/technique-authenticated-api-probing.yml
295
383
  type: technique
296
384
  priority: high
297
- tags: [api, backend, verification, evidence, boundaries, negative-testing, error-handling, security, acceptance-criteria]
298
- domains: [all]
299
-
300
- - id: technique-ui-api-differential
301
- file: releases/v0.4.0/entries/technique-ui-api-differential.yml
385
+ tags:
386
+ - api
387
+ - backend
388
+ - verification
389
+ - evidence
390
+ - boundaries
391
+ - negative-testing
392
+ - error-handling
393
+ - security
394
+ - acceptance-criteria
395
+ domains:
396
+ - all
397
+ - id: technique-environment-fingerprinting
398
+ file: releases/v0.4.0/entries/technique-environment-fingerprinting.yml
302
399
  type: technique
303
400
  priority: high
304
- tags: [api, backend, ui, verification, differential, error-handling, silent-failure, acceptance-criteria, regression]
305
- domains: [all]
306
-
401
+ tags:
402
+ - backend
403
+ - api
404
+ - verification
405
+ - evidence
406
+ - deployment
407
+ - feature-flags
408
+ - environment
409
+ - acceptance-criteria
410
+ - regression
411
+ domains:
412
+ - all
307
413
  - id: technique-silent-failure-audit
308
414
  file: releases/v0.4.0/entries/technique-silent-failure-audit.yml
309
415
  type: technique
310
416
  priority: high
311
- tags: [error-handling, silent-failure, api, backend, ui, data-integrity, observability, negative-testing, regression]
312
- domains: [all]
313
-
314
- - id: technique-derived-value-verification
315
- file: releases/v0.5.0/entries/technique-derived-value-verification.yml
417
+ tags:
418
+ - error-handling
419
+ - silent-failure
420
+ - api
421
+ - backend
422
+ - ui
423
+ - data-integrity
424
+ - observability
425
+ - negative-testing
426
+ - regression
427
+ domains:
428
+ - all
429
+ - id: technique-ui-api-differential
430
+ file: releases/v0.4.0/entries/technique-ui-api-differential.yml
316
431
  type: technique
317
432
  priority: high
318
- tags: [data-integrity, api, backend, calculations, verification, evidence, oracles, acceptance-criteria]
319
- domains: [all]
320
-
321
- - id: technique-presentation-integrity
322
- file: releases/v0.5.0/entries/technique-presentation-integrity.yml
433
+ tags:
434
+ - api
435
+ - backend
436
+ - ui
437
+ - verification
438
+ - differential
439
+ - error-handling
440
+ - silent-failure
441
+ - acceptance-criteria
442
+ - regression
443
+ domains:
444
+ - all
445
+ - id: technique-config-surface-verification
446
+ file: releases/v0.5.0/entries/technique-config-surface-verification.yml
447
+ type: technique
448
+ priority: medium
449
+ tags:
450
+ - backend
451
+ - api
452
+ - feature-flags
453
+ - environment
454
+ - security
455
+ - configuration
456
+ - deployment
457
+ - verification
458
+ domains:
459
+ - all
460
+ - id: technique-derived-value-verification
461
+ file: releases/v0.5.0/entries/technique-derived-value-verification.yml
323
462
  type: technique
324
463
  priority: high
325
- tags: [ui, api, data-integrity, verification, differential, calculations, regression, error-handling]
326
- domains: [all]
327
-
464
+ tags:
465
+ - data-integrity
466
+ - api
467
+ - backend
468
+ - calculations
469
+ - verification
470
+ - evidence
471
+ - oracles
472
+ - acceptance-criteria
473
+ domains:
474
+ - all
328
475
  - id: technique-expected-behaviour-specification
329
476
  file: releases/v0.5.0/entries/technique-expected-behaviour-specification.yml
330
477
  type: technique
331
478
  priority: high
332
- tags: [acceptance-criteria, api, backend, requirements, reporting, communication, contract, verification]
333
- domains: [all]
334
-
335
- - id: technique-config-surface-verification
336
- file: releases/v0.5.0/entries/technique-config-surface-verification.yml
479
+ tags:
480
+ - acceptance-criteria
481
+ - api
482
+ - backend
483
+ - requirements
484
+ - reporting
485
+ - communication
486
+ - contract
487
+ - verification
488
+ domains:
489
+ - all
490
+ - id: technique-presentation-integrity
491
+ file: releases/v0.5.0/entries/technique-presentation-integrity.yml
337
492
  type: technique
338
- priority: medium
339
- tags: [backend, api, feature-flags, environment, security, configuration, deployment, verification]
340
- domains: [all]
341
-
493
+ priority: high
494
+ tags:
495
+ - ui
496
+ - api
497
+ - data-integrity
498
+ - verification
499
+ - differential
500
+ - calculations
501
+ - regression
502
+ - error-handling
503
+ domains:
504
+ - all
342
505
  - id: technique-release-readiness-verification
343
506
  file: releases/v0.5.0/entries/technique-release-readiness-verification.yml
344
507
  type: technique
345
508
  priority: high
346
- tags: [regression, release, deployment, reporting, coverage, risk, acceptance-criteria, verification, environment]
347
- domains: [all]
509
+ tags:
510
+ - regression
511
+ - release
512
+ - deployment
513
+ - reporting
514
+ - coverage
515
+ - risk
516
+ - acceptance-criteria
517
+ - verification
518
+ - environment
519
+ domains:
520
+ - all
521
+ - id: technique-async-callback-contracts
522
+ file: releases/v0.6.0/entries/technique-async-callback-contracts.yml
523
+ type: technique
524
+ priority: high
525
+ tags:
526
+ - webhooks
527
+ - callbacks
528
+ - api
529
+ - backend
530
+ - contracts
531
+ - silent-failure
532
+ - integration
533
+ - payments
534
+ domains:
535
+ - fintech
536
+ - all
537
+ - id: technique-exactly-once-verification
538
+ file: releases/v0.6.0/entries/technique-exactly-once-verification.yml
539
+ type: technique
540
+ priority: high
541
+ tags:
542
+ - money
543
+ - payments
544
+ - concurrency
545
+ - idempotency
546
+ - callbacks
547
+ - webhooks
548
+ - data-integrity
549
+ - api
550
+ - backend
551
+ domains:
552
+ - fintech
553
+ - all
@@ -33,7 +33,7 @@ content:
33
33
  - "Look for commented-out features, feature flags, A/B test routes"
34
34
  - "Try common endpoint patterns: /admin, /debug, /status, /health, /metrics"
35
35
  playwright_cli_approach:
36
- - "npx playwright-cli network — capture all API calls during normal usage"
36
+ - "npx playwright-cli requests — capture all API calls during normal usage"
37
37
  - "npx playwright-cli eval \"Array.from(document.querySelectorAll('script[src]')).map(s => s.src)\" — find JS bundles"
38
38
  - "npx playwright-cli eval \"performance.getEntriesByType('resource').filter(r => r.name.includes('api')).map(r => r.name)\" — find API calls"
39
39
 
@@ -11,7 +11,7 @@ notes: >
11
11
  how to recognize bugs (FEW HICCUPPS), how to explore (Test Tours),
12
12
  and core techniques (boundary testing, error guessing, accessibility).
13
13
 
14
- entry_count: 6
14
+ entry_count: 13
15
15
 
16
16
  entries:
17
17
  - heuristic-sfdipot
@@ -20,3 +20,10 @@ entries:
20
20
  - technique-boundary-testing
21
21
  - technique-error-guessing
22
22
  - checklist-accessibility-wcag
23
+ - heuristic-goldilocks
24
+ - heuristic-rcrcrc
25
+ - technique-business-logic-race-conditions
26
+ - technique-risk-based-testing
27
+ - technique-data-integrity-testing
28
+ - reference-exploratory-testing-types
29
+ - reference-heuristic-praxis
@@ -0,0 +1,98 @@
1
+ id: technique-async-callback-contracts
2
+ version: "0.6.0"
3
+ type: technique
4
+ name: "Asynchronous Callback Contracts — What a Webhook Endpoint Owes Its Caller"
5
+ description: >
6
+ A callback endpoint is an API whose caller you do not control, cannot ask to retry, and
7
+ cannot expect to behave. This covers what to probe on the receiving end: the identity it
8
+ keys on, what it does with an event it cannot match, whether it distinguishes acknowledging
9
+ from applying, whether its answer is honest enough for the sender to act on, and whether an
10
+ event that arrives out of order is applied, rejected or silently swallowed.
11
+ author: "Qualiow — BE/API verification layer"
12
+ source: "Derived from a black-box assessment of an asynchronous mobile-money top-up service, 2026-09"
13
+ tags: [webhooks, callbacks, api, backend, contracts, silent-failure, integration, payments]
14
+ domains: [fintech, all]
15
+ priority: high
16
+ added: "2026-09-03"
17
+ updated: "2026-09-03"
18
+
19
+ content:
20
+ summary: >
21
+ Establish four things before anything else: is the endpoint authenticated, what field does
22
+ it key on, what does it do with an event that matches nothing, and can the caller tell the
23
+ difference between accepted, duplicate and discarded. Everything else about the integration
24
+ is downstream of those answers.
25
+
26
+ core_principle: >
27
+ The endpoint is the entire contract. There is no client in front of it, no form validation,
28
+ no retry the receiver controls. Judge every case on the consequence of the call succeeding,
29
+ never on how hard it was to make.
30
+
31
+ first_question_authentication: >
32
+ Probe the callback endpoint with no credential and with a wrong one, before anything else.
33
+ A callback endpoint that accepts unauthenticated requests is a "credit any account" endpoint
34
+ on a payments platform, and every other finding is secondary to it. It is also the single
35
+ most commonly unprotected route in an integration, because it is written to be called by
36
+ someone else's system and is easy to think of as inbound plumbing rather than as an API.
37
+ When it IS protected, say so explicitly and prominently — it is worth as much to the reader
38
+ as a defect.
39
+
40
+ second_question_the_dedup_key: >
41
+ The documentation says "duplicates are deduplicated" and never says duplicate of what. Find
42
+ out empirically by varying one field at a time against a settled record: same everything;
43
+ same reference with a new receipt; same receipt against a different reference; same reference
44
+ with a different amount. The field it actually keys on is frequently not the one that is
45
+ unique in the sender's system. A receipt that is globally unique upstream but keyed on
46
+ locally, or a reference that is unique locally but reused upstream, both produce silent
47
+ misapplication.
48
+
49
+ third_question_the_unmatched_event: >
50
+ Send an event whose identifier matches nothing — well-formed, then malformed. Three answers
51
+ are possible and they are not equally good:
52
+ a 4xx that makes a retrying sender retry forever against a record that will never exist;
53
+ a 200 that claims it was applied, which is a broken error contract; and a 200 that is
54
+ explicitly distinguishable, such as an "ignored" flag, which is usually right for a sender
55
+ that does not retry. Whichever it does, the question that follows is the one you cannot see
56
+ from outside — does anything count or alert on it? An unmatched callback for a real payment
57
+ means money collected and never credited, and if nothing counts them the platform learns
58
+ from the customer. Report that as a suspected finding about an absence and say plainly that
59
+ it is not observable through the API.
60
+
61
+ fourth_question_the_honest_acknowledgement: >
62
+ The response body has to let the sender distinguish applied, already-applied and discarded.
63
+ Collapsing them into one 200 is a silent-failure shape: it means no sender, no monitor and
64
+ no engineer can tell a working integration from a broken one. Check what a response says
65
+ when the event applied to MORE records than intended, too — a body listing the records it
66
+ touched is the cheapest possible detection for an identity collision, and a body that just
67
+ says "ok" hides it completely.
68
+
69
+ ordering_and_lateness:
70
+ - "Deliver two events for one record in the wrong order and see which one wins."
71
+ - "Deliver an event after the record has been closed by a timeout or reconciliation job."
72
+ - "Deliver two contradicting events simultaneously and see whether the result is stable."
73
+ - >
74
+ Ask, for each: what was the customer or the downstream system told at the moment of the
75
+ first event? Every out-of-order defect gets its severity from what had already been
76
+ promised, not from the record's final state.
77
+
78
+ simulating_the_provider: >
79
+ Where the system under test offers provider behaviour profiles — healthy, silent, duplicate,
80
+ late, contradictory — those are the specification of what the integration is supposed to
81
+ survive, and they should be exercised one by one and named in the coverage map. Where it does
82
+ not offer them, the equivalent is a mode where the platform schedules nothing and the tester
83
+ sends every event by hand: that mode is worth more than all the others combined, because it
84
+ is the only one that gives deterministic control of timing, ordering and concurrency. Reach
85
+ for it by default, and use a real profile only when the provider's own behaviour is the
86
+ subject of the test.
87
+
88
+ common_mistakes:
89
+ - "Testing the callback endpoint only through the happy path the platform itself triggers."
90
+ - "Assuming the documented dedup key is the implemented one."
91
+ - "Reading a 200 as success without checking what the body says was actually done."
92
+ - "Treating an unmatchable event as a low-value case; it is how collected money goes uncredited."
93
+ - "Reporting 'the endpoint is authenticated' nowhere, so the reader cannot tell it was checked."
94
+
95
+ relationship_to_other_entries: >
96
+ The receiving half of technique-exactly-once-verification, which covers the ledger effects.
97
+ Shares its result-reading vocabulary with technique-silent-failure-audit, and its
98
+ identity-and-scope discipline with technique-authenticated-api-probing.