Something went wrong. Try again.
experiments in a post-browser web
Something went wrong. Try again.
peek commit-msg.txt
956 B · 17 lines
123456789101112131415161718docs(test): record proton-pass-autofill as a deliberate permanent skipThe spec header framed un-skipping as a future "build a seeded-vaultfixture" TODO. That undersells it: the only way to satisfy the`data-protonpass-*` assertion is a real UNLOCKED Proton vault, i.e. livecredentials, which are not committable to a CI-safe fixture. So the skipis deliberate and indefinite — a manual / dev-profile-only check, not apending automation task.Also record why keeping it skipped loses no automated coverage: thecompat-layer fixes behind causes 1-3 each have credential-free coverage(sendMessage polyfill in runtime-external-polyfill.spec.ts; the bridgewindow's mandatory sandboxing enforced by main/sandbox-enforcement.test.ts).Only the aggregate live-vault end-to-end DOM assertion is unique here, andit was verified by hand on the dev profile when cause 3 was fixed (d9acbf6d).Comment-only; the spec stays test.describe.skip. peek 976a7700.