e2e-testing

Automate Playwright end-to-end tests for the WooPayments platform.

191|83|Updated Mar 2, 2019
One-click install
npx skills add https://github.com/Automattic/woocommerce-payments --skill e2e-testing-automattic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e-testing
Source: https://github.com/Automattic/woocommerce-payments/tree/main/.claude/skills/e2e-testing
Command: npx skills add https://github.com/Automattic/woocommerce-payments --skill e2e-testing-automattic

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of running end-to-end tests, setting up the necessary testing environment, and debugging any failures that occur, ensuring code changes function correctly from a user's perspective.

Core Features & Use Cases

  • E2E Test Execution: Run comprehensive end-to-end tests using Playwright in a real browser environment.
  • Environment Setup & Management: Facilitates the initial setup of the E2E testing environment and provides commands to start, stop, and reset containers.
  • Debugging Tools: Offers detailed guidance on interpreting test failures, utilizing screenshots, traces, and direct access to the E2E site and container logs.
  • Use Case: After developing a new payment gateway feature, use this Skill to run all relevant E2E tests to confirm it integrates seamlessly with the checkout process and admin interfaces.

Quick Start

Run all E2E tests by executing the command npm run test:e2e.

Frequently Asked Questions about e2e-testing

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

FAQPage Schema
How do I run E2E tests for WooPayments using Playwright?

To run E2E tests for WooPayments, execute the command `npm run test:e2e` to validate new features and bug fixes from a user's perspective in a real browser environment.

How do I debug Playwright E2E test failures?

Debug Playwright E2E test failures by analyzing generated artifacts like screenshots, traces, and container logs, alongside direct access to the running E2E site for failure analysis.

Can I manage the E2E testing environment with this setup?

Yes, you can manage the E2E testing environment through commands that facilitate initial setup and allow you to start, stop, and reset containers for test execution.

What is the best way to validate WooPayments checkout integration after development?

The best way to validate WooPayments checkout integration is running comprehensive E2E tests using Playwright to confirm new payment gateway features integrate seamlessly with checkout and admin interfaces.

Why do my Playwright E2E tests fail after code changes?

Playwright E2E tests fail because code changes might disrupt user-perspective functionality; use screenshots, traces, and container logs provided by the testing framework to interpret the failures.

Do I need Docker to run E2E tests with Playwright?

Environment setup for E2E testing with Playwright typically requires Docker to manage containers, allowing you to start, stop, and reset the testing environment efficiently.