e2e

Execute Basic and Extended end-to-end tests for the Imagify WordPress plugin.

81|31|Updated Jul 12, 2016
One-click install
npx skills add https://github.com/wp-media/imagify-plugin --skill e2e-wp-media
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e
Source: https://github.com/wp-media/imagify-plugin/tree/main/.claude/skills/e2e
Command: npx skills add https://github.com/wp-media/imagify-plugin --skill e2e-wp-media

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End-to-end testing for the Imagify WordPress plugin, validating core flows from setup to UI interactions across Basic and Extended tiers to ensure reliability.

Core Features & Use Cases

  • Tiered testing approach: Basic smoke tests and Extended full regression suite to cover typical and edge scenarios.
  • Environment boot and navigation: Uses a provided script to boot a local WordPress environment and verify admin pages and API endpoints.
  • Cross-layer validation: Combines REST/AJAX checks with Playwright MCP browser flows to detect regressions early.

Quick Start

Boot the environment and run the Basic tier to perform a smoke test of the E2E workflow.

Frequently Asked Questions about e2e

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

FAQPage Schema
How do I run end-to-end tests for a WordPress plugin using Playwright?

You can run end-to-end tests for a WordPress plugin using Playwright by executing a tiered testing approach that validates REST/AJAX calls and browser flows against a local WordPress environment. This ensures core functionality and UI interactions work as expected.

What is the difference between smoke tests and full regression suites in e2e testing?

In e2e testing, smoke tests verify critical basic workflows quickly, while full regression suites run extended tests to cover edge cases. This two-tier approach ensures both typical user paths and potential edge scenarios are validated for reliability.

Can I validate WordPress REST and AJAX calls with end-to-end testing?

Yes, you can validate WordPress REST and AJAX calls during end-to-end testing. The testing process combines REST/AJAX checks with Playwright browser flows to detect regressions early across different application layers.

Do I need a local WordPress environment to run Playwright e2e tests?

Yes, you need a local WordPress environment to run Playwright e2e tests. The process relies on a provided boot script to start the local environment and requires an authenticated admin session to verify admin pages and API endpoints.

What dependencies are required to automate WordPress e2e testing with curl and Playwright?

To automate WordPress e2e testing, you need environment boot tooling, Playwright MCP for browser flows, and curl for API validation. These tools work together to execute tests and validate the injected configuration values at runtime.