extension-testing

name	extension-testing
description	Single MetaMask Extension testing entrypoint. Routes unit, UI and composed-background integration, and Selenium E2E create/maintain work (flakiness, POM anti-patterns) to the right references. Use when writing, fixing, reviewing, or placing Extension tests; when the user mentions MetaMaskController, FixtureBuilderV2, page objects, E2E flake, POM anti-patterns, or asks which Extension testing skill to install.
maturity	stable
base	true

Extension testing

One skill for MetaMask Extension functional testing. Classify the task, pick the layer, then open only the matching reference.

Flakiness note: Unlike Mobile (where Jest unit flakiness is a separate skill), Extension E2E flakiness lives inside this skill under references/e2e/flakiness.md — create and maintain share one tree.

When To Use

• Writing, fixing, or reviewing MetaMask Extension unit, integration, or Selenium E2E tests
• Choosing the right Extension test layer (unit vs integration vs E2E)
• Creating or updating page objects, flows, or fixtures (FixtureBuilderV2)
• Fixing E2E flakes or auditing POM anti-patterns
• MMQA testing-skills work that targets Extension (for example MMQA-2274)

Out of scope: performance, visual (visual-testing / mm CLI), A/B, i18n, Mobile layers, and cross-layer placement audits (phase 2). Keep those separate.