e2e

name: e2e description: Run E2E smoke tests (basic) or full acceptance + regression suite (extended).

E2E SKILL

Config loading

The following values are injected via the orchestrator prompt — do not read any config file:

• {TEMP_ROOT} = .ai
• {REPO} = wp-media/imagify-plugin
• {E2E_URL} = http://localhost:8888
• {E2E_BOOT} = bash bin/dev-start.sh
• {E2E_SETTINGS} = http://localhost:8888/wp-admin/options-general.php?page=imagify
• {E2E_CI} = true

This skill provides end-to-end test execution at two tiers. The tooling is the same (Playwright MCP + curl); the difference is scope and depth.

The local WordPress environment is at {E2E_URL} (admin / password). Boot or restart it with {E2E_BOOT}.

Tier 1 — Basic

Purpose: behavioral verification and smoke tests. Fast enough to fit inside a planning agent's execution window.

Invokers:

• grooming-agent — verify behavioral assumptions about the current system before writing the spec. Use to confirm: does the current feature behave as described in the issue? What does the current API or AJAX endpoint return for the scenario being changed?

Anti-rationalization table

Basic tier process

1. Boot the environment (idempotent — safe to run if already up):

   {E2E_BOOT}
   

   If the script exits non-zero, set status: "SKIP", note the reason, and do not block the pipeline.

2. Run the primary happy path scenario from the spec or grooming plan.

   Backend / AJAX / REST:

   # Public REST or AJAX
   curl -s -X POST {E2E_URL}/wp-admin/admin-ajax.php \
     -H "Cookie: $(cat .wp-session-cookie 2>/dev/null)" \
     -d 'action=<action>&nonce=...'
   
   # Cache headers
   curl -sI {E2E_URL}/ | grep -E '(x-cache|cf-cache)'
   

   Browser (settings page, dashboard notices, interactive UI): Use the Playwright MCP directly for basic-tier smoke. Do not delegate to e2e-qa-tester at this tier (that is the extended tier path):

   mcp__playwright__navigate({ url: "{E2E_URL}/wp-login.php" })
   # login
   mcp__playwright__fill({ selector: "#user_login", value: "admin" })
   mcp__playwright__fill({ selector: "#user_pass", value: "password" })
   mcp__playwright__click({ selector: "#wp-submit" })
   # primary scenario
   mcp__playwright__navigate({ url: "{E2E_SETTINGS}" })
   mcp__playwright__snapshot({})
   # Inspect snapshot output to confirm expected element/text is present
   

   Take at most 1–2 screenshots if helpful, but do not publish them at this tier.

3. Report:

   {
     "status": "PASS|FAIL|SKIP",
     "scenarios_tested": ["Settings page loads without errors after enabling X option"],
     "details": "Logged in as admin, navigated to {E2E_SETTINGS}, confirmed no JS console errors and X toggle present"
   }
   

   SKIP: {E2E_BOOT} failed or environment unreachable. Record reason. Do not block the pipeline.

Basic tier boundaries

• Do: verify the one primary scenario from the spec or grooming plan
• Do: probe current-system behavior (grooming-agent only) when an assumption needs verification
• Do not: cover all acceptance criteria (that is extended tier)
• Do not: write or commit Playwright specs (that is extended tier via e2e-qa-tester)
• Do not: publish screenshots (that is extended tier)

Tier 2 — Extended

Purpose: full acceptance criteria coverage, regression testing, edge cases, visual comparison, and Playwright spec authoring with screenshot evidence.

Invoker: qa-engineer only.

Execution: the qa-engineer agent delegates browser flows to the e2e-qa-tester sub-agent, which handles Playwright MCP driving, temporary spec authoring under .e2e-temp/, screenshot publishing via the commit-SHA method, and clean-up.

The qa-engineer agent itself handles:

• Strategy A (API / functional validation via curl)
• Strategy C (test-suite-only fallback when the environment is unreachable)

For details, read:

• .claude/agents/qa-engineer.md — strategy selection and report format
• .claude/agents/e2e-qa-tester.md — browser flow execution, spec authoring, screenshot publishing

The extended tier writes Playwright specs to .e2e-temp/ (gitignored, never committed when {E2E_CI} is false). Because {E2E_CI} is true for this project, e2e-qa-tester will commit spec files to the permanent suite under Tests/e2e/specs/ rather than delete them.

Screenshots go to .e2e-screenshots/ (gitignored). Screenshots are published using the commit-SHA method: commit screenshots temporarily to the branch, push, capture the SHA, then remove them in a follow-up commit. Use the SHA-based raw.githubusercontent.com URL in QA reports (permanent even after file removal):

https://raw.githubusercontent.com/wp-media/imagify-plugin/<SHA>/.e2e-screenshots/<filename>

When to use which tier

Project-specific notes

• The boot script {E2E_BOOT} is idempotent. Always run it before testing — don't pre-check whether the environment is up.

• Admin credentials: admin / password.

• Settings page URL: {E2E_SETTINGS}.

• Plugin activation check:

  npx @wordpress/env run cli wp plugin list --name=imagify
  

• Playwright config: Tests/e2e/playwright.config.ts. Test specs: Tests/e2e/specs/. Page objects: Tests/e2e/pages/. Fixtures: Tests/e2e/fixtures/.

• Page Object Model files:

  • Tests/e2e/pages/settings.ts → SettingsPage
  • Tests/e2e/pages/bulk-optimization.ts → BulkOptimizationPage
  • Tests/e2e/pages/media-library.ts → MediaLibraryPage

• API-key-gated tests require IMAGIFY_TESTS_API_KEY to be set (sourced from .env.local):

  test.skip( ! process.env.IMAGIFY_TESTS_API_KEY, 'IMAGIFY_TESTS_API_KEY not set' );
  

• Run the full E2E suite via: bash bin/test-e2e.sh (flags: --headed, --ui, or a spec pattern).

• The basic tier never writes Playwright spec files and is invoked by grooming-agent only. Implementation agents (backend-agent, frontend-agent) do not invoke the e2e skill — full E2E validation belongs to the qa-engineer + e2e-qa-tester tier.

• Known admin routes:

  Area	URL
  Settings	/wp-admin/options-general.php?page=imagify
  Bulk optimization	/wp-admin/upload.php?page=imagify-bulk-optimization
  Custom folders (Files)	/wp-admin/upload.php?page=imagify-files
  Media library (list)	/wp-admin/upload.php?mode=list