e2e-testing

The e2e-testing skill provides end-to-end testing patterns using Playwright for full-stack Python and React applications. It solves the problem of validating complete user workflows — login, CRUD operations, multi-page navigation, authentication flows, and file upload/download — across the whole stack and multiple browsers, in a way that stays maintainable and resists flakiness. It explicitly scopes itself away from unit and component tests, deferring those to sibling pytest and React testing skills.

The skill prescribes a concrete test structure (fixtures, page objects, tests, utilities) and a set of opinionated conventions. It enforces the Page Object Model, where every page gets a class encapsulating locators and actions while tests hold the assertions. It defines a strict selector priority — data-testid first, then role, label, placeholder, and text — and explicitly forbids brittle CSS, XPath, and DOM-structure selectors. It bans hardcoded waits in favor of explicit wait conditions on elements, navigation, API responses, and network state. It also covers authentication-state reuse, test-data management with cleanup, cross-browser validation across Chromium, Firefox, and WebKit, and CI integration, and ships template files for page objects, tests, and Playwright configuration plus a shell script for running E2E tests with a report.

The target users are full-stack engineers and QA automation developers writing critical-path regression tests, smoke tests for deployment verification, and cross-browser checks for Python/React apps. It is MIT-licensed and declares compatibility with Playwright 1.40+ and Node.js 20+. The skill's allowed tools are scoped to file editing and running npx/npm, and its behavior is limited to safe test authoring and execution, making it a benign developer-productivity resource.