e2e-testing

Implement Playwright end-to-end tests for Python/React applications.

Updated Jan 26, 2026
One-click install
npx skills add https://github.com/shelbeely/ADHD-Closet --skill e2e-testing-shelbeely
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e-testing
Source: https://github.com/shelbeely/ADHD-Closet/tree/main/.agents/skills/e2e-testing
Command: npx skills add https://github.com/shelbeely/ADHD-Closet --skill e2e-testing-shelbeely

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides a comprehensive framework for writing reliable end-to-end tests for full-stack applications, ensuring user workflows function as expected across different browsers.

Core Features & Use Cases

  • End-to-End Workflow Testing: Validate complete user journeys like login, CRUD operations, and multi-page navigation.
  • Cross-Browser Validation: Ensure consistent application behavior across Chromium, Firefox, and WebKit.
  • Use Case: You need to verify that a new user can successfully register, log in, create a profile, and then log out without any errors on both Chrome and Firefox.

Quick Start

Use the e2e-testing skill to write a new test for the user login flow in the tests/auth/ directory.

Frequently Asked Questions about e2e-testing

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

FAQPage Schema
How do I structure end-to-end tests using Playwright for a full-stack Python and React application?

Structure end-to-end tests using Playwright by implementing a page object model, robust selector strategies, and wait strategies to validate full-stack Python/React workflows. This framework covers test structure, authentication state reuse, and test data management for reliable cross-browser regression testing.

Can I reuse authentication state across multiple Playwright tests to speed up cross-browser validation?

Yes, you can reuse authentication state across multiple Playwright tests. This framework provides patterns for authentication state reuse, allowing you to validate critical path regressions across Chromium, Firefox, and WebKit without repeating login workflows in every test.

What do I need to set up Playwright for cross-browser e2e testing in CI?

To set up Playwright for cross-browser e2e testing in CI, you need Playwright 1.40+ and Node.js 20+. The framework includes CI integration patterns to automate regression testing and validate consistent behavior across Chromium, Firefox, and WebKit.

What is the best way to manage test data for end-to-end workflows like CRUD operations?

The best way to manage test data for end-to-end workflows is using the integrated test data management patterns provided. This ensures reliable execution of CRUD operations and multi-page navigation by maintaining consistent data states across your regression test suites.

When should I implement e2e testing patterns instead of unit tests for my application?

Implement e2e testing patterns when you need to validate complete user journeys like registration, login, and multi-page navigation. This framework ensures critical path workflows function as expected across different browsers, complementing unit tests by catching integration failures.

Does this e2e-testing framework work with both Chromium and WebKit for regression testing?

Yes, this e2e-testing framework works with Chromium, Firefox, and WebKit for regression testing. It provides cross-browser validation to ensure consistent application behavior across all major browser engines for your critical path workflows.