chrome-extension-e2e-playwright

Name: chrome-extension-e2e-playwright
Availability: InStock
Author: daichan132

Automate Chrome extension end-to-end tests with Playwright.

34|Updated Oct 30, 2023

Search Tags:#playwright #e2e-testing #chrome-extension #shadow-dom #service-worker #mv3

Ready to run

npx skills add https://github.com/daichan132/Youtube-Live-Chat-Fullscreen --skill chrome-extension-e2e-playwright

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: chrome-extension-e2e-playwright
Source: https://github.com/daichan132/Youtube-Live-Chat-Fullscreen/tree/main/.agents/skills/chrome-extension-e2e-playwright
Command: npx skills add https://github.com/daichan132/Youtube-Live-Chat-Fullscreen --skill chrome-extension-e2e-playwright

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Playwright-based E2E testing for Chrome extensions, including MV3 service worker startup, extension loading, and interaction with shadow DOM, chrome.storage, and iframes, to ensure robust extension behavior across environments.

Core Features & Use Cases

End-to-end validation of MV3 extensions from load to ID retrieval
Shadow DOM, chrome.storage, and iframe interaction coverage
Guidance for stable, diagnosable tests with fixtures and references

Quick Start

Run your Playwright tests against a built extension by pointing to dist, launch a persistent context with load-extension, and smoke-check that the MV3 Service Worker starts and an extension ID can be retrieved

Frequently Asked Questions about chrome-extension-e2e-playwright

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I run E2E tests for a Chrome extension with Playwright?▼

Playwright E2E testing for Chrome extensions uses a persistent context with load-extension arguments to load your built extension, ensuring deterministic startup, robust shadow DOM interaction, and reliable diagnostics across environments.

Can I test MV3 service worker startup and shadow DOM interactions in Playwright?▼

Yes, Playwright supports MV3 extension testing by validating service worker startup, retrieving extension IDs, and interacting with shadow DOM and iframes through a persistent context designed for robust extension behavior.

What is the best way to retrieve a Chrome extension ID during Playwright testing?▼

The best way to retrieve a Chrome extension ID during Playwright testing is to load the extension via a persistent context and smoke-check that the MV3 service worker starts, which allows reliable ID retrieval across different contexts.

Why does my Playwright test fail when loading a Chrome extension?▼

Playwright tests loading a Chrome extension may fail if not using a persistent context with proper load-extension arguments; a reference-driven workflow ensures deterministic startup, robust interaction, and reliable diagnostics to prevent loading failures.

Does Playwright support chrome.storage and iframe interaction for MV3 extensions?▼

Yes, Playwright supports chrome.storage and iframe interaction for MV3 extensions by utilizing a persistent context that ensures stable interaction and diagnosable tests across various extension components and environments.