qualiow-exploratory-testing 1.1.0 → 1.3.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 (79) hide show
  1. package/README.md +177 -0
  2. package/bin/mcli +16 -0
  3. package/bin/mobile-cli.mjs +573 -0
  4. package/bin/wadb +6 -0
  5. package/bin/wk-ios +58 -0
  6. package/bin/wkeval.mjs +44 -0
  7. package/data/domains/_default.md +181 -0
  8. package/data/domains/ecommerce.md +192 -0
  9. package/data/domains/fintech.md +200 -0
  10. package/data/domains/identity.md +88 -0
  11. package/data/domains/identity.yml +138 -0
  12. package/data/domains/marketing.md +194 -0
  13. package/data/domains/saas.md +197 -0
  14. package/data/knowledge/changelog.yml +86 -0
  15. package/data/knowledge/learned-patterns.md +172 -1
  16. package/data/knowledge/manifest.yml +210 -4
  17. package/data/knowledge/releases/v0.2.0/entries/technique-contract-narrowing.yml +150 -0
  18. package/data/knowledge/releases/v0.2.0/entries/technique-test-suite-audit.yml +116 -0
  19. package/data/knowledge/releases/v0.2.0/release.yml +20 -0
  20. package/data/knowledge/releases/v0.3.0/entries/technique-functional-diff-analysis.yml +119 -0
  21. package/data/knowledge/releases/v0.3.0/entries/technique-llm-output-verification.yml +102 -0
  22. package/data/knowledge/releases/v0.3.0/entries/technique-verification-mode-selection.yml +153 -0
  23. package/data/knowledge/releases/v0.3.0/release.yml +25 -0
  24. package/data/knowledge/releases/v0.4.0/entries/technique-authenticated-api-probing.yml +137 -0
  25. package/data/knowledge/releases/v0.4.0/entries/technique-environment-fingerprinting.yml +113 -0
  26. package/data/knowledge/releases/v0.4.0/entries/technique-silent-failure-audit.yml +86 -0
  27. package/data/knowledge/releases/v0.4.0/entries/technique-ui-api-differential.yml +97 -0
  28. package/data/knowledge/releases/v0.4.0/release.yml +28 -0
  29. package/data/knowledge/releases/v0.5.0/entries/technique-config-surface-verification.yml +77 -0
  30. package/data/knowledge/releases/v0.5.0/entries/technique-derived-value-verification.yml +81 -0
  31. package/data/knowledge/releases/v0.5.0/entries/technique-expected-behaviour-specification.yml +97 -0
  32. package/data/knowledge/releases/v0.5.0/entries/technique-presentation-integrity.yml +78 -0
  33. package/data/knowledge/releases/v0.5.0/entries/technique-release-readiness-verification.yml +110 -0
  34. package/data/knowledge/releases/v0.5.0/release.yml +33 -0
  35. package/data/targets/_example-backend.yml +123 -0
  36. package/data/targets/_example-mobile-emulation.yml +52 -0
  37. package/data/targets/_example-native-mobile.yml +61 -0
  38. package/data/targets/_example-sim-android-chrome.yml +81 -0
  39. package/data/targets/_example-sim-ios-safari.yml +80 -0
  40. package/data/templates/api-probe-matrix.md +99 -0
  41. package/data/templates/coverage-map.md +14 -0
  42. package/data/templates/expected-behaviour.md +93 -0
  43. package/dist/cli/index.js +137 -5
  44. package/dist/cli/index.js.map +1 -1
  45. package/dist/index.d.ts +350 -527
  46. package/dist/index.js +144 -5
  47. package/dist/index.js.map +1 -1
  48. package/docs/BACKEND-VERIFICATION.md +277 -0
  49. package/docs/MOBILE-SETUP.md +92 -0
  50. package/package.json +26 -12
  51. package/scripts/doctor-mobile.sh +143 -0
  52. package/scripts/setup-mobile.sh +213 -0
  53. package/skills/qa-explore/phases/00-setup.md +8 -1
  54. package/skills/qa-explore/phases/01-auth.md +4 -0
  55. package/skills/qa-explore-mobile/SKILL.md +146 -0
  56. package/skills/qa-explore-mobile/phases/00-setup.md +203 -0
  57. package/skills/qa-explore-mobile/phases/01-auth.md +127 -0
  58. package/skills/qa-explore-mobile/phases/02-charter.md +70 -0
  59. package/skills/qa-explore-mobile/phases/03-discovery.md +79 -0
  60. package/skills/qa-explore-mobile/phases/04-journeys.md +49 -0
  61. package/skills/qa-explore-mobile/phases/05-features.md +72 -0
  62. package/skills/qa-explore-mobile/phases/06-edge-cases.md +157 -0
  63. package/skills/qa-explore-mobile/phases/07-reporting.md +123 -0
  64. package/skills/qa-explore-mobile/references/mobile-edges.md +117 -0
  65. package/skills/qa-explore-quick/SKILL.md +6 -0
  66. package/skills/qa-verify-backend/SKILL.md +163 -0
  67. package/skills/qa-verify-backend/phases/00-setup.md +97 -0
  68. package/skills/qa-verify-backend/phases/01-ac-decomposition.md +58 -0
  69. package/skills/qa-verify-backend/phases/02-static-review.md +71 -0
  70. package/skills/qa-verify-backend/phases/03-live-verification.md +62 -0
  71. package/skills/qa-verify-backend/phases/03b-api-verification.md +157 -0
  72. package/skills/qa-verify-backend/phases/04-e2e-trigger.md +66 -0
  73. package/skills/qa-verify-backend/phases/05-reporting.md +135 -0
  74. package/skills/qa-verify-backend/references/api-probes.md +141 -0
  75. package/skills/qa-verify-backend/references/aws-readonly-probes.md +156 -0
  76. package/skills/qa-verify-backend/references/environment-fingerprinting.md +104 -0
  77. package/skills/qa-verify-backend/references/payload-verification.md +112 -0
  78. package/skills/qa-verify-backend/references/release-readiness.md +97 -0
  79. package/skills/qa-verify-backend/references/safety-rules.md +90 -0
@@ -2,6 +2,92 @@
2
2
  # Tracks what changed in each release so /qa-knowledge-list can show history.
3
3
 
4
4
  releases:
5
+ - version: "0.5.0"
6
+ date: "2026-09-03"
7
+ summary: "Payload correctness and release-level verification — what to do with the answer once you have it, and how to report a set of tickets rather than one."
8
+ entries_added:
9
+ - id: technique-derived-value-verification
10
+ type: technique
11
+ name: "Derived Value Verification - Recomputing the Number and Naming What It Does Not Prove"
12
+ description: "Recompute every percentage, total, ratio and aggregate from the raw figures in the same response, using the formula from the spec rather than the code. Choose cases that stress sign, zero, scale and cardinality, add the structural invariants, then state explicitly that internal consistency is not correctness and name the independent oracle that would close the gap."
13
+ - id: technique-presentation-integrity
14
+ type: technique
15
+ name: "Presentation Integrity - Does the Screen Show What the Service Sent?"
16
+ description: "A correct payload can still reach the user as a wrong number. Formatting helpers that guess what a value is, units applied twice, rounding across a threshold, truncation shown as a total. Invisible from either surface alone, and routinely attributed to the wrong change."
17
+ - id: technique-expected-behaviour-specification
18
+ type: technique
19
+ name: "Expected Behaviour Specification - Writing the Spec That Should Have Existed"
20
+ description: "Observed against expected, per area rather than per case, with the reject-or-clamp and error-or-empty decisions made explicit, ranked by what users can reach today, and closed with a plain-English reply for whoever decides to fund the fix."
21
+ - id: technique-config-surface-verification
22
+ type: technique
23
+ name: "Config & Feature-Flag Surface Verification"
24
+ description: "When the configuration mechanism is itself the change: values matching the deployed config rather than the source default, nothing leaking alongside them, the runtime genuinely reading through the surface rather than around it, and the route existing in every environment the change will be promoted to."
25
+ - id: technique-release-readiness-verification
26
+ type: technique
27
+ name: "Release Readiness Verification - Many Tickets, One Build"
28
+ description: "Establish what is deployed before testing anything, give every ticket a result from a fixed vocabulary that keeps not-testable and not-tested visible, mark code-verified-only as UNVERIFIABLE rather than green, separate carry-overs, and end with a disposition and the condition that would reverse it."
29
+ entries_modified: []
30
+ entries_removed: []
31
+ origin: "Sessions that verified calculated values, multi-ticket releases and a feature-flag surface exposed the gaps: derived values signed off from a single payload, screens signed off without the payload beside them, findings with no acceptance criterion to file them against, and release reports where a code reading looked the same colour as an observation."
32
+
33
+ - version: "0.4.0"
34
+ date: "2026-09-03"
35
+ summary: "The HTTP/API verification lane — how to probe a service's own endpoints with real credentials, and how to know the environment is running the code you are judging."
36
+ entries_added:
37
+ - id: technique-environment-fingerprinting
38
+ type: technique
39
+ name: "Environment Fingerprinting - Proving What Is Actually Running"
40
+ description: "Before the first probe: which build is deployed in every component of the path, whether the changed code path is SELECTED here, and whether the commit under test is an ancestor of what is running. Same build plus different behaviour means configuration, not deploy lag. Adds NOT-REACHABLE as the honest verdict when the change is not live in the environment being measured."
41
+ - id: technique-authenticated-api-probing
42
+ type: technique
43
+ name: "Authenticated API Probing - Calling the Endpoint Behind the Screen"
44
+ description: "Get a real authenticated request context without handling a token by running fetch inside the already-logged-in page, then drive a written case matrix through it. Ten case families, how to read each signal, and the evidence and safety rules that keep credentials and response bodies off disk."
45
+ - id: technique-ui-api-differential
46
+ type: technique
47
+ name: "UI-vs-API Differential - Running the Same Matrix at Both Surfaces"
48
+ description: "Sort every finding into reproducible-at-both, API-only, UI-only and neither. Corrects the most common false PASS in exploratory testing: a client-side guard recorded as the endpoint's behaviour."
49
+ - id: technique-silent-failure-audit
50
+ type: technique
51
+ name: "Silent Failure Audit - Failures That Render as Ordinary Results"
52
+ description: "Seven shapes of failure that look like a legitimate empty or zero answer, how to force each one, and why they recur as a class rather than as individual bugs."
53
+ entries_modified: []
54
+ entries_removed: []
55
+ origin: "Paired UI and API sessions on the same features showed three gaps: the endpoint was never called directly, so client-side guards were being recorded as endpoint behaviour; environments were compared without checking which implementation each one ran; and the same silent-failure defect kept being filed as unrelated one-off bugs."
56
+
57
+ - version: "0.3.0"
58
+ date: "2026-08-21"
59
+ summary: "The BE/API verification layer — how to actually observe a backend, API or LLM change, and how to say so when you cannot."
60
+ entries_added:
61
+ - id: technique-verification-mode-selection
62
+ type: technique
63
+ name: "Verification Mode Selection - Choosing How to Observe a Backend Change"
64
+ description: "Route each AC to the observation channel that can falsify it: API-behind-the-screen, direct request to a no-UI endpoint, LLM output judgement, or needs-a-human. Makes UNVERIFIABLE a first-class verdict instead of a PASS inferred from source."
65
+ - id: technique-functional-diff-analysis
66
+ type: technique
67
+ name: "Functional Diff Analysis - Reading a Backend Change for Behaviour, Not Style"
68
+ description: "Eight passes over a BE/API/LLM diff that produce falsifiable hypotheses rather than code comments: spec drift, value tracing to the service boundary, failure paths, identity propagation, producer/consumer contract, scope, and the tests that shipped with it."
69
+ - id: technique-llm-output-verification
70
+ type: technique
71
+ name: "LLM & Agent Output Verification - Running It and Judging the Result"
72
+ description: "Fixed input set, written rubric, before-and-after on the same inputs, N runs to expose variance, assertions on properties and tool trajectory rather than on generated text. Includes what not to claim from a passing run."
73
+ entries_modified: []
74
+ entries_removed: []
75
+ origin: "Built after two backend ticket verifications showed the gap: deep judgement and real test execution existed for the UI, but backend, API and LLM changes were being signed off by reading the diff."
76
+
77
+ - version: "0.2.0"
78
+ date: "2026-08-20"
79
+ summary: "Backend AC-verification techniques derived from real /qa-verify-backend sessions — both aimed at changes that fail silently by construction."
80
+ entries_added:
81
+ - id: technique-contract-narrowing
82
+ type: technique
83
+ name: "Contract Narrowing - Verifying a Swapped Data Source"
84
+ description: "When a full-record read is replaced by a projection, the request's field-selection list becomes the payload specification. Trace every consumed field to a selection token; unrequested fields vanish with no error, no DLQ, and a green suite."
85
+ - id: technique-test-suite-audit
86
+ type: technique
87
+ name: "Auditing the Branch's Own Tests"
88
+ description: "When a change rewrites the tests that are meant to prove it works, those tests become part of the change. Check that each assertion still falsifies what its name claims, and that artefacts named by an AC actually exist."
89
+ origin: "A read-path swap on an event-processing service — a full-record read replaced by a projection read. The contract-narrowing audit found a dropped webhook field that 175 green unit tests could not see; the test audit found an e2e negative scenario that could only pass when the system was broken."
90
+
5
91
  - version: "0.1.0"
6
92
  date: "2026-03-28"
7
93
  summary: "Initial knowledge base — core heuristics, techniques, checklists, and references for exploratory testing."
@@ -4,7 +4,59 @@ _Seeded from community exploratory testing sessions. Add your own via /qa-explor
4
4
 
5
5
  ## False Positive Patterns (skip these)
6
6
 
7
- _None yet — patterns added here will be skipped in future sessions._
7
+ Findings that looked real on a first read and did not survive tracing. Check the
8
+ disqualifier before filing any of these.
9
+
10
+ - **"Errors are swallowed instead of retried"** (backend queue handlers): before filing, read the
11
+ wrapper that invokes the handler. A `return false` and a thrown exception often converge on the
12
+ same partial-batch-failure path, so retry and DLQ semantics are identical. *Disqualifier: the
13
+ wrapper's catch block reports the same unprocessed records the `false` path does.*
14
+ - **"Alerting severity regressed from fatal to error"**: check the logger's metric config first.
15
+ If `pushOnError` and `pushOnFatal` are both true, nothing changes operationally. *Disqualifier:
16
+ both flags set.*
17
+ - **"This cleanup/deletion script is dangerous"**: read it to the end before calling it a safety
18
+ defect. Dry-run defaults, cross-checks against another source of truth, and fail-closed error
19
+ handling are common and often present. *Disqualifier: it dry-runs by default and aborts rather
20
+ than proceeding when its safety check fails.* Scope creep may still be a valid, separate finding.
21
+ - **"The branch's tests fail"** — rule out your own harness first. A mis-resolved workspace
22
+ dependency, stale build, or wrong Node version produces errors that look exactly like product
23
+ defects. *Disqualifier: it passes once the harness is corrected.* File nothing until you have
24
+ re-run clean.
25
+ - **"A value never arrives / is never written"**: trace it to the persistence or serialization
26
+ layer before claiming absence. *Disqualifier: some earlier step already stamps it.*
27
+ - **"No evidence record exists, so the work was not done"**: absence of an evidence record is not
28
+ evidence of absence. *Disqualifier: measuring the data shows it is already in the desired state.*
29
+ - **"The result count changed, so it is a regression"**: counts drift with the data and differ per
30
+ environment. *Disqualifier: the two numbers come from different environments, or from runs days
31
+ apart on a collection that changes.* Compare status codes and response shapes instead.
32
+ - **"It behaves differently in staging, so the deploy is broken"**: check the configuration before
33
+ the deployment. *Disqualifier: both environments report the same build, and a flag or config
34
+ value selects a different code path in each.* That is still a finding — just a different one.
35
+ - **"It only reproduces after editing client-side storage / typing a URL the product never
36
+ surfaces"**: no user vector, so not a defect on its own. *Disqualifier: no affordance anywhere in
37
+ the product reaches that state.* **Then go looking for one** — see the triage patterns below,
38
+ because this disqualifier is wrong more often than any other on this list.
39
+ - **"The behaviour is inconsistent across surfaces"** where the requirement was never written:
40
+ route it to product as a requirements gap and a negative-space observation, not as a bug.
41
+ *Disqualifier: no acceptance criterion, spec or design covers it, and both behaviours are
42
+ defensible.*
43
+
44
+ ## Triage and Re-Verification Patterns
45
+
46
+ - **"Closed: no legitimate user vector" is a hypothesis to falsify, not a fact.** When a bug is
47
+ closed because "users cannot reach this", the next session on that surface must actively hunt
48
+ for vectors the triage did not consider — alternative menu entries, help and onboarding
49
+ affordances, query parameters, deep links, other clients. A defect closed on this rationale and
50
+ left broken for a release is a recurring, expensive pattern.
51
+ - **"Partial fix" is the most common re-test outcome.** A fix typically addresses the reported
52
+ symptom, not the defect class. When re-verifying anything marked fixed, test the class: the same
53
+ code path with a different trigger, and structurally equivalent surfaces built from the same
54
+ component or pattern. Re-running only the original repro will pass and prove very little.
55
+ - **Re-verify against a build, not against a date.** Record the build id or commit of every
56
+ component when the bug was found and again when it is re-tested. A re-run against the same build
57
+ cannot surface a fix, and "it was merged" is not "it is deployed".
58
+ - **A fix behind a flag that is off is not a fix.** Re-testing in the one environment where the
59
+ flag is on says nothing about the environments users are in. Say both halves.
8
60
 
9
61
  ## Missed Bug Patterns (always check these)
10
62
 
@@ -38,3 +90,122 @@ _None yet — patterns added here will be skipped in future sessions._
38
90
  - Verify transactions appear in BOTH sender and receiver account histories
39
91
  - Check for MFA/2FA on sensitive operations
40
92
  - Loan approval should enforce documented requirements (down payment thresholds, terms disclosure)
93
+
94
+ ### Backend / API / event-driven (no UI surface)
95
+
96
+ - **A swapped read path is the whole risk.** "Replace X with Y" tickets on a read path are rarely
97
+ mechanical, however small the diff. See `technique-contract-narrowing`.
98
+ - **`SELECT *` -> projection drops fields silently.** Trace every field the downstream mapper reads
99
+ to the selection token that requests it. The gap table written in the ticket is a claim to
100
+ falsify, not a specification to trust.
101
+ - **Assert on the serialized payload, not the object.** `JSON.stringify` omits `undefined` keys, so
102
+ a mapper that always assigns the key still publishes a payload without it.
103
+ - **"Structurally identical" needs a differential test.** One record, both paths, diff the output.
104
+ If the branch does not contain that test, the AC is unverified no matter how green the suite is.
105
+ - **Optional-everywhere schemas hide missing data.** Zod `.optional()` / TS optional means the
106
+ response parses fine with the field gone. Tests asserting "parses" and "does not throw" cannot
107
+ falsify equivalence.
108
+ - **Check what an AC names before scoring it.** ACs cite Cucumber scenarios, suites, or dashboards
109
+ that sometimes do not exist. That is an AC defect to report, not something to reinterpret.
110
+ - **Producers cannot observe downstream filtering.** A test claiming to verify routing must read
111
+ the router or the consumer (rule metrics, target state, DLQ depth) — never the producer's logs.
112
+ - **Log-scraping oracles hide a LOG_LEVEL dependency.** If the asserted line is `logger.debug`, the
113
+ suite silently requires debug logging, and "broken flow" is indistinguishable from "quiet logs".
114
+ - **Read the infra value, do not infer it.** A committed `.tf` value is not proof of a deployed
115
+ attribute. Without account access the verdict is `BLOCKED` — write the probe commands out ready
116
+ to run rather than inferring `PASS` from source.
117
+ - **Scan the diff for what the ticket did not ask for.** Lockfile regenerations, CI jobs, steering
118
+ docs, and validation tweaks ride along and consume the review attention the real change needed.
119
+ - **Grep committed files for real identifiers.** UIDs, customer emails, and staff contacts turn up
120
+ in incident notes and fixtures. In any system handling personal data that is a compliance
121
+ finding, not just untidiness.
122
+ - **Ask whether anyone consumes the field.** A dropped field nobody reads is a documentation fix,
123
+ not a code fix. Say so explicitly — it is usually answerable only by the consuming team, and
124
+ naming that unknown is more useful than assuming severity.
125
+
126
+ ### HTTP endpoints — what a browser can never show you
127
+
128
+ - **Fingerprint before you probe.** Which build is deployed in every component of the path, and
129
+ whether the changed path is even selected here. Same build plus different behaviour means
130
+ configuration, not deploy lag. See `technique-environment-fingerprinting`.
131
+ - **A client-side guard is not the endpoint's contract.** "The button is disabled until you type"
132
+ describes the browser. Call the endpoint the way the guard is preventing before recording a
133
+ `PASS` — an empty body, a filter with no query, a pagination value the control cannot produce.
134
+ These are the cases that reach every non-browser client. See `technique-ui-api-differential`.
135
+ - **`200` is not a pass.** A login page returns `200`. So does an error body, a zero-row page with a
136
+ non-zero count, and a silently rejected filter value. Read the body.
137
+ - **Group the crash family.** Nine inputs that `500` on the same unescaped character are one bug
138
+ with nine examples. Find the shared character before writing anything up.
139
+ - **Metacharacters are ordinary when the data contains them.** If real values carry brackets,
140
+ colons or asterisks, copying a value out of a result and pasting it back in is a normal user
141
+ action — and the fastest route from an "edge case" to a customer report.
142
+ - **Probe the four kinds of nothing separately.** Empty string, `null`, whitespace-only and the
143
+ field absent are four different requests, and they routinely behave four different ways. One of
144
+ them is often a match-all that returns the entire collection.
145
+ - **Check the cap is code, not documentation.** A `limit` above the documented maximum that is
146
+ honoured anyway is both an availability risk and a bulk-extraction path.
147
+ - **An invalid enum answered with `200` and an empty list will be read as data.** Expect a `4xx`
148
+ with an error body; silent rejection is a finding. See `technique-silent-failure-audit`.
149
+ - **Repeat one read as a second identity and in a second scope.** A read that ignores tenant,
150
+ market or ownership is a data-exposure finding no UI session will surface.
151
+ - **Compare shapes across environments, never counts.** Different data, drifting under you.
152
+ - **Run the request from inside the authenticated page.** `fetch` with the session's own cookies
153
+ needs no token plumbing, survives SSO and MFA, and keeps the credential in the browser where it
154
+ belongs. See `technique-authenticated-api-probing`.
155
+
156
+ ### Calculated values and what reaches the screen
157
+
158
+ - **Recompute every derived value from the raw figures in the same response**, using the formula
159
+ from the spec — not from the code under test. Recomputing the implementation's own arithmetic
160
+ proves only that arithmetic is deterministic.
161
+ - **Then say what that does not prove.** Both sides came from one payload, so you verified the
162
+ derivation and not the inputs. Name the independent oracle that would close it and whether you
163
+ ran it. See `technique-derived-value-verification`.
164
+ - **Pick a negative, a zero, a very large and a very small value, and a single-item case.** Sign
165
+ handling is where derivation breaks; a single-item aggregate is the cleanest comparison against
166
+ any second system, with no aggregation ambiguity.
167
+ - **Add the structural invariants** — a total equal to the sum of its parts, one metric bounded by
168
+ another, a derived cost positive. Cheap, and they generalise past the cases you picked.
169
+ - **Hold the raw response next to the screen.** A correct payload still reaches the user wrong when
170
+ a formatter guesses what a value is (`value > 1 ? value : value * 100`), a unit is applied twice,
171
+ rounding crosses a threshold, or a truncated figure is presented as a total.
172
+ - **A self-contradicting tile is the tell** — a percentage printed above the fraction it came from,
173
+ and the two disagree. One of them is a lie.
174
+ - **Attribute a rendering defect to the change that owns it.** It is usually not the backend ticket
175
+ that surfaced it, and it is frequently deployed on one environment and not another. Say plainly
176
+ when the change under test is not at fault. See `technique-presentation-integrity`.
177
+ - **Consistent is not causal.** A locale, currency or format setting whose current value happens to
178
+ match the output proves nothing until you change the setting and watch the output follow.
179
+ - **Measure timing in the page, cold and warm.** Wrap the request in `performance.now()` and record
180
+ the first, second and third call. A cold path an order of magnitude slower is the number every
181
+ user gets first, and no averaged dashboard shows it.
182
+
183
+ ### Reporting a set of tickets
184
+
185
+ - **Establish what is deployed before testing anything.** A ticket whose backend is not in the
186
+ build is *not testable here* — testing its UI produces a convincing, meaningless result that
187
+ looks exactly like a data bug and gets filed as one.
188
+ - **Keep "not tested" visible.** It disappears between "passed" and "failed" unless the vocabulary
189
+ has a slot for it, and so does "not testable here".
190
+ - **Mark a code reading differently from an observation.** 🔍 code-verified-only is `UNVERIFIABLE`,
191
+ not green.
192
+ - **Carry-overs get their own section.** Pre-existing defects mixed into a release's results
193
+ inflate the apparent risk of shipping it and bury the findings that belong to it.
194
+ - **A deploy landing mid-session invalidates everything measured before it.** Re-fingerprint, keep
195
+ the pre-deploy findings in their own file, and never merge the two into one table.
196
+ - **State the tolerance on any baseline comparison.** A few per cent on a large live collection is
197
+ churn. And when a system-wide figure and a per-user figure disagree, name which one describes the
198
+ behaviour the change actually altered.
199
+ - **Close with a disposition and its reversal condition**, plus the scope of what you checked when
200
+ it is narrower than the question being asked. See `technique-release-readiness-verification`.
201
+
202
+ ### Findings with no acceptance criterion
203
+
204
+ - **Write the spec instead of filing ten bugs.** Group by cause, put observed against expected, and
205
+ make the decisions explicit: reject or clamp (reject — silent correction breaks callers that
206
+ trust the value back); an error or an empty result (an error — a silent zero is read as data);
207
+ where validation lives (the layer covering every implementation, never only the client).
208
+ - **Rank by what users can reach today**, not by how bad each finding reads. Name which one is live
209
+ in production and which only exists in an environment nobody ships from.
210
+ - **Finish with a plain-English reply.** The section that gets the work scheduled is the one the
211
+ person funding the fix can read. See `technique-expected-behaviour-specification`.
@@ -1,16 +1,20 @@
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.1.0"
5
- last_updated: "2026-03-28"
4
+ version: "0.5.0"
5
+ last_updated: "2026-09-03"
6
6
 
7
7
  active_releases:
8
8
  - "v0.1.0"
9
+ - "v0.2.0"
10
+ - "v0.3.0"
11
+ - "v0.4.0"
12
+ - "v0.5.0"
9
13
 
10
14
  stats:
11
- total_entries: 13
15
+ total_entries: 27
12
16
  heuristics: 5
13
- techniques: 5
17
+ techniques: 19
14
18
  checklists: 1
15
19
  references: 2
16
20
  domain_profiles: 0
@@ -39,10 +43,114 @@ loading_strategy:
39
43
  - checklist-accessibility-wcag
40
44
  regression:
41
45
  - heuristic-rcrcrc
46
+ - technique-environment-fingerprinting
47
+ - technique-silent-failure-audit
42
48
  risk:
43
49
  - technique-risk-based-testing
44
50
  data-integrity:
45
51
  - technique-data-integrity-testing
52
+ - technique-contract-narrowing
53
+ - technique-derived-value-verification
54
+ - technique-presentation-integrity
55
+ calculations:
56
+ - technique-derived-value-verification
57
+ - technique-presentation-integrity
58
+ oracles:
59
+ - technique-derived-value-verification
60
+ - heuristic-few-hiccupps
61
+ requirements:
62
+ - technique-expected-behaviour-specification
63
+ reporting:
64
+ - technique-expected-behaviour-specification
65
+ - technique-release-readiness-verification
66
+ release:
67
+ - technique-release-readiness-verification
68
+ - technique-environment-fingerprinting
69
+ coverage:
70
+ - technique-release-readiness-verification
71
+ configuration:
72
+ - technique-config-surface-verification
73
+ - technique-environment-fingerprinting
74
+ backend:
75
+ - technique-contract-narrowing
76
+ - technique-test-suite-audit
77
+ - technique-verification-mode-selection
78
+ - technique-functional-diff-analysis
79
+ - technique-environment-fingerprinting
80
+ - technique-authenticated-api-probing
81
+ - technique-ui-api-differential
82
+ api:
83
+ - technique-verification-mode-selection
84
+ - technique-functional-diff-analysis
85
+ - technique-authenticated-api-probing
86
+ - technique-ui-api-differential
87
+ - technique-environment-fingerprinting
88
+ api-contract:
89
+ - technique-contract-narrowing
90
+ - technique-functional-diff-analysis
91
+ - technique-authenticated-api-probing
92
+ verification:
93
+ - technique-verification-mode-selection
94
+ - technique-llm-output-verification
95
+ - technique-environment-fingerprinting
96
+ - technique-authenticated-api-probing
97
+ evidence:
98
+ - technique-verification-mode-selection
99
+ - technique-llm-output-verification
100
+ - technique-environment-fingerprinting
101
+ - technique-authenticated-api-probing
102
+ environment:
103
+ - technique-environment-fingerprinting
104
+ deployment:
105
+ - technique-environment-fingerprinting
106
+ - technique-config-surface-verification
107
+ - technique-release-readiness-verification
108
+ feature-flags:
109
+ - technique-environment-fingerprinting
110
+ - technique-config-surface-verification
111
+ error-handling:
112
+ - technique-silent-failure-audit
113
+ - technique-error-guessing
114
+ silent-failure:
115
+ - technique-silent-failure-audit
116
+ - technique-contract-narrowing
117
+ - technique-ui-api-differential
118
+ differential:
119
+ - technique-ui-api-differential
120
+ ui:
121
+ - technique-ui-api-differential
122
+ - technique-silent-failure-audit
123
+ - technique-presentation-integrity
124
+ observability:
125
+ - technique-silent-failure-audit
126
+ negative-testing:
127
+ - technique-error-guessing
128
+ - technique-authenticated-api-probing
129
+ - technique-silent-failure-audit
130
+ boundaries:
131
+ - technique-boundary-testing
132
+ - technique-authenticated-api-probing
133
+ llm:
134
+ - technique-llm-output-verification
135
+ - technique-verification-mode-selection
136
+ - technique-functional-diff-analysis
137
+ agent:
138
+ - technique-llm-output-verification
139
+ code-review:
140
+ - technique-functional-diff-analysis
141
+ - technique-test-suite-audit
142
+ acceptance-criteria:
143
+ - technique-verification-mode-selection
144
+ - technique-functional-diff-analysis
145
+ - technique-test-suite-audit
146
+ - technique-expected-behaviour-specification
147
+ - technique-release-readiness-verification
148
+ test-quality:
149
+ - technique-test-suite-audit
150
+ refactor:
151
+ - technique-contract-narrowing
152
+ - technique-test-suite-audit
153
+ - technique-verification-mode-selection
46
154
  exploration:
47
155
  - reference-exploratory-testing-types
48
156
  - reference-heuristic-praxis
@@ -139,3 +247,101 @@ entries:
139
247
  priority: high
140
248
  tags: [heuristics, praxis, theory, meta-testing, reflection]
141
249
  domains: [all]
250
+
251
+ - id: technique-contract-narrowing
252
+ file: releases/v0.2.0/entries/technique-contract-narrowing.yml
253
+ type: technique
254
+ priority: high
255
+ tags: [backend, api-contract, integration, data-integrity, refactor, silent-failure, regression]
256
+ domains: [all]
257
+
258
+ - id: technique-test-suite-audit
259
+ file: releases/v0.2.0/entries/technique-test-suite-audit.yml
260
+ type: technique
261
+ 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
+
272
+ - id: technique-functional-diff-analysis
273
+ file: releases/v0.3.0/entries/technique-functional-diff-analysis.yml
274
+ type: technique
275
+ priority: high
276
+ tags: [backend, api, code-review, static-analysis, acceptance-criteria, llm, scope-creep, regression]
277
+ domains: [all]
278
+
279
+ - id: technique-llm-output-verification
280
+ file: releases/v0.3.0/entries/technique-llm-output-verification.yml
281
+ type: technique
282
+ 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
288
+ type: technique
289
+ priority: high
290
+ tags: [backend, api, verification, evidence, deployment, feature-flags, environment, acceptance-criteria, regression]
291
+ domains: [all]
292
+
293
+ - id: technique-authenticated-api-probing
294
+ file: releases/v0.4.0/entries/technique-authenticated-api-probing.yml
295
+ type: technique
296
+ 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
302
+ type: technique
303
+ priority: high
304
+ tags: [api, backend, ui, verification, differential, error-handling, silent-failure, acceptance-criteria, regression]
305
+ domains: [all]
306
+
307
+ - id: technique-silent-failure-audit
308
+ file: releases/v0.4.0/entries/technique-silent-failure-audit.yml
309
+ type: technique
310
+ 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
316
+ type: technique
317
+ 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
323
+ type: technique
324
+ priority: high
325
+ tags: [ui, api, data-integrity, verification, differential, calculations, regression, error-handling]
326
+ domains: [all]
327
+
328
+ - id: technique-expected-behaviour-specification
329
+ file: releases/v0.5.0/entries/technique-expected-behaviour-specification.yml
330
+ type: technique
331
+ 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
337
+ type: technique
338
+ priority: medium
339
+ tags: [backend, api, feature-flags, environment, security, configuration, deployment, verification]
340
+ domains: [all]
341
+
342
+ - id: technique-release-readiness-verification
343
+ file: releases/v0.5.0/entries/technique-release-readiness-verification.yml
344
+ type: technique
345
+ priority: high
346
+ tags: [regression, release, deployment, reporting, coverage, risk, acceptance-criteria, verification, environment]
347
+ domains: [all]