Manifest V3 testing guides

Build a smaller, more reliable extension release check.

Chrome extensions cross normal web pages, extension pages, content scripts, storage, permissions, and an event-driven service worker. These guides focus on the few checks most likely to expose a broken release.

Last reviewed August 18, 2026 · No signup required · Technical references link to the official Chrome and Playwright documentation.

• Manifest V3 testing checklist before releaseUse a compact manual or automated checklist across build integrity, popup, content UI, permissions, storage, upgrade behavior, and safe test data.
• How to test a Chrome extension with PlaywrightLaunch an unpacked build in a persistent Chromium context, discover the extension ID, open extension pages, and keep tests maintainable.
• How to test an MV3 service worker restartCatch missing top-level listeners, global-state assumptions, unfinished timers, and cold-start failures.

What these guides do not promise

They are not a security audit, Chrome Web Store approval service, or guarantee that every extension bug will be found. Treat them as a practical baseline, adapt them to your permissions and user journeys, and keep exploratory testing for behavior that cannot be reduced to a stable assertion.