qualiow-exploratory-testing 1.2.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.
- package/README.md +92 -0
- package/data/domains/_default.md +181 -0
- package/data/domains/ecommerce.md +192 -0
- package/data/domains/fintech.md +200 -0
- package/data/domains/identity.md +88 -0
- package/data/domains/identity.yml +138 -0
- package/data/domains/marketing.md +194 -0
- package/data/domains/saas.md +197 -0
- package/data/knowledge/changelog.yml +86 -0
- package/data/knowledge/learned-patterns.md +172 -86
- package/data/knowledge/manifest.yml +211 -6
- 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/targets/_example-backend.yml +123 -0
- package/data/templates/api-probe-matrix.md +99 -0
- package/data/templates/coverage-map.md +14 -0
- package/data/templates/expected-behaviour.md +93 -0
- package/dist/cli/index.js +79 -70
- package/dist/cli/index.js.map +1 -1
- package/dist/index.d.ts +90 -0
- package/dist/index.js +58 -49
- package/dist/index.js.map +1 -1
- package/docs/BACKEND-VERIFICATION.md +277 -0
- package/package.json +5 -3
- package/skills/qa-verify-backend/SKILL.md +163 -0
- package/skills/qa-verify-backend/phases/00-setup.md +97 -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 +157 -0
- package/skills/qa-verify-backend/phases/04-e2e-trigger.md +66 -0
- package/skills/qa-verify-backend/phases/05-reporting.md +135 -0
- package/skills/qa-verify-backend/references/api-probes.md +141 -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 +90 -0
package/README.md
CHANGED
|
@@ -179,6 +179,96 @@ Notes that save time:
|
|
|
179
179
|
/qa-target-setup
|
|
180
180
|
```
|
|
181
181
|
|
|
182
|
+
## How to Verify Backend Acceptance Criteria
|
|
183
|
+
|
|
184
|
+
Not every acceptance criterion is visible in a browser. `/qa-verify-backend` covers tickets
|
|
185
|
+
whose ACs live below the UI — tables and streams, queue consumers, Lambda triggers, IAM
|
|
186
|
+
policies, webhooks, IaC, and the service's own HTTP endpoints — and produces an **AC
|
|
187
|
+
traceability matrix** instead of a pass/fail claim.
|
|
188
|
+
|
|
189
|
+
```bash
|
|
190
|
+
# Copy the template, point it at your service, then verify a ticket branch
|
|
191
|
+
cp data/targets/_example-backend.yml data/targets/local-my-service.yml
|
|
192
|
+
|
|
193
|
+
/qa-verify-backend --target local-my-service --context output/context/TICKET-123-context.md
|
|
194
|
+
/qa-verify-backend --target local-my-service --static-only # no cloud credentials
|
|
195
|
+
/qa-verify-backend --target local-my-service --api-only --parity local-my-service-staging
|
|
196
|
+
```
|
|
197
|
+
|
|
198
|
+
It runs four lanes:
|
|
199
|
+
|
|
200
|
+
| Lane | What it does |
|
|
201
|
+
|------|--------------|
|
|
202
|
+
| **Static** | Reads the implementation branch against each AC with `git show` (never checks out) — spec drift, scope creep, failure paths, identity propagation, producer/consumer contract breaks |
|
|
203
|
+
| **Live** | Read-only `aws-cli` probes, one per AC, raw output saved as evidence. Never mutates; hard stop on production |
|
|
204
|
+
| **API** | Calls the service's own endpoints from the already-authenticated page, with a written case matrix covering everything the browser's guards prevent. Read-only, limited to the target's `api.probe_allowlist` |
|
|
205
|
+
| **End-to-end** | Drives the real write path in a non-production environment, then re-probes the data layer — including same-tick writes, deletes, bulk saves, a second identity, and DLQ depth |
|
|
206
|
+
|
|
207
|
+
Each AC gets a verdict with cited evidence — `PASS`, `PARTIAL`, `FAIL`, `BLOCKED`,
|
|
208
|
+
`NOT-REACHABLE` or `UNVERIFIABLE` — and the verdict **names the mode it was reached by and the
|
|
209
|
+
environment it holds in**. `PASS (direct request, raw response attached)` and `PASS (read the
|
|
210
|
+
diff)` are different claims, and a verdict backed only by a code reading is `UNVERIFIABLE`,
|
|
211
|
+
never `PASS`. `BLOCKED` is a first-class outcome: when credentials are missing, the probe
|
|
212
|
+
commands are written out ready to run rather than the verdict being inferred from source.
|
|
213
|
+
|
|
214
|
+
### Two things it will not let you get away with
|
|
215
|
+
|
|
216
|
+
**Believing a green result from an environment that does not run your code.** Before the first
|
|
217
|
+
probe, the skill fingerprints every component of the request path: which build is deployed,
|
|
218
|
+
whether the changed path is *selected* here, and whether the commit under test is genuinely an
|
|
219
|
+
ancestor of what is running. One identical build can hold two implementations of the same
|
|
220
|
+
feature with a flag choosing between them — *same build, different behaviour ⇒ configuration,
|
|
221
|
+
not deploy lag*. An environment that does not run the change gets `NOT-REACHABLE`.
|
|
222
|
+
|
|
223
|
+
**Recording a client-side guard as the endpoint's behaviour.** "The search box refuses to fire
|
|
224
|
+
when empty" describes the browser. Every other client — mobile, partner integration, script —
|
|
225
|
+
sends that request, and it is frequently the one that fails. When a ticket has both a screen
|
|
226
|
+
and an endpoint, the same cases run at both surfaces and each finding is sorted into *both*,
|
|
227
|
+
*API only* (a real defect the guard is hiding), *UI only* (the client invents or masks
|
|
228
|
+
behaviour the service does not have) or *neither*.
|
|
229
|
+
|
|
230
|
+
The API lane needs no token handling: the request runs inside the page that is already logged
|
|
231
|
+
in, so it carries the same session cookie, CSRF token and interceptors as the UI — which also
|
|
232
|
+
means it works with SSO and MFA that no scripted login can pass. Credentials stay in the
|
|
233
|
+
browser profile under `.auth/` and never enter a script, a report or the repository.
|
|
234
|
+
|
|
235
|
+
### Correct shape is not a correct answer
|
|
236
|
+
|
|
237
|
+
Every derived value — a percentage, total, ratio, delta or aggregate — is recomputed from the
|
|
238
|
+
raw figures in the same response, with the formula taken from the specification rather than from
|
|
239
|
+
the code under test, and with cases chosen to stress sign, zero, scale and cardinality. Then the
|
|
240
|
+
report states the limitation plainly: when both sides of the check come from one payload, the
|
|
241
|
+
derivation is verified and the inputs are not, so the **independent oracle** that would close
|
|
242
|
+
the gap is named along with whether it was run.
|
|
243
|
+
|
|
244
|
+
The payload is also held next to the screen, because a correct response can still reach the user
|
|
245
|
+
as a wrong number — a formatter that guesses what a value is, a unit applied twice, a truncated
|
|
246
|
+
figure presented as a total. That defect is invisible from either surface alone, and it usually
|
|
247
|
+
belongs to a different change than the one under test.
|
|
248
|
+
|
|
249
|
+
### Findings with no acceptance criterion become a spec
|
|
250
|
+
|
|
251
|
+
Most of what an API probe turns up has nothing to be filed against, so it turns into an argument
|
|
252
|
+
rather than a fix. `data/templates/expected-behaviour.md` converts a pile of observations into
|
|
253
|
+
one reviewable decision: observed against expected, grouped by cause, with the decisions the fix
|
|
254
|
+
forces made explicit — reject rather than clamp, an error rather than a silent zero, validation
|
|
255
|
+
at the layer that covers every implementation — ranked by what real users can reach today, and
|
|
256
|
+
closed with a plain-English reply for whoever decides to fund the work.
|
|
257
|
+
|
|
258
|
+
### Verifying a release rather than a ticket
|
|
259
|
+
|
|
260
|
+
`.claude/skills/qa-verify-backend/references/release-readiness.md` changes the shape of the
|
|
261
|
+
session: the deployment table first
|
|
262
|
+
for every ticket, so a ticket whose backend is not in the build is marked *not testable here*
|
|
263
|
+
rather than tested against a UI that will render convincing nonsense; a result vocabulary that
|
|
264
|
+
keeps *not tested* visible; a coverage map where 🔍 *code-verified only* is marked as
|
|
265
|
+
`UNVERIFIABLE` rather than green, with one sentence naming the untested item that carries the
|
|
266
|
+
most risk; carry-over defects in their own section; and a disposition with the condition that
|
|
267
|
+
would reverse it.
|
|
268
|
+
|
|
269
|
+
Full guide: **`docs/BACKEND-VERIFICATION.md`**. Safety rules (read-only discipline, the
|
|
270
|
+
production hard stop, redaction): `.claude/skills/qa-verify-backend/references/safety-rules.md`.
|
|
271
|
+
|
|
182
272
|
## How to Generate Reports
|
|
183
273
|
|
|
184
274
|
qualiow produces three report formats from session data.
|
|
@@ -220,6 +310,7 @@ const csv = await generateJiraExport('output/sessions/2026-03-28-parabank');
|
|
|
220
310
|
| `/qa-explore` | Full exploratory testing session (45 min) |
|
|
221
311
|
| `/qa-explore-mobile` | Exploratory session on a simulator/emulator — native apps or mobile web in the real device browser (iOS Safari / Android Chrome) |
|
|
222
312
|
| `/qa-explore-quick` | Quick focused session on a single page or feature (15 min) |
|
|
313
|
+
| `/qa-verify-backend` | Verify backend/API/infra acceptance criteria with no UI surface — branch review, read-only cloud probes, direct API probes, AC traceability matrix |
|
|
223
314
|
| `/qa-explore-report` | Generate or regenerate report from existing session |
|
|
224
315
|
| `/qa-explore-feedback` | Post-session feedback capture (false positives, missed bugs) |
|
|
225
316
|
| `/qa-explore-cleanup` | Session cleanup and archival |
|
|
@@ -263,6 +354,7 @@ qualiow-exploratory-testing-skills/
|
|
|
263
354
|
benchmarks/ # performance benchmarks
|
|
264
355
|
docs/
|
|
265
356
|
GETTING-STARTED.md # detailed setup and usage guide
|
|
357
|
+
BACKEND-VERIFICATION.md # verifying ACs with no UI surface
|
|
266
358
|
ARCHITECTURE-DECISIONS.md # architecture decision records
|
|
267
359
|
```
|
|
268
360
|
|
|
@@ -0,0 +1,181 @@
|
|
|
1
|
+
# Default Domain: Generic Web Application
|
|
2
|
+
|
|
3
|
+
## Priority Areas
|
|
4
|
+
|
|
5
|
+
1. **Core Functionality** - Forms, navigation, and primary user flows work correctly
|
|
6
|
+
2. **Authentication & Authorization** - Login, logout, session management, protected routes
|
|
7
|
+
3. **Error Handling** - Graceful failures, meaningful error messages, recovery paths
|
|
8
|
+
4. **Responsive Design** - Layout integrity across viewport sizes
|
|
9
|
+
5. **Accessibility** - Keyboard navigation, screen reader basics, color contrast
|
|
10
|
+
6. **Performance** - Page load times, interaction responsiveness
|
|
11
|
+
7. **SEO Fundamentals** - Meta tags, heading structure, crawlability
|
|
12
|
+
|
|
13
|
+
## Feature Risk Ranking Guide
|
|
14
|
+
|
|
15
|
+
> Assign a priority tier to every feature before testing. Spend the most time on P0, then P1, and so on. Adjust based on domain-specific risk.
|
|
16
|
+
|
|
17
|
+
| Tier | Meaning | Time Allocation | Criteria |
|
|
18
|
+
|------|--------------------------------|-----------------|--------------------------------------------------------------------------|
|
|
19
|
+
| P0 | Must work perfectly | ~40% of effort | Revenue-generating, security-critical, or legally required. Failure = outage or data loss. |
|
|
20
|
+
| P1 | Must work correctly | ~30% of effort | Core user journeys and frequently used features. Failure = major user frustration. |
|
|
21
|
+
| P2 | Should work correctly | ~20% of effort | Supporting features that enhance the experience. Failure = degraded but usable. |
|
|
22
|
+
| P3 | Nice to have working | ~10% of effort | Informational pages, rarely used settings, cosmetic polish. Failure = minor annoyance. |
|
|
23
|
+
|
|
24
|
+
**How to rank a feature:**
|
|
25
|
+
1. Ask: "If this feature is broken, does the business lose money or get sued?" -- If yes, P0.
|
|
26
|
+
2. Ask: "If this feature is broken, do users fail their primary task?" -- If yes, P1.
|
|
27
|
+
3. Ask: "If this feature is broken, do users notice and complain?" -- If yes, P2.
|
|
28
|
+
4. Everything else is P3.
|
|
29
|
+
|
|
30
|
+
## Completeness Checklist
|
|
31
|
+
|
|
32
|
+
> Minimum features and states every web application should have. Test for the *existence* of these before deep-diving into any single feature.
|
|
33
|
+
|
|
34
|
+
### Navigation & Structure
|
|
35
|
+
- [ ] Logo links to homepage
|
|
36
|
+
- [ ] Primary navigation is present and functional on all pages
|
|
37
|
+
- [ ] Footer is present with expected links (privacy, terms, contact)
|
|
38
|
+
- [ ] Breadcrumbs reflect the current location (if applicable)
|
|
39
|
+
- [ ] 404 page exists and is user-friendly (not a raw server error)
|
|
40
|
+
- [ ] 500 error page exists and is user-friendly
|
|
41
|
+
|
|
42
|
+
### Authentication Flows (if applicable)
|
|
43
|
+
- [ ] Registration flow completes end to end
|
|
44
|
+
- [ ] Login flow works with valid credentials
|
|
45
|
+
- [ ] Logout clears session and redirects appropriately
|
|
46
|
+
- [ ] Password reset flow sends email and allows reset
|
|
47
|
+
- [ ] Protected pages redirect to login when unauthenticated
|
|
48
|
+
|
|
49
|
+
### Empty States
|
|
50
|
+
- [ ] Empty list/table shows a helpful message (not a blank page)
|
|
51
|
+
- [ ] Empty search results suggest alternatives or show a clear message
|
|
52
|
+
- [ ] New user with no data sees onboarding or guidance, not emptiness
|
|
53
|
+
|
|
54
|
+
### Content Essentials
|
|
55
|
+
- [ ] No placeholder text (lorem ipsum, "TODO", "TBD")
|
|
56
|
+
- [ ] No broken images or missing media
|
|
57
|
+
- [ ] Copyright year is current
|
|
58
|
+
- [ ] Legal pages are linked and accessible (privacy policy, terms of service)
|
|
59
|
+
|
|
60
|
+
### Functional Basics
|
|
61
|
+
- [ ] All forms submit and provide feedback (success or error)
|
|
62
|
+
- [ ] All buttons and links lead somewhere (no dead ends)
|
|
63
|
+
- [ ] Loading states exist for async operations (no frozen UI)
|
|
64
|
+
- [ ] Back button behavior is consistent and does not break state
|
|
65
|
+
|
|
66
|
+
## Data Integrity Checks
|
|
67
|
+
|
|
68
|
+
> After every state-changing action (create, update, delete, submit), verify these:
|
|
69
|
+
|
|
70
|
+
1. **Persistence** -- Reload the page. Does the change survive? Is the data still correct?
|
|
71
|
+
2. **Reflection** -- Does the change appear everywhere it should? (List views, detail views, summaries, exports.)
|
|
72
|
+
3. **Consistency** -- Do calculated values (totals, counts, timestamps) update correctly?
|
|
73
|
+
4. **Reversibility** -- If the action can be undone (delete, cancel), does the system return to a clean state?
|
|
74
|
+
5. **Concurrency** -- If two users (or two tabs) act on the same data, does the system handle it without silent data loss?
|
|
75
|
+
6. **Cascade** -- If the changed item is referenced elsewhere (e.g., a category that contains products), are related items updated or handled?
|
|
76
|
+
|
|
77
|
+
## Cross-Feature Journeys
|
|
78
|
+
|
|
79
|
+
> Test these generic end-to-end flows that cross multiple features. Bugs often hide at the seams between features.
|
|
80
|
+
|
|
81
|
+
### Journey 1: New User Onboarding
|
|
82
|
+
`Register -> Verify Email -> Login -> Complete Profile -> Use Primary Feature -> Logout`
|
|
83
|
+
- Verify: session persists correctly through each step, data entered in earlier steps is visible later, logout clears everything.
|
|
84
|
+
|
|
85
|
+
### Journey 2: Content Lifecycle
|
|
86
|
+
`Create Item -> View in List -> Edit Item -> Verify Changes -> Delete Item -> Verify Removal`
|
|
87
|
+
- Verify: item appears in all relevant views after creation, edits persist after reload, deletion removes item from all views and does not leave orphaned references.
|
|
88
|
+
|
|
89
|
+
### Journey 3: Error Recovery
|
|
90
|
+
`Start Action -> Force Error (disconnect network, submit invalid data) -> See Error State -> Retry -> Complete Successfully`
|
|
91
|
+
- Verify: error messages are clear, no data is lost or duplicated on retry, system returns to a consistent state.
|
|
92
|
+
|
|
93
|
+
## Must-Test Patterns
|
|
94
|
+
|
|
95
|
+
### Forms
|
|
96
|
+
- Required field validation (submit empty, partial, complete)
|
|
97
|
+
- Input boundary values (min/max length, special characters, Unicode)
|
|
98
|
+
- Email and URL format validation
|
|
99
|
+
- Date and number field constraints
|
|
100
|
+
- Form submission with network interruption
|
|
101
|
+
- Double-submit prevention
|
|
102
|
+
- Tab order through form fields
|
|
103
|
+
- Error message clarity and placement
|
|
104
|
+
|
|
105
|
+
### Navigation
|
|
106
|
+
- All internal links resolve (no 404s)
|
|
107
|
+
- Browser back/forward behavior is consistent
|
|
108
|
+
- Deep linking and bookmarking work
|
|
109
|
+
- Breadcrumbs reflect actual location
|
|
110
|
+
- Menu states (open, close, hover, focus)
|
|
111
|
+
- Navigation on mobile (hamburger menu, touch targets)
|
|
112
|
+
|
|
113
|
+
### Authentication
|
|
114
|
+
- Login with valid and invalid credentials
|
|
115
|
+
- Password reset flow end to end
|
|
116
|
+
- Session timeout behavior
|
|
117
|
+
- Concurrent session handling
|
|
118
|
+
- Remember me functionality
|
|
119
|
+
- Logout clears session data
|
|
120
|
+
- Protected pages redirect to login
|
|
121
|
+
|
|
122
|
+
### Error Handling
|
|
123
|
+
- 404 page for invalid URLs
|
|
124
|
+
- Server error pages (500) are user-friendly
|
|
125
|
+
- Network timeout behavior
|
|
126
|
+
- Invalid input error messages are helpful
|
|
127
|
+
- Form validation errors do not lose user input
|
|
128
|
+
- API failure graceful degradation
|
|
129
|
+
|
|
130
|
+
### Responsive Design
|
|
131
|
+
- Layout at 320px, 768px, 1024px, 1440px widths
|
|
132
|
+
- Images scale without distortion
|
|
133
|
+
- Text remains readable at all sizes
|
|
134
|
+
- Touch targets are at least 44x44px on mobile
|
|
135
|
+
- No horizontal scrolling on mobile
|
|
136
|
+
- Modals and popups work on small screens
|
|
137
|
+
|
|
138
|
+
### Accessibility
|
|
139
|
+
- All images have alt text
|
|
140
|
+
- Form fields have associated labels
|
|
141
|
+
- Focus indicators are visible
|
|
142
|
+
- Color is not the only indicator of state
|
|
143
|
+
- Page has a logical heading hierarchy (h1-h6)
|
|
144
|
+
- Skip navigation link is present
|
|
145
|
+
- ARIA roles are used correctly where needed
|
|
146
|
+
|
|
147
|
+
### Performance
|
|
148
|
+
- Initial page load under 3 seconds
|
|
149
|
+
- Time to interactive is reasonable
|
|
150
|
+
- Large images are optimized
|
|
151
|
+
- No excessive DOM size
|
|
152
|
+
- No memory leaks on repeated interactions
|
|
153
|
+
- Lazy loading for below-the-fold content
|
|
154
|
+
|
|
155
|
+
### SEO
|
|
156
|
+
- Each page has a unique title tag
|
|
157
|
+
- Meta descriptions are present and descriptive
|
|
158
|
+
- Heading hierarchy is semantic
|
|
159
|
+
- Canonical URLs are set
|
|
160
|
+
- Robots.txt and sitemap.xml are accessible
|
|
161
|
+
- Open Graph and Twitter Card meta tags present
|
|
162
|
+
|
|
163
|
+
## Common Bugs
|
|
164
|
+
|
|
165
|
+
- Broken links after content updates
|
|
166
|
+
- Form submission succeeds silently without confirmation
|
|
167
|
+
- Session expires during long form entry, losing data
|
|
168
|
+
- Mobile menu overlaps content
|
|
169
|
+
- Inconsistent error message styles
|
|
170
|
+
- Missing loading states causing double clicks
|
|
171
|
+
- Stale cache showing outdated content
|
|
172
|
+
- Z-index issues with overlapping modals and dropdowns
|
|
173
|
+
- Autofill conflicts with custom input components
|
|
174
|
+
- Scroll position not restored on back navigation
|
|
175
|
+
|
|
176
|
+
## Compliance Requirements
|
|
177
|
+
|
|
178
|
+
- WCAG 2.1 Level AA (baseline accessibility)
|
|
179
|
+
- GDPR cookie consent if applicable
|
|
180
|
+
- HTTPS everywhere
|
|
181
|
+
- Privacy policy and terms of service links accessible
|
|
@@ -0,0 +1,192 @@
|
|
|
1
|
+
# Domain: E-Commerce
|
|
2
|
+
|
|
3
|
+
## Priority Areas
|
|
4
|
+
|
|
5
|
+
1. **Checkout Flow** - Cart to payment confirmation must be rock solid
|
|
6
|
+
2. **Payment Processing** - All payment methods work, edge cases handled
|
|
7
|
+
3. **Product Catalog** - Search, filter, sort, and display accuracy
|
|
8
|
+
4. **Pricing & Calculations** - Discounts, coupons, tax, and totals are precise
|
|
9
|
+
5. **Inventory Management** - Stock levels, availability, and oversell prevention
|
|
10
|
+
6. **User Accounts** - Registration, profiles, order history, saved addresses
|
|
11
|
+
7. **Shipping & Returns** - Rate calculation, tracking, return/refund flows
|
|
12
|
+
|
|
13
|
+
## Feature Risk Ranking
|
|
14
|
+
|
|
15
|
+
| Tier | Features | Rationale |
|
|
16
|
+
|------|-------------------------------------------------------|------------------------------------------------------------------|
|
|
17
|
+
| P0 | Checkout, payment processing, cart, pricing/totals | Direct revenue. A broken checkout = lost sales. A pricing bug = financial loss or legal liability. |
|
|
18
|
+
| P1 | Product catalog, search, authentication | Users cannot buy what they cannot find. Auth gates the account experience. |
|
|
19
|
+
| P2 | Reviews & ratings, wishlist, filters & sort | Enhance discovery and trust but do not block purchase. |
|
|
20
|
+
| P3 | About page, contact page, social media links | Informational. Rarely blocks a transaction. |
|
|
21
|
+
|
|
22
|
+
## Completeness Checklist
|
|
23
|
+
|
|
24
|
+
> Minimum features an e-commerce site should have. Verify these exist and function before deep-testing.
|
|
25
|
+
|
|
26
|
+
- [ ] Cart displays items with name, image, price, and quantity
|
|
27
|
+
- [ ] Cart quantity can be increased, decreased, and item removed
|
|
28
|
+
- [ ] Empty cart shows a helpful message and a link to continue shopping
|
|
29
|
+
- [ ] Delivery/shipping address form with validation
|
|
30
|
+
- [ ] Payment method selector (at least one method functional)
|
|
31
|
+
- [ ] Order summary visible before final confirmation with itemized totals
|
|
32
|
+
- [ ] Order confirmation page with a unique order ID
|
|
33
|
+
- [ ] Confirmation email or receipt sent after purchase
|
|
34
|
+
- [ ] Order history accessible from user account
|
|
35
|
+
- [ ] Guest checkout option (or clear account creation prompt)
|
|
36
|
+
|
|
37
|
+
## Data Integrity Checks
|
|
38
|
+
|
|
39
|
+
> After every state-changing action in e-commerce, verify these calculations and data flows.
|
|
40
|
+
|
|
41
|
+
1. **Item price x quantity = line total** -- Check for every line item in the cart and in the order confirmation. Watch for rounding issues with discounts.
|
|
42
|
+
2. **All line totals + shipping + tax - discounts = order total** -- Verify on the cart page, checkout summary, confirmation page, and confirmation email. All four should match.
|
|
43
|
+
3. **Inventory decremented after purchase** -- If stock count is visible, verify it decreases by the purchased quantity. Verify out-of-stock messaging appears when inventory hits zero.
|
|
44
|
+
4. **Order appears in history** -- After completing checkout, the order should immediately appear in the user's order history with correct items, quantities, totals, and status.
|
|
45
|
+
5. **Coupon/discount applied correctly** -- Discount shows as a line item, subtotal adjusts, and the discount does not apply to items it should not (e.g., excluded categories).
|
|
46
|
+
6. **Price consistency** -- The price on the product page, in the cart, at checkout, and on the confirmation must all match (accounting for any discounts applied).
|
|
47
|
+
|
|
48
|
+
## Cross-Feature Journeys
|
|
49
|
+
|
|
50
|
+
> These end-to-end flows cross multiple features. Bugs hide at the boundaries.
|
|
51
|
+
|
|
52
|
+
### Journey 1: Browse to Purchase
|
|
53
|
+
`Browse Catalog -> Add to Cart -> Proceed to Checkout -> Enter Shipping -> Select Payment -> Confirm Order -> View Order History`
|
|
54
|
+
- Verify: item details persist from catalog through confirmation, totals are correct at every step, order appears in history with correct status.
|
|
55
|
+
|
|
56
|
+
### Journey 2: Search to Purchase
|
|
57
|
+
`Search for Product -> Apply Filters -> Open Product Detail -> Select Variant -> Add to Cart -> Checkout`
|
|
58
|
+
- Verify: search results match filters, selected variant (size/color) carries into cart correctly, price reflects variant choice.
|
|
59
|
+
|
|
60
|
+
### Journey 3: Full Account Lifecycle
|
|
61
|
+
`Register -> Login -> Browse -> Add to Cart -> Purchase -> Logout -> Login Again -> View Order History`
|
|
62
|
+
- Verify: registration completes, cart persists across login, order history is accessible after re-login, all data is consistent.
|
|
63
|
+
|
|
64
|
+
## Must-Test Patterns
|
|
65
|
+
|
|
66
|
+
### Product Catalog
|
|
67
|
+
- Search returns relevant results for exact and partial matches
|
|
68
|
+
- Filters narrow results correctly (price range, category, size, color)
|
|
69
|
+
- Sort options work (price low-high, high-low, newest, rating)
|
|
70
|
+
- Product images load and zoom functions work
|
|
71
|
+
- Product variants (size, color) update price and availability
|
|
72
|
+
- Out-of-stock items display clear messaging
|
|
73
|
+
- Pagination or infinite scroll loads correctly
|
|
74
|
+
- Category navigation reflects accurate product counts
|
|
75
|
+
- Recently viewed and related products display correctly
|
|
76
|
+
|
|
77
|
+
### Search
|
|
78
|
+
- Exact product name search
|
|
79
|
+
- Misspelled search terms (fuzzy matching)
|
|
80
|
+
- Search with special characters
|
|
81
|
+
- Empty search submission
|
|
82
|
+
- Search suggestions and autocomplete
|
|
83
|
+
- No results page with helpful alternatives
|
|
84
|
+
- Search within category or filtered results
|
|
85
|
+
|
|
86
|
+
### Cart
|
|
87
|
+
- Add single and multiple items
|
|
88
|
+
- Update quantity (increase, decrease, zero, negative, decimal)
|
|
89
|
+
- Remove items from cart
|
|
90
|
+
- Cart persists across sessions (logged in)
|
|
91
|
+
- Cart persists across sessions (guest via cookie)
|
|
92
|
+
- Cart reflects current prices (not stale cached prices)
|
|
93
|
+
- Cart handles out-of-stock items added before stock depletion
|
|
94
|
+
- Maximum quantity limits enforced
|
|
95
|
+
- Cart total updates in real time
|
|
96
|
+
- Empty cart state displays correctly
|
|
97
|
+
- Cart icon badge count updates immediately
|
|
98
|
+
|
|
99
|
+
### Checkout
|
|
100
|
+
- Guest checkout flow end to end
|
|
101
|
+
- Registered user checkout with saved details
|
|
102
|
+
- Address validation and autocomplete
|
|
103
|
+
- Shipping method selection updates total
|
|
104
|
+
- Order summary accuracy before payment
|
|
105
|
+
- Back button behavior during checkout
|
|
106
|
+
- Checkout with expired session
|
|
107
|
+
- Checkout with empty cart (direct URL access)
|
|
108
|
+
- Order confirmation page with correct details
|
|
109
|
+
- Confirmation email sent with correct content
|
|
110
|
+
|
|
111
|
+
### Payments
|
|
112
|
+
- Credit/debit card processing (valid card)
|
|
113
|
+
- Credit card with invalid number, expired date, wrong CVV
|
|
114
|
+
- PayPal or third-party payment redirect and return
|
|
115
|
+
- Payment failure and retry flow
|
|
116
|
+
- Insufficient funds handling
|
|
117
|
+
- 3D Secure authentication flow
|
|
118
|
+
- Saved payment methods selection
|
|
119
|
+
- Payment timeout handling (gateway slow response)
|
|
120
|
+
- Refund to original payment method
|
|
121
|
+
- Currency display matches user locale
|
|
122
|
+
|
|
123
|
+
### Shipping
|
|
124
|
+
- Shipping rate calculation by weight, destination, method
|
|
125
|
+
- Free shipping threshold display and application
|
|
126
|
+
- Multiple shipping addresses (split shipment)
|
|
127
|
+
- International shipping with customs information
|
|
128
|
+
- Estimated delivery date accuracy
|
|
129
|
+
- Shipping to PO boxes and military addresses
|
|
130
|
+
- Express vs standard shipping option differences
|
|
131
|
+
- Shipping cost updates when address changes
|
|
132
|
+
|
|
133
|
+
### Returns & Refunds
|
|
134
|
+
- Return request initiation within policy window
|
|
135
|
+
- Return request outside policy window (should be denied)
|
|
136
|
+
- Return label generation
|
|
137
|
+
- Refund processing and confirmation
|
|
138
|
+
- Partial returns from multi-item orders
|
|
139
|
+
- Exchange flow for different size or color
|
|
140
|
+
- Return status tracking
|
|
141
|
+
|
|
142
|
+
### Pricing
|
|
143
|
+
- Regular price display
|
|
144
|
+
- Sale price with original price strikethrough
|
|
145
|
+
- Percentage and fixed amount discount application
|
|
146
|
+
- Coupon code entry (valid, invalid, expired, case sensitivity)
|
|
147
|
+
- Stacking rules for multiple discounts
|
|
148
|
+
- Tax calculation by jurisdiction
|
|
149
|
+
- Bundle pricing accuracy
|
|
150
|
+
- Bulk pricing tiers
|
|
151
|
+
- Currency conversion if multi-currency supported
|
|
152
|
+
- Price updates when variant is changed
|
|
153
|
+
|
|
154
|
+
### User Accounts
|
|
155
|
+
- Registration with email verification
|
|
156
|
+
- Social login (Google, Facebook, Apple)
|
|
157
|
+
- Profile update (name, email, password)
|
|
158
|
+
- Address book management (add, edit, delete, set default)
|
|
159
|
+
- Order history with status and details
|
|
160
|
+
- Reorder from previous order
|
|
161
|
+
- Wishlist add, remove, move to cart
|
|
162
|
+
- Account deletion and data removal
|
|
163
|
+
|
|
164
|
+
### Reviews & Ratings
|
|
165
|
+
- Submit a review with star rating and text
|
|
166
|
+
- Review with photo upload
|
|
167
|
+
- Review moderation (pending state)
|
|
168
|
+
- Sort reviews by date, rating, helpfulness
|
|
169
|
+
- Average rating calculation accuracy
|
|
170
|
+
- Review filtering by star count
|
|
171
|
+
- Verified purchase badge display
|
|
172
|
+
|
|
173
|
+
## Common Bugs
|
|
174
|
+
|
|
175
|
+
- **Cart calculation errors** - Rounding issues with discounts, tax computed on wrong subtotal, quantity multiplier off by one
|
|
176
|
+
- **Checkout flow breaks** - Back button causes duplicate order, session timeout loses cart, address validation rejects valid addresses
|
|
177
|
+
- **Payment gateway timeouts** - Order created but payment status unknown, user charged but order not confirmed, retry creates duplicate charge
|
|
178
|
+
- **Inventory sync issues** - Item shows in stock but fails at checkout, overselling due to race condition, stock not restored on cancelled order
|
|
179
|
+
- **Coupon stacking exploits** - Applying multiple exclusive coupons, coupon applied after order total goes negative, expired coupon still works via direct URL
|
|
180
|
+
- **Price display mismatches** - Cart shows different price than product page, currency rounding differs between pages, tax-inclusive vs exclusive confusion
|
|
181
|
+
- **Search relevance issues** - Exact match not in top results, filters reset after pagination, zero results for valid product names
|
|
182
|
+
- **Account edge cases** - Guest checkout email conflicts with existing account, social login does not merge with email account, order history missing after password reset
|
|
183
|
+
- **Mobile checkout** - Payment form keyboard covers input, autofill breaks card number formatting, touch targets too small on shipping options
|
|
184
|
+
|
|
185
|
+
## Compliance Requirements
|
|
186
|
+
|
|
187
|
+
- **PCI DSS** - Payment card data handled securely, no card numbers in logs or URLs
|
|
188
|
+
- **GDPR** - Cookie consent, data export, right to deletion, privacy policy
|
|
189
|
+
- **Consumer protection** - Clear return policy, accurate product descriptions, transparent pricing
|
|
190
|
+
- **Accessibility (WCAG 2.1 AA)** - Full checkout flow usable by keyboard and screen reader
|
|
191
|
+
- **Tax compliance** - Correct tax rates by jurisdiction, tax displayed before final purchase
|
|
192
|
+
- **Email compliance** - CAN-SPAM Act for marketing emails, transactional email opt-out separation
|