Mark
eb2258a880
Move the three load-bearing prototype files from `tests/uat/prototype/`
to their production paths under `tests/uat/`, leaving the architectural
narrative (research findings, BLOCKER citations, falsification table
references) intact. No behavioral changes — A6 still PASSES 5/5 in ~7s
end-to-end from the new paths.
File moves (git mv preserves history):
- tests/uat/prototype/extension-page-harness.html
→ tests/uat/extension-page-harness.html
- tests/uat/prototype/extension-page-harness.ts
→ tests/uat/extension-page-harness.ts
- tests/uat/prototype/a6.test.ts
→ tests/uat/a6.test.ts
The `tests/uat/prototype/` directory is now empty (git does not track
empty directories; will not appear in subsequent `git status`).
Path-reference updates inside the moved files:
- tests/uat/extension-page-harness.html: `<p>` line referencing the
chrome-extension:// URL updated to drop `/prototype/`.
- tests/uat/extension-page-harness.ts: file-header docstring rewritten
to cite Plan 01-13 / Approach B / inheritance from c647f61. The
load-bearing architectural-finding comment block (MV3 SW dynamic-
import block falsification, Approach-B chrome.* surface summary)
is REWORDED but its semantic content + research citations are
PRESERVED — every load-bearing fact survives the rename.
- tests/uat/a6.test.ts:
* File-header rewritten to position the file as Plan 01-13's
standalone single-assertion entry point (preserves the future-
proof rationale: this entry stays around forever for fast TDD
iteration on A6 even after Wave 3 folds A6 into the orchestrator
harness.test.ts).
* REPO_ROOT resolvePath chain corrected from `..,..,..` to `..,..`
— the file is now two directory levels above the repo root
instead of three. Without this fix DIST_TEST_DIR would resolve
to a path one level above the actual repo root and
assertBundlePresent would throw. **VERIFIED by running the
driver: build path resolves correctly.**
* harnessUrl constant updated to drop `/prototype/` from the
chrome-extension://<id>/tests/uat/extension-page-harness.html
URL — must match the rollup emission path in dist-test/.
* Stdout labels updated: 'PROTOTYPE A6 result' → 'A6 result',
'Plan 01-11 PROTOTYPE — A6 ... feasibility test' → 'Plan 01-13
— A6 (Bug B canonical) standalone driver'. Inside the docstrings
the historical 'originally landed as 01-11 prototype' provenance
is preserved per the plan's contract.
vite.test.config.ts:
- `rollupOptions.input` renamed `prototype_harness` → `extension_page_harness`
pointing at the new production path. crxjs emits the harness HTML
to `dist-test/tests/uat/extension-page-harness.html` (verified by
`ls dist-test/tests/uat/`).
- The `modulePreload: { polyfill: false }` line is PRESERVED — this
is the CRITICAL SW FIX per 01-11-SUMMARY (disabling the polyfill
is what makes the test bundle's offscreen-side dynamic import work
without crashing in non-DOM contexts that incorrectly try to call
document.querySelector).
- File-header comment §4 and the inline `define.__MOKOSH_UAT__` comment
are PRESERVED — load-bearing rationale for the dedicated build-time
token (vs `import.meta.env.MODE === 'test'` which collides with
vitest).
Verification (all GREEN):
- `npm run build:test` — exit 0; dist-test/ emits
`tests/uat/extension-page-harness.html` and `assets/extension_page_harness-*.js`.
- `npx tsx tests/uat/a6.test.ts` — exits 0 with "A6 result: PASS";
5/5 checks GREEN (SETUP: badge becomes REC; A6.1 badge==''; A6.2
popup==''; A6.3 notif delta==0; A6.4 isRecording=false). End-to-end
runtime ~7s headless on this workstation.
- `npx tsc --noEmit` — exit 0 (root tsconfig + tests/uat/tsconfig.json).
- `npx vitest run` — 92/92 GREEN; the moves do not touch any vitest-
discovered files.
- `npm run build` — exit 0; Tier-1 grep gate stays GREEN
(the moves do not touch production code).
Wave 2 (next): build out `tests/uat/lib/{launch,assertions,harness-page-
driver}.ts` around the extension-page architecture; rewrite
`tests/uat/a6.test.ts` to use the shared lib (still PASSES 5/5).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Mokosh UAT harness (Plan 01-11)
Puppeteer-driven Node script that runs 14 assertions end-to-end against a real Chrome instance loaded with the Mokosh extension. Replaces Plan 01-09 Task 5's operator-empirical functional verification (the operator retains only step 1 — build — and step 14 — brand/design acceptance).
Quick start
npm run test:uat
This builds dist-test/ (the hook-enabled bundle) and runs the harness.
Exit 0 means all 14 assertions passed. Final line: UAT harness: 14/14 assertions passed.
Local-debug mode
HEADLESS=0 npm run test:uat
Opens a real Chrome window so you can watch the picker auto-accept, the badge transitions, the popup appear, etc.
Developer iteration tricks
# Skip the production build inside assertion 0 (uses existing dist/):
SKIP_PROD_REBUILD=1 npm run test:uat
# Run the harness against an existing dist-test/ (skip npm run build:test):
npx tsx tests/uat/harness.test.ts
Assertion catalog
| # | Title | Bug class | Hook used |
|---|---|---|---|
| 0 | Production bundle has no test-hook leaks | T-1-11-01 | filesystem grep |
| 1 | SW bootstrap → setIdleMode | — | sw.evaluate |
| 2 | Toolbar onClicked-idle → REC + popup | — | triggerExtensionAction |
| 3 | Offscreen displaySurface === monitor | D-15 | __mokoshTest.getCurrentStream |
| 4 | Toolbar onClicked-recording → popup, no new offscreen | — | targets count |
| 5 | SAVE_ARCHIVE → download fires | — | downloads polling |
| 6 | BUG B: simulateUserStop → badge OFF + no recovery notif | b9eeeeb |
dispatchEvent('ended') |
| 7 | RECORDING_ERROR codec-unsupported → ERR + recovery notif | — | sendMessage |
| 8 | BUG A: onStartup → mokosh-startup- notification creates | a881bf0 |
__mokoshTest.handlers.onStartup |
| 9 | Icon file sizes meet floors | Bug A precondition | sw.evaluate(fetch) |
| 10 | Manifest has notifications + 3 icons | Bug A precondition | chrome.runtime.getManifest |
| 11 | 35s recording → segments.length >= 3 | D-13 | __mokoshTest.getSegmentCount |
| 12 | ffprobe on extracted webm exits 0 | Plan 01-08 | jszip + execFile |
| 13 | Archive shape — video + meta.json version match | Plan 01-07 | jszip |
Failure isolation
Single browser, serial assertions, bail on first failure for setup- dependent assertions (assertion 0 abort means refusing to launch a potentially-leaky bundle). Per-assertion bail keeps the diagnostic output unambiguous — see RESEARCH §5 + Plan 01-11 open-question resolution 4.
On failure, the harness dumps the last 30 lines of SW console + last 30 lines of offscreen console (captured live during the run) to stderr BEFORE rethrowing — gives you contextual triage without needing to re- run with debug logging.
Known gotchas
Locale-specific picker auto-accept
The --auto-select-desktop-capture-source=Entire screen Chrome flag
auto-accepts the screen-share picker. The string "Entire screen" is
en_US-specific. If your Chrome is set to a non-English locale, the
picker option label will differ and the auto-accept will silently fail
(picker stays open; assertion 2 times out).
Fallback: switch your Chrome user-data-dir's locale to en_US for
harness runs, OR adjust the launch arg in tests/uat/lib/launch.ts to
match your locale's equivalent string.
dev-dep Chromium binary size
puppeteer pulls a ~150 MB Chromium binary at npm install time. CI
must accept this. Production npm install --omit=dev skips it cleanly.
Xvfb is NOT required
Per Plan 01-11 RESEARCH §3 empirical probes against Chrome 148, the
--headless=new mode handles screen capture without Xvfb on Linux CI
runners. If a future Chrome regresses this, Xvfb :99 & DISPLAY=:99 npm run test:uat is the fallback.
CI runner screen-capture concern
The 35s recording assertion (A11) captures whatever is on screen during that window. CI MUST run the harness in an isolated container with no concurrent workload — see T-1-11-02 in Plan 01-11's threat model.
Real Chrome download (assertion 5 → A12)
The harness configures per-page download behavior via CDP to a fresh
os.tmpdir()/mokosh-uat-downloads-* directory; downloads are NOT
written to your real ~/Downloads. The temp directory is deleted by OS
tmpdir GC.