qualiow-exploratory-testing 1.2.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.
- package/.claude-plugin/plugin.json +22 -0
- package/.env.example +27 -0
- package/CHANGELOG.md +194 -0
- package/README.md +428 -179
- package/agents/qa-gather-agent.md +24 -0
- package/{scripts → bin}/doctor-mobile.sh +57 -18
- package/bin/mcli +15 -9
- package/bin/mobile-cli.mjs +574 -286
- package/{scripts → bin}/setup-mobile.sh +56 -19
- package/bin/wadb +10 -4
- package/bin/wk-ios +29 -17
- package/bin/wkeval.mjs +7 -1
- package/data/domains/_default.yml +1 -1
- package/data/domains/identity.yml +138 -0
- package/data/knowledge/changelog.yml +104 -0
- package/data/knowledge/learned-patterns.md +172 -86
- package/data/knowledge/manifest.yml +481 -70
- package/data/knowledge/releases/v0.1.0/entries/technique-business-logic-race-conditions.yml +1 -1
- package/data/knowledge/releases/v0.1.0/release.yml +8 -1
- package/data/knowledge/releases/v0.2.0/entries/technique-contract-narrowing.yml +150 -0
- package/data/knowledge/releases/v0.2.0/entries/technique-test-suite-audit.yml +116 -0
- package/data/knowledge/releases/v0.2.0/release.yml +20 -0
- package/data/knowledge/releases/v0.3.0/entries/technique-functional-diff-analysis.yml +119 -0
- package/data/knowledge/releases/v0.3.0/entries/technique-llm-output-verification.yml +102 -0
- package/data/knowledge/releases/v0.3.0/entries/technique-verification-mode-selection.yml +153 -0
- package/data/knowledge/releases/v0.3.0/release.yml +25 -0
- package/data/knowledge/releases/v0.4.0/entries/technique-authenticated-api-probing.yml +137 -0
- package/data/knowledge/releases/v0.4.0/entries/technique-environment-fingerprinting.yml +113 -0
- package/data/knowledge/releases/v0.4.0/entries/technique-silent-failure-audit.yml +86 -0
- package/data/knowledge/releases/v0.4.0/entries/technique-ui-api-differential.yml +97 -0
- package/data/knowledge/releases/v0.4.0/release.yml +28 -0
- package/data/knowledge/releases/v0.5.0/entries/technique-config-surface-verification.yml +77 -0
- package/data/knowledge/releases/v0.5.0/entries/technique-derived-value-verification.yml +81 -0
- package/data/knowledge/releases/v0.5.0/entries/technique-expected-behaviour-specification.yml +97 -0
- package/data/knowledge/releases/v0.5.0/entries/technique-presentation-integrity.yml +78 -0
- package/data/knowledge/releases/v0.5.0/entries/technique-release-readiness-verification.yml +110 -0
- package/data/knowledge/releases/v0.5.0/release.yml +33 -0
- package/data/knowledge/releases/v0.6.0/entries/technique-async-callback-contracts.yml +98 -0
- package/data/knowledge/releases/v0.6.0/entries/technique-exactly-once-verification.yml +116 -0
- package/data/knowledge/releases/v0.6.0/release.yml +30 -0
- package/data/security/SECURITY-POLICY.md +273 -0
- package/data/targets/_default.yml +1 -1
- package/data/targets/_example-api-only.yml +80 -0
- package/data/targets/_example-backend.yml +123 -0
- package/data/targets/_example-mobile-emulation.yml +2 -2
- package/data/targets/_example-native-mobile.yml +2 -2
- package/data/targets/_example-sim-android-chrome.yml +1 -1
- package/data/targets/_example-sim-ios-safari.yml +1 -1
- package/data/templates/api-probe-matrix.md +99 -0
- package/data/templates/bug-report.md +29 -151
- package/data/templates/coverage-map.md +23 -6
- package/data/templates/expected-behaviour.md +94 -0
- package/data/templates/session-charter.md +3 -0
- package/data/templates/session-report.md +57 -80
- package/dist/cli/index.js +1500 -739
- package/dist/index.d.ts +673 -75
- package/dist/index.js +1664 -270
- package/docs/BACKEND-VERIFICATION.md +307 -0
- package/docs/GETTING-STARTED.md +188 -128
- package/docs/MOBILE-SETUP.md +149 -18
- package/package.json +32 -16
- package/skills/qa-explore/SKILL.md +31 -25
- package/skills/qa-explore/phases/00-setup.md +67 -41
- package/skills/qa-explore/phases/01-auth.md +32 -15
- package/skills/qa-explore/phases/02-charter.md +16 -5
- package/skills/qa-explore/phases/03-discovery.md +50 -26
- package/skills/qa-explore/phases/04-journeys.md +2 -2
- package/skills/qa-explore/phases/05-features.md +39 -24
- package/skills/qa-explore/phases/06-edge-cases.md +24 -13
- package/skills/qa-explore/phases/07-reporting.md +79 -140
- package/skills/qa-explore/references/context-integration.md +1 -1
- package/skills/qa-explore/references/output-contract.md +187 -0
- package/skills/qa-explore/references/paths.md +84 -0
- package/skills/qa-explore/references/playwright-agents-integration.md +61 -84
- package/skills/qa-explore/references/security-rules.md +66 -25
- package/skills/qa-explore/references/severity-guide.md +31 -4
- package/skills/qa-explore-cleanup/SKILL.md +17 -6
- package/skills/qa-explore-feedback/SKILL.md +18 -5
- package/skills/qa-explore-mobile/SKILL.md +86 -64
- package/skills/qa-explore-mobile/phases/00-setup.md +71 -62
- package/skills/qa-explore-mobile/phases/01-auth.md +28 -31
- package/skills/qa-explore-mobile/phases/02-charter.md +8 -4
- package/skills/qa-explore-mobile/phases/03-discovery.md +17 -11
- package/skills/qa-explore-mobile/phases/04-journeys.md +6 -6
- package/skills/qa-explore-mobile/phases/05-features.md +9 -9
- package/skills/qa-explore-mobile/phases/06-edge-cases.md +35 -40
- package/skills/qa-explore-mobile/phases/07-reporting.md +82 -56
- package/skills/qa-explore-mobile/references/mobile-edges.md +26 -26
- package/skills/qa-explore-quick/SKILL.md +60 -25
- package/skills/qa-explore-report/SKILL.md +40 -34
- package/skills/qa-gather/SKILL.md +17 -2
- package/skills/qa-knowledge-add/SKILL.md +20 -9
- package/skills/qa-knowledge-list/SKILL.md +12 -3
- package/skills/qa-target-setup/SKILL.md +63 -41
- package/skills/qa-verify-backend/SKILL.md +172 -0
- package/skills/qa-verify-backend/phases/00-setup.md +142 -0
- package/skills/qa-verify-backend/phases/01-ac-decomposition.md +58 -0
- package/skills/qa-verify-backend/phases/02-static-review.md +71 -0
- package/skills/qa-verify-backend/phases/03-live-verification.md +62 -0
- package/skills/qa-verify-backend/phases/03b-api-verification.md +170 -0
- package/skills/qa-verify-backend/phases/04-e2e-trigger.md +82 -0
- package/skills/qa-verify-backend/phases/05-reporting.md +163 -0
- package/skills/qa-verify-backend/references/api-probes.md +168 -0
- package/skills/qa-verify-backend/references/aws-readonly-probes.md +156 -0
- package/skills/qa-verify-backend/references/environment-fingerprinting.md +104 -0
- package/skills/qa-verify-backend/references/payload-verification.md +112 -0
- package/skills/qa-verify-backend/references/release-readiness.md +97 -0
- package/skills/qa-verify-backend/references/safety-rules.md +95 -0
- package/dist/cli/index.d.ts +0 -1
- package/dist/cli/index.js.map +0 -1
- package/dist/index.js.map +0 -1
|
@@ -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
|
-
|
|
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
|
|
|
@@ -30,91 +82,6 @@ _None yet — patterns added here will be skipped in future sessions._
|
|
|
30
82
|
- Price calculations: test with discounts, tax, multiple quantities, $0 totals
|
|
31
83
|
- Test ALL user personas if multiple exist — each may have different bugs
|
|
32
84
|
|
|
33
|
-
### Checkout Interaction Patterns (from production monitoring + 100+ historical bugs)
|
|
34
|
-
|
|
35
|
-
**Session & Basket State:**
|
|
36
|
-
- **Modal dismiss + navigate back**: Reserve seat → dismiss login modal (X) → navigate back. Check: "failed to delete basket" console errors? Seats released?
|
|
37
|
-
- **Multiple tabs**: Open checkout in 2 tabs → ticket/site branding mismatches, theme changes, session conflicts - **Session timer off-focus**: Minimize browser → timer may slow down or stop counting
|
|
38
|
-
- **Session expiry modal**: Let timer expire → "Cancel Order" button should NOT navigate to 404
|
|
39
|
-
- **Session TTL**: Orders may be deleted before user completes if session TTL is too short
|
|
40
|
-
- **Basket refetch on focus**: After switching tabs and coming back, basket view may not update
|
|
41
|
-
|
|
42
|
-
**Payment Patterns:**
|
|
43
|
-
- **Duplicate payment callbacks**: PayPal or 3DS can trigger multiple callbacks → duplicate payments
|
|
44
|
-
- **3DS with no paymentMethodId**: 3DS callback called without payment method → fails
|
|
45
|
-
- **3DS retry after failure**: Cancel 3DS → retry → check "payment method not found" errors
|
|
46
|
-
- **Apple Pay failures**: Indefinite loading when Apple Pay fails
|
|
47
|
-
- **Google Pay**: May not work on certain environments
|
|
48
|
-
- **Zero value basket**: Free tickets → billing should show "Confirm your order" and actually work
|
|
49
|
-
- **Voucher + retry**: Selecting voucher on retry page may incorrectly show PayPal button
|
|
50
|
-
- **Payment form issues**: Amex CVV placeholder may be wrong
|
|
51
|
-
- **Payment options accessibility**: Payment selector may not be keyboard accessible
|
|
52
|
-
|
|
53
|
-
**Navigation & Back Button:**
|
|
54
|
-
- **Back button Safari/Firefox**: Browser back may fail to trigger seat release
|
|
55
|
-
- **Back from payment**: May cause endless loop
|
|
56
|
-
- **Back from contacts**: Never loads seatmap, gets stuck
|
|
57
|
-
- **Back from calendar**: May redirect to homepage or 404
|
|
58
|
-
- **Auto scroll persists**: Page scroll position carries over from previous page
|
|
59
|
-
|
|
60
|
-
**Login & Auth:**
|
|
61
|
-
- **Page refresh after login**: Form loses user details, profile icon shows logged-out, CPS 400 errors
|
|
62
|
-
- **New accounts**: May get stuck in endless loop during checkout
|
|
63
|
-
- **Required login flow**: Can trigger "Unexpected Application Error!" on contacts page intermittently
|
|
64
|
-
- **Guest → login transition**: On voucher flow, refresh after login breaks the form
|
|
65
|
-
|
|
66
|
-
**Delivery & Contacts:**
|
|
67
|
-
- **Skip contacts page**: Reaching payment without delivery method selection → "delivery method ID missing" errors
|
|
68
|
-
- **Customer country data**: May create customer record with wrong country
|
|
69
|
-
- **Delivery method misalignment**: Methods may not match what's expected
|
|
70
|
-
|
|
71
|
-
**Upsells & Extras:**
|
|
72
|
-
- **Upsell removal race condition**: If basket refetches while upsell removal is in-flight, removed upsell reappears and can't be removed
|
|
73
|
-
- **Lounge toggle quantity**: Toggle should add packages × ticket count, not just 1
|
|
74
|
-
- **Unavailable upsells**: Should notify user, not silently fail
|
|
75
|
-
- **Slow lounge addition**: Large ticket count → upsell reservation times out
|
|
76
|
-
- **Upsell ordering**: Should match CMS configuration, not random
|
|
77
|
-
- **Last upsell removal**: Removing the last non-ticket upsell may delete the entire AV session
|
|
78
|
-
|
|
79
|
-
**Ticket Protection:**
|
|
80
|
-
- **TP links wrong region**: UK shows US terms, US shows UK terms
|
|
81
|
-
- **TP purchased multiple times**: Should only be purchasable once
|
|
82
|
-
- **TP skip/redirect**: May skip TP page due to timer expiry logic
|
|
83
|
-
- **TP endless loading**: Can get stuck between TP and payment
|
|
84
|
-
- **TP error handling**: TP service errors should let user continue to payment
|
|
85
|
-
- **TP blocking checkout**: Basket update during TP should block progression until complete
|
|
86
|
-
|
|
87
|
-
**Fees & Pricing:**
|
|
88
|
-
- **Fee copy when no fees**: Shows fee text even when there are no fees
|
|
89
|
-
- **Fees display incorrect**: Basket summary may show wrong fee amounts
|
|
90
|
-
- **Decimal price rejection**: Some tickets rejected because basket API doesn't accept decimal totals
|
|
91
|
-
- **Currency symbol wrong region**: £ symbol showing in US totals
|
|
92
|
-
- **Upsell prices misaligned**: Price formatting inconsistent
|
|
93
|
-
|
|
94
|
-
**Themes & Branding:**
|
|
95
|
-
- **Theme changes post-seatmap**: Theme may reset after navigating back
|
|
96
|
-
- **Theme loading delay**: Visible flash of wrong theme
|
|
97
|
-
- **US domains redirecting to UK**: Links in footer, confirmation, error pages go to UK
|
|
98
|
-
- **Favicons**: Should show new ATG Entertainment logo
|
|
99
|
-
|
|
100
|
-
**Confirmation & Post-Purchase:**
|
|
101
|
-
- **Confirmation page guard**: Should NOT be accessible without completing payment
|
|
102
|
-
- **Confirmation header not clickable**: Users get locked in
|
|
103
|
-
- **Continue to checkout button on confirmation**: Should not appear
|
|
104
|
-
- **Order confirmation CTA**: Should go to correct region MyAccount
|
|
105
|
-
|
|
106
|
-
**Copy & Legal:**
|
|
107
|
-
- **Basket expired modal copy**: Should be correct for all shows/themes
|
|
108
|
-
- **Payment retry phone numbers**: Must be correct per US region
|
|
109
|
-
- **Legal links with www**: Should not have www prefix
|
|
110
|
-
- **Error page phone numbers**: Must be region-appropriate
|
|
111
|
-
- **Voucher copy**: Gift card terminology for US
|
|
112
|
-
|
|
113
|
-
**Security:**
|
|
114
|
-
- **OWASP A01 Broken Access Control**: Basket summary had access control issue
|
|
115
|
-
- **XSS in calendar service**: ReDoS vulnerability
|
|
116
|
-
- **Comp ticket exposure**: Internal pricing visible to regular users
|
|
117
|
-
|
|
118
85
|
### Fintech
|
|
119
86
|
- Session IDs should never appear in URLs (security risk)
|
|
120
87
|
- Admin pages should require authentication
|
|
@@ -123,3 +90,122 @@ _None yet — patterns added here will be skipped in future sessions._
|
|
|
123
90
|
- Verify transactions appear in BOTH sender and receiver account histories
|
|
124
91
|
- Check for MFA/2FA on sensitive operations
|
|
125
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`.
|