e2e-testing

Name: e2e-testing
Availability: InStock
Author: jacexh

Generate pytest-playwright scaffolds with Page Object Model and GitHub Actions multi-browser CI.

Updated Mar 3, 2026

Search Tags:#pytest #artifacts #playwright #e2e-testing #ci #page-object-model #flaky-tests

Ready to run

npx skills add https://github.com/jacexh/skills --skill e2e-testing-jacexh

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: e2e-testing
Source: https://github.com/jacexh/skills/tree/main/skills/e2e-testing
Command: npx skills add https://github.com/jacexh/skills --skill e2e-testing-jacexh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides patterns and concrete examples to build stable, fast, and maintainable end-to-end test suites for Python web applications, reducing flakiness and CI failures.

Core Features & Use Cases

Page Object Model & fixtures: Recommended test organization, examples of Pages, and session/auth storage to avoid repetitive logins.
Flakiness mitigation & artifact capture: Strategies for retries, isolation, network-aware waits, and saving screenshots, videos, and traces for debugging.
CI / multi-browser workflows: Guidance and a sample GitHub Actions pipeline for running tests across chromium, firefox, and webkit with artifact upload.

Quick Start

Generate a pytest-playwright scaffold that includes a pages directory, conftest with auth fixtures, and a GitHub Actions workflow for multi-browser CI.

Frequently Asked Questions about e2e-testing

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

FAQPage Schema

How do I stabilize flaky Playwright tests in GitHub Actions CI?▼

Structure Playwright tests using the Page Object Model and pytest fixtures to organize UI flows and manage browser contexts. This approach isolates test logic from UI selectors, making your end-to-end suite more maintainable.

How do I avoid repetitive logins in pytest-playwright tests?▼

Avoid repetitive logins in pytest-playwright tests by using fixtures for session and auth storage. This preserves authentication state across multiple test runs, speeding up execution while maintaining test isolation for web applications.

What is the best way to run Playwright e2e tests across chromium, firefox, and webkit?▼

Run Playwright e2e tests across chromium, firefox, and webkit using a GitHub Actions multi-browser workflow. This pipeline executes test matrices and uploads artifacts, ensuring reliable cross-browser coverage for Python web applications.

How do I capture screenshots and traces for failed Playwright tests?▼

Capture screenshots and traces for failed Playwright tests by configuring artifact collection within your pytest setup. Saving these artifacts during test execution provides visual evidence and debugging context for flaky UI flows.

Does this e2e-testing approach support Web3 wallet interactions?▼

Yes, the e2e-testing patterns support Web3 wallet interactions and critical financial flows. You can apply these Playwright and pytest examples to Python-based web applications requiring reliable UI flow validation.