e2e-testing

Automate Playwright end-to-end tests with page objects and auth fixtures.

Updated Apr 5, 2023
One-click install
npx skills add https://github.com/fcalell/dotfiles --skill e2e-testing-fcalell
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e-testing
Source: https://github.com/fcalell/dotfiles/tree/main/dot_claude/skills/e2e-testing
Command: npx skills add https://github.com/fcalell/dotfiles --skill e2e-testing-fcalell

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This setup guides teams to implement robust end-to-end testing for web applications using Playwright, enabling reliable verification of critical user flows.

Core Features & Use Cases

  • Page Object pattern organizes interactions and promotes reusable components across tests.
  • Auth fixtures support authenticated test scenarios to avoid repeated logins.
  • Config-driven testing centralized testDir, baseURL, and project configurations for predictable runs.
  • Debugging & tracing built-in traces and debugging options to diagnose failures quickly.

Quick Start

Install Playwright and set up the test suite, then run the tests with the Playwright CLI.

Frequently Asked Questions about e2e-testing

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

FAQPage Schema
How do I automate end-to-end testing for authenticated web application flows?

Automate end-to-end testing for authenticated web flows using Playwright auth fixtures that leverage storage-based state to maintain user sessions. This approach prevents repeated logins across multiple tests and structures your test suite with reusable fixtures.

What is the best way to organize Playwright test interactions for better maintainability?

Organize Playwright test interactions by applying the Page Object pattern to structure your web page interactions into reusable components. This architecture centralizes element selectors and page workflows, making your end-to-end tests easier to maintain and scale.

How do I configure Playwright to run predictable end-to-end test suites?

Configure Playwright by centralizing your test directory, baseURL, and project configurations to establish predictable test runs. This config-driven testing approach ensures consistent execution environments across different test scenarios and browser contexts.

Why are my Playwright end-to-end tests failing and how can I debug them?

Debug failing Playwright end-to-end tests by utilizing built-in traces and debugging options to quickly diagnose failures. These tools allow you to inspect test execution step-by-step, review semantic selectors, and analyze storage state issues effectively.

Can I use Playwright fixtures to manage authentication state across multiple test scenarios?

Yes, you can use Playwright auth fixtures to manage authentication state across multiple test scenarios. They implement storage-based state mechanisms that bypass repeated login procedures, enabling reliable execution of authenticated end-to-end testing workflows.