← ClaudeAtlas

playwright-extension-fixtureslisted

Use when writing or debugging Playwright tests for a Chromium browser extension: the persistent-context fixture that loads the extension and finds its ID, why an edit seems to have no effect (reload matrix), and popup, content-script, storage and MV3 service-worker tests.
testland/qa · ★ 13 · Testing & QA · score 83
Install: claude install-skill testland/qa
# playwright-extension-fixtures ## Overview Every Playwright-driven Chromium-extension test starts the same way: a persistent context launched with two flags, a service-worker race, and an extension-ID extraction. Per the [Playwright Chrome extensions docs][pw-ext], this fixture is the contract the assertion-level skills depend on - it's the foundation, not the test logic. This SKILL.md is the "how to launch" layer - the Playwright fixture pattern (`launchPersistentContext` + `--disable-extensions-except` + `--load-extension`) shared by all extension tests. The "what to assert" playbook per surface - popup, content script, background messaging, storage, MV3 auto-suspend - lives in [references/extension-surface-tests.md](references/extension-surface-tests.md) and builds on this fixture. [pw-ext]: https://playwright.dev/docs/chrome-extensions Composes with: - [references/extension-surface-tests.md](references/extension-surface-tests.md) - per-surface assertion recipes (popup, content script, messaging, storage persistence, auto-suspend) run from this fixture. - [references/reload-matrix.md](references/reload-matrix.md) - which edits require which reload; the manual `chrome://extensions` gesture this fixture automates. - [references/storage-tests.md](references/storage-tests.md) - the `chrome.storage` area / quota / event test suite run from this fixture's SW context. - [references/manifest-v3-test-surface.md](references/manifest-v3-test-surface.md) - the manifest fields t