testland/playwright-extension-fixtures
Author the Playwright fixture layer every Chromium extension test depends on - `chromium.launchPersistentContext` with `--disable-extensions-except=$DIR` + `--load-extension=$DIR`, the `channel: 'chromium'` selection that unlocks headless extension support, the `context.serviceWorkers()` + `waitForEvent('serviceworker')` race-handling pattern, and the `extensionId = serviceWorker.url().split('/')[2]` extraction recipe - plus, in references/, the extension load / reload matrix (which edit re-evaluates which surface), the `chrome.storage` test suite (area selection, quota-exceeded, `storage.onChanged`, managed read-only), and the per-surface assertion recipes (popup, content script, background messaging, MV3 auto-suspend survival). Use when authoring or debugging the fixture a Chromium extension test imports, when an edit appears to have no effect and you need the reload matrix, or when authoring popup / content-script / storage tests.
69
87%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
reload-matrix.mdreferences/
Extension reload matrix - what a code edit re-evaluates
Companion reference for playwright-extension-fixtures. Consult when an edit
appears to have no effect and you need to know which extension surface
requires an explicit reload - the manual chrome://extensions card-refresh
gesture this fixture automates.
Per the Chrome Extensions "Hello World" tutorial:
| Component edited | Reload action required |
|---|---|
manifest.json | Click refresh on the extension card |
Service worker (background.service_worker) | Click refresh on the extension card |
| Content scripts | Click refresh on the extension card plus refresh the host page |
| Popup HTML / JS | None, next open re-evaluates |
| Options page | None, next open re-evaluates |
| Other extension HTML pages | None |
An automated harness reproduces the "click refresh on the card" gesture
either by toggling chrome.management.setEnabled(id, false) then
setEnabled(id, true) (requires the "management" permission per the
chrome.management reference; management.getSelf is the
no-permission exception), or by closing and re-launching the persistent
browser context.
Anti-patterns the matrix prevents:
- Editing a content script and expecting the next page load to pick it up - content scripts need the card refresh and a host-page refresh per cr-hello.
- Reloading the card after a popup-only edit - the popup re-evaluates on next open per cr-hello; the reload is wasted time and resets service-worker state.